SEO/AEO Audit MCP
Uses Google Chrome UX Report (CrUX) API to fetch Core Web Vitals data for technical SEO assessment.
Provides AI visibility analysis by querying OpenAI to check how often a brand surfaces in AI answer-engine results.
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., "@SEO/AEO Audit MCP audit https://example.com"
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.
SEO / AEO Audit MCP
An MCP server + skill that produces a 5-section landscape PDF audit for any website:
Executive Summary — health score, key metrics, top gaps, priority plan
Search Demand + Content Performance — Ahrefs keywords/pages, what's working / limiting growth
Technical SEO + AEO Readiness — crawl findings, Core Web Vitals (CrUX), structured-data gaps
Authority + Roadmap — backlink profile (with spam flags), 90-day roadmap
AI Visibility — how often the brand surfaces in AI answer-engine results, vs. competitors
It exposes three tools — fetch_audit_data (crawl + Ahrefs + Core Web Vitals), fetch_ai_visibility (grounded OpenAI brand-visibility), and render_audit_pdf — and a skill that orchestrates them into one audit <url> command.
Setup
Have an AI assistant (Claude Code, etc.)? Tell it: "Set up this tool by following AGENT_SETUP.md." → AGENT_SETUP.md
Doing it yourself? → SETUP.md
Related MCP server: @metricspot/mcp-server
Requirements
Node.js 18+
AHREFS_API_KEY(paid) — required (the core SEO data)OPENAI_API_KEY(paid) — optional; enables the AI Visibility section (omitted/"not measured" without it)CRUX_API_KEY(free, Google Chrome UX Report API) — optional; adds Core Web Vitals
The audit runs with only the Ahrefs key; the other two just add sections.
Keys go in a local .env (copy .env.example); never commit it.
Use
After setup, in your assistant: audit https://example.com → PDF saved to your Desktop.
Each audit makes ~10 OpenAI calls plus Ahrefs API usage — small but metered cost per run.
Available Tools
3 toolsfetch_ai_visibilityA
Measure how often a brand appears in AI/answer-engine results for unbiased, category-level buyer queries. Generates prompts (brand-name excluded), runs grounded web-search rankings, and returns brand visibility %, average position, per-topic breakdown, and competitor brands. Pass brand and industry from fetch_audit_data when available. Requires OPENAI_API_KEY.
Inputs: url (required), brand, industry.
fetch_audit_dataA
Crawl a website and fetch its Ahrefs SEO metrics. Returns a JSON object with: crawl (pages, issues, schema summary), ahrefs (DR, keywords, traffic, backlinks, top pages, referring domains), brand_name (inferred from schema/title), and industry (inferred from page content). Call this first when auditing a site.
Inputs: url (required).
render_audit_pdfA
Render the completed SEO/AEO audit report as a PDF file. Pass the ahrefs and crawl objects exactly as returned by fetch_audit_data (pass through unchanged), plus the ai_visibility data you gathered via web search and the narratives you wrote based on the data.
Inputs: narratives (required), crux, crawl, ahrefs, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: fetch_audit_data crawls websites, fetch_ai_visibility measures AI visibility, and render_audit_pdf generates reports. There is no overlap or ambiguity.
All tools follow a consistent verb_noun pattern (fetch_audit_data, fetch_ai_visibility, render_audit_pdf), making it easy for an agent to infer functionality from names.
With only 3 tools, the server is tightly scoped to its domain. Each tool is necessary and well-justified, avoiding bloat or insufficiency.
The tool set covers the full audit workflow: data collection (fetch_audit_data), AI visibility analysis (fetch_ai_visibility), and report generation (render_audit_pdf). No obvious gaps exist for the stated purpose.
Maintenance
Related MCP Connectors
AEO audit: score any website 0-100 for AI visibility. Checks schema, meta, content, AI crawlers.
Audit any website for AI visibility: graded report, findings with fixes, AI crawler access check.
AI website audit: security, SEO, performance, UX and accessibility checks with actionable fixes.
SEO and AI search audit for any website: technical SEO, schema, AI crawler access and llms.txt.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceProvides comprehensive website auditing for SEO, performance, accessibility, and security using AI-powered analysis. It enables users to generate detailed audit reports and actionable improvement suggestions for any given URL.-

@metricspot/mcp-serverofficial
AlicenseNot gradedqualityCmaintenanceExposes SEO and AI-readability audit tools to AI agents, enabling one-shot anonymous audits or full authenticated audits with PDF reports and organic traffic data.48 npmMIT- FlicenseNot gradedqualityCmaintenanceAudits any website for SEO issues, providing scored health checks, schema validation, and performance analysis through AI assistants.-
- AlicenseNot gradedqualityBmaintenanceRuns AI visibility (GEO/AEO) audits on websites, checking AI crawler access, schema markup, llms.txt, and content signals, with optional full PDF report.MIT