technical-seo-mcp
Related Servers
Alternatives to technical-seo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server for SEO auditing that performs technical SEO, content quality, Schema.org, sitemap, hreflang, and GEO checks, returning scores and prioritized fixes.MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides a suite of SEO analysis tools for auditing meta tags, headings, links, keyword density, page speed, and sitemaps without requiring external API keys.616 npm1MIT
- FlicenseNot gradedqualityBmaintenanceProvides SEO audits, content analysis, and domain overviews through an MCP server, including on-page, technical, and authority metrics with built-in browser rendering and anti-bot handling.-
- FlicenseNot gradedqualityDmaintenanceA production-ready remote MCP server that performs comprehensive SEO audits, providing structured insights on on-page SEO, technical health, and social metadata without requiring local setup.30-
- AlicenseAqualityDmaintenanceAn MCP server that audits websites for accessibility (WCAG 2.1 AA/EAA), performance, SEO, design quality, and mobile responsiveness, providing actionable scores, grades, and prioritized fixes.6MIT
- AlicenseAqualityDmaintenanceAn MCP server that gives AI agents tools to inspect a website's visibility to AI answer engines, including crawler permissions, llms.txt, structured data, on-page signals, and a full 29-check AI-readiness audit.50MIT
TDQS
Scored across 14 tools
The aggregate tools (seo_full_audit, crawl_audit) clearly overlap in scope with the individual check_* tools, but descriptions explicitly state that full_audit excludes Lighthouse and that crawl_audit reuses a shared fetch, so the granular/aggregate boundary is legible. check_robots vs check_ai_crawlers could be confused, yet the description clarifies the latter covers meta/X-Robots-Tag and per-bot status. Only these mild overlaps prevent a 5.
Nearly all tools follow a snake_case verb_noun pattern (check_*, crawl_audit, run_lighthouse, seo_full_audit). 'check_' dominates uniformly, but the mixed prefixes (check_/crawl_/run_/seo_) and the irregular 'seo_full_audit' are minor deviations from a single convention.
14 tools sit squarely in the well-scoped 3-15 range. Each tool maps to a distinct technical SEO subsystem (robots, sitemap, hreflang, structured data, rendering, caching, etc.), so none feel redundant filler.
Coverage is broad: rendering, HTTPS/redirects, page essentials, caching, structured data, sitemap, robots/AI crawlers, hreflang, URL structure, keyword placement, Lighthouse, and a site crawl. Minor gaps remain (no field/CrUX data, backlink or log-file analysis), but core technical SEO workflows have no dead ends.