nextjs-seo-audit-mcp
Related Servers
Alternatives to nextjs-seo-audit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to audit public or localhost pages, gather structured SEO evidence, and retrieve compact reports, finding details, and next actions for triage.6 npmMIT
- AlicenseAqualityBmaintenanceEnables agents to run SEO and AI-search readiness audits (llms.txt, crawler access, sitemaps, structured data, redirects, indexability, and more), look up startup revenue listings and leaderboards, and check a domain's SPF, DKIM, DMARC, and MX records with concrete fixes. Runs locally over stdio with no account or API key, and frames all third-party responses as untrusted data.7MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to crawl and audit websites for SEO issues, returning structured JSON reports with errors, warnings, and key statistics.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to audit a site's technical SEO and AI-search readiness — including localhost dev servers — and retrieve rule explanations, fix templates, and generated llms.txt files so the assistant can edit the repo to resolve what it finds.6 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables a coding agent to audit any public page the way search engines and AI crawlers see it, including per-crawler robots.txt rules, CDN/firewall blocks, and no-JavaScript content. It returns a prioritized fix pack showing where each fix belongs in the codebase plus a command to verify it, so the agent can apply the changes, flag human-only settings, and re-run the audit to confirm.MIT
- 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
TDQS
Scored across 3 tools
audit_site is clearly the execution tool, while explain_finding and list_checks are read-only reference tools. Those two overlap slightly because both describe issue codes, but the distinction between one-code lookup and full module catalog is clear from the descriptions.
All three tools follow a consistent verb_noun pattern: explain_finding, list_checks, audit_site. There is no mixing of casing or verb style.
Three tools is compact but well-scoped for an SEO audit server: one performs the audit, one lists supported checks, and one explains findings. Each tool has a distinct role and none feels redundant.
The core workflow of discovering checks, running an audit, and interpreting issue codes is covered, including diff support via previous. Minor gaps exist around batch auditing, configuration, or separate robots/sitemap inspection, but agents can work around them.