SEO Auditor MCP Server

Audit titles, descriptions, headings, canonical tags and JSON-LD syntax with the local, read-only MCP SEO Auditor.

Local serverstdio

What is the SEO Auditor MCP Server?

MCP SEO Auditor performs static HTML checks through three read-only tools. It can inspect supplied HTML, fetch a page for an audit or crawl a small set of pages to find basic metadata and markup problems.

Audit a page after a content change

Check the title, meta description, H1, canonical, robots directive and relevant image alt text. Review each finding against the page’s intended purpose. The JSON-LD check concerns syntax; passing it does not establish rich-result eligibility or a search ranking.

Understand the small-crawl limit

The documented MVP requires Python 3.11 or later, with a Node wrapper launched through npx -y mcp-seo-auditor. crawl_site accepts one to ten pages and defaults to five. Audits inspect static HTML rather than rendering client-side JavaScript, so a browser check remains useful when content appears only after scripts run.

Setup and tool documentation. Explore related MCP servers.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
audit_htmlAudit supplied static HTML.
audit_urlFetch and audit a URL.
crawl_siteAudit a small crawl of one to ten pages.

How to install the SEO Auditor MCP Server

{
  "mcpServers": {
    "seo-auditor": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-seo-auditor"
      ]
    }
  }
}

Configuration

Node.js with npx and Python 3.11+ on PATH, or an absolute Python executable set in MCP_SEO_PYTHON.

VariableDescriptionRequired
MCP_SEO_PYTHONOptional absolute path to Python 3.11 or later.Optional

Example prompts to try

  • “Audit our homepage title, description, H1 and canonical tag, then show the findings with the affected markup.”

Frequently asked questions

No. The documented MVP checks static HTML.