mcp-seo-audit
This server provides on-page SEO analysis via five MCP tools, requiring no API keys. It enables automated audits of public web pages, including structured data extraction, robots.txt and sitemap analysis, and link checking.
audit_page: Fetches a URL and returns title/meta description lengths, canonical tags, robots meta, Open Graph & Twitter card data, heading outlines, image alt coverage, word count, language, and hreflang attributes.
extract_schema: Extracts all JSON-LD blocks from a page, lists @type values, returns parsed objects, and reports any parse errors.
check_robots: Fetches and parses a site's robots.txt, showing user-agent groups, allow/disallow rules, declared sitemaps, and crawl-delay directives.
parse_sitemap: Parses a sitemap.xml or sitemap index, returning total URL count, a configurable sample of entries with lastmod dates, and nested sitemap references.
extract_links: Lists all page links categorized as internal/external/nofollow, and optionally HEAD-checks internal links (up to a configurable limit) to detect broken ones.
Enables retrieval of real-user Core Web Vitals from the Chrome UX Report API, including LCP, CLS, INP, FCP, and TTFB at the 75th percentile with Google's performance verdicts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-seo-audit Audit example.com and give me a prioritized fix list."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-seo-audit

On-page SEO analysis as MCP tools.
An MCP server that exposes on-page SEO analysis — metas, structured data, robots.txt, sitemaps and links — as tools any MCP-compatible client can call. The six core tools need no API keys and no accounts: everything runs off plain public-page fetches. check_vitals optionally adds real-user Core Web Vitals with a free API key.
Tools
Tool | Returns |
| Title/meta lengths, canonical, robots meta, Open Graph & Twitter cards, headings outline, image alt coverage, word count, lang, hreflang |
| Every JSON-LD block parsed, |
| robots.txt user-agent groups, allow/disallow rules, declared sitemaps |
| URL counts, |
| Internal/external/nofollow split, optional broken-link check |
| Breadth-first crawl of internal links, auditing every page and aggregating findings by issue category |
| Real-user Core Web Vitals from the Chrome UX Report: LCP, CLS, INP (plus FCP and TTFB) at the 75th percentile with Google's good / needs improvement / poor verdicts — needs a free API key |
The server returns structured data and leaves the interpretation to the client. The same tools drive a quick audit, a competitor comparison, or a full crawl conversation.
Related MCP server: mcp-seo
Install
Requires Node.js 20.18.1 or newer — cheerio pulls in undici 7, which needs the File global introduced in Node 20. On older versions the server fails to start.
No install step — register the server with any MCP client and npx fetches it on first run:
{
"mcpServers": {
"seo-audit": {
"command": "npx",
"args": ["mcp-seo-audit"]
}
}
}On Windows, wrap the command in cmd:
{
"mcpServers": {
"seo-audit": {
"command": "cmd",
"args": ["/c", "npx", "mcp-seo-audit"]
}
}
}To try it outside a client, npx mcp-seo-audit prints mcp-seo-audit ready and waits for a client on stdio.
From source
For contributors, or to run an unreleased change:
git clone https://github.com/mk-techi/mcp-seo-audit
cd mcp-seo-audit
npm install
npm run devThen point the client at the local checkout instead of the published package:
{
"mcpServers": {
"seo-audit": {
"command": "npx",
"args": ["tsx", "/absolute/path/to/mcp-seo-audit/src/index.ts"]
}
}
}Core Web Vitals (CrUX) API key
check_vitals queries Google's Chrome UX Report API — the Core Web Vitals real Chrome users experienced over the last 28 days, the same field data Google Search uses. It reads a key from the CRUX_API_KEY environment variable:
{
"mcpServers": {
"seo-audit": {
"command": "npx",
"args": ["mcp-seo-audit"],
"env": { "CRUX_API_KEY": "your-key" }
}
}
}The key is free and needs no billing account: create an API key in the Google Cloud console and enable the Chrome UX Report API for its project. Without the key, check_vitals explains how to get one and every other tool keeps working.
Usage
Once connected, the tools are available. Example prompts:
Audit example.com and give me a prioritized fix list.
Does this page have valid JSON-LD? Which types, and what's missing for rich results?
Compare the on-page SEO of my landing page against a competitor's.
Find broken internal links on the homepage.
How are my real-user Core Web Vitals on mobile, and which metric should I fix first?
Build
npm run build # emits dist/
npm start # runs the compiled serverRoadmap
crawl_site- follow internal links up to N pages and aggregate issuesSchema validation against Google's rich results requirements
License
MIT
Available Tools
5 toolsaudit_pageAudit a page's on-page SEOA
Fetch a URL and return structured on-page SEO data: title and meta description with lengths, canonical, robots meta, Open Graph and Twitter cards, headings outline, image alt coverage, word count, lang and hreflang.
Inputs: url (required).
check_robotsFetch and parse robots.txtA
Fetch a site's robots.txt and return user-agent groups with their rules, declared sitemaps and crawl-delay directives.
Inputs: siteUrl (required).
extract_linksExtract and check linksA
List a page's links split into internal and external with nofollow counts. Optionally HEAD-checks internal links to find broken ones.
Inputs: url (required), checkLimit, checkBroken.
extract_schemaExtract structured data (JSON-LD)A
Extract every JSON-LD block from a page, list the @type values found, and return the parsed objects along with any parse errors.
Inputs: url (required).
parse_sitemapParse a sitemapA
Fetch a sitemap.xml or sitemap index and return the URL count, a sample of entries with lastmod, and any nested sitemaps.
Inputs: sitemapUrl (required), sampleSize.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct aspect of SEO auditing: page content, schema, robots.txt, sitemaps, and links. There is no overlap in their purposes, making selection unambiguous.
All tool names follow a consistent verb_noun pattern: audit_page, extract_schema, check_robots, parse_sitemap, extract_links. The naming is predictable and follows a clear convention.
Five tools is well-scoped for an SEO audit server. Each tool covers a core aspect of SEO analysis without redundancy, and the count feels neither sparse nor bloated.
The tool set covers the essential components of a technical SEO audit: on-page elements, structured data, robots directives, sitemap discovery, and link analysis. There are no obvious gaps for a standard audit workflow.
Maintenance
Related MCP Connectors
Audit, rank-track and analyze SEO for sites via an authenticated MCP server.
Free MCP server that audits any public URL: technical SEO, Core Web Vitals, indexing checks.
Your agent needs to crawl a site and say what is wrong with it — broken tags, duplicate content, pages nothing can index, resources that never load. **What you can ask for** • "Crawl this site and list every page with a duplicate title or missing description." • "Which pages are non-indexable, and why?" • "Run Lighthouse on these URLs and give me the failing audits." • "Show the internal link graph and the orphan pages." • "Give me this page's raw HTML and its microdata." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-onpage/mcp and sign in with OAuth — there is no key to create or paste. 20 tools: submit a crawl and read its summary, pages, resources, links and waterfall; duplicate content and duplicate tags; keyword density; non-indexable and uncrawlable resources; parsed content, raw HTML, microdata, screenshots and Lighthouse. **Why this rather than the source** A crawler you drive from the agent, with the audit results as structured data rather than a PDF. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the broken pages here, then ask the same agent what those pages used to rank for — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Free technical-SEO audit MCP: crawl a site, run checks, return an LLM-ready shareable report.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for website SEO + GEO analysis. Scan any URL to get scores across 5 categories (SEO, GEO, Performance, Security, Accessibility) with actionable fix recommendations. Enables AI coding assistants to audit websites and implement fixes autonomously.-
- AlicenseAqualityDmaintenanceEnables AI agents to perform comprehensive SEO audits on web pages, including meta tags, headings, links, images, performance, and more, via a CLI or MCP server.181MIT
- AlicenseAqualityBmaintenanceSEO toolkit MCP server for analyzing meta tags, robots.txt, sitemaps, keyword density, readability, and heading structure from any AI assistant that supports MCP.619 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides comprehensive technical SEO audits, Schema.org validation, AEO readiness checks, and semantic cannibalization detection via MCP and CLI.-