seo_cro_audit
Full SEO + CRO audit of any public URL. Analyses technical SEO (HTTP status, HTTPS, title/meta/canonical/robots, H1-H2, JSON-LD structured data, sitemap, robots.txt, OG/Twitter cards), content SEO (word count, keyword density top-10, readability estimate, image alt coverage, internal/external lin...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/seo-cro-audit.md
What seo_cro_audit does on Mcp Knowledge
AI agents call seo_cro_audit to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Fully-qualified URL to audit (e.g. https://stripe.com/pricing) |
mode | string | — | Audit scope — defaults to 'full' |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
compare_competitors | array | — | Optional list of competitor URLs to compare (max 5) |
Parameters from the server's own tool schema.
Why seo_cro_audit is rated Low
This is a passive analysis and reporting tool that retrieves metadata and performance metrics from public URLs and competitor sites. It collects and evaluates data but performs no modifications, deletions, execution of arbitrary code, or financial transactions. The scope is limited to auditing and scoring publicly available web content.
From the tool's definition Tool performs analysis and auditing of public URLs: 'Analyses technical SEO', 'content SEO', 'performance signals', 'CRO', 'Returns 0-100 scores per dimension'. All operations are read-only inspection and measurement of publicly accessible web pages.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs seo_cro_audit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seo_cro_audit, this is the rule to start with:
seo_cro_audit 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 Mcp Knowledge, apply this rule, and every seo_cro_audit call is checked against it from then on.
Questions about seo_cro_audit
Full SEO + CRO audit of any public URL. Analyses technical SEO (HTTP status, HTTPS, title/meta/canonical/robots, H1-H2, JSON-LD structured data, sitemap, robots.txt, OG/Twitter cards), content SEO (word count, keyword density top-10, readability estimate, image alt coverage, internal/external links), performance signals (page size, estimated render time, inline scripts/styles, unoptimised images), and CRO (CTA detection, above-fold CTAs, forms, social proof, trust signals, pricing visibility). Optionally compares up to 5 competitor URLs. Returns 0-100 scores per dimension plus a prioritised (P0/P1/P2) recommendation list. ICP: marketing managers, SEO/CRO consultants, e-commerce ops, agency teams. Budget: 8s per URL. Cache TTL: 1h. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
seo_cro_audit accepts 4 parameters: url, mode, async, compare_competitors. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for seo_cro_audit: 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 Mcp Knowledge. Nothing to install.
seo_cro_audit 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_cro_audit 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_cro_audit. 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_cro_audit is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue