seo_audit_url
Fetch a URL and analyze its SEO elements: title tag, meta description, Open Graph tags (og:title, og:description, og:image), heading hierarchy (h1-h6 counts), images without alt text, canonical URL, robots meta, and structured data (JSON-LD). Scores each element 0-100 and returns a total score wi...
This record as markdown: /tools/io-github-homenshum-nodebench/seo-audit-url.md
What seo_audit_url does on Nodebench
AI agents call seo_audit_url to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why seo_audit_url is rated Low
This tool retrieves and analyzes publicly available HTML metadata from a URL without modifying data, executing code, or causing side effects. It is purely analytical and read-only in nature. The low severity reflects minimal risk even if misused by an AI agent, as it only gathers and scores existing SEO attributes.
From the tool's definition Tool performs 'Fetch a URL and analyze its SEO elements' with 'HTTP fetch with regex-based HTML parsing' that 'Scores each element' and 'returns a total score with actionable recommendations.' No mutations, deletions, code execution, or financial operations…
Attacks that exploit this kind of access
The rule that runs seo_audit_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seo_audit_url, this is the rule to start with:
seo_audit_url is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every seo_audit_url call is checked against it from then on.
Questions about seo_audit_url
Fetch a URL and analyze its SEO elements: title tag, meta description, Open Graph tags (og:title, og:description, og:image), heading hierarchy (h1-h6 counts), images without alt text, canonical URL, robots meta, and structured data (JSON-LD). Scores each element 0-100 and returns a total score with actionable recommendations. Uses HTTP fetch with regex-based HTML parsing — no browser needed. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for seo_audit_url: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Nodebench. Nothing to install.
seo_audit_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the seo_audit_url rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for seo_audit_url. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
seo_audit_url is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue