google-seo-mcp
Related Servers
Alternatives to google-seo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to diagnose and fix technical SEO, content and generative-engine-optimization issues in one conversation by bundling 102 tools spanning Google Search Console, Analytics 4, PageSpeed/CrUX, structured data, llms.txt, AI-crawler access, WordPress and GitHub.7414 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents such as Cursor, Claude, and Windsurf to run local SEO audits, inspect routes, apply safe code fixes, and access Google Search Console, Bing, and Core Web Vitals data through 13 standard tools.1MIT
- AlicenseBqualityCmaintenanceProvides AI agents with hands-on control of Google SEO and analytics tools including Search Console, GA4, Tag Manager, Indexing API, and PageSpeed Insights, with self-configuring OAuth2.3314 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to crawl live websites, audit AEO readiness, generate Schema.org @graph JSON-LD, llms.txt, ai.txt, and robots.txt, inject structured data into HTML, validate optimizations, and retrieve framework-specific code snippets.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query 16 months of backed-up Google Search Console data in BigQuery and the live Search Console API through 39 tools covering top queries and pages, period comparisons, striking-distance keywords, cannibalization, URL inspection, sitemaps, and Core Web Vitals. It also provides site health summaries, environment discovery, and auth checks so assistants can analyze SEO performance conversationally.MIT
- AlicenseNot gradedqualityBmaintenanceConnects AI agents to live SEO data and hosted tools for site audits, keyword research, competitor analysis, local SEO, and link prospecting, with guided workflows for structured search optimization.2MIT
TDQS
Scored across 72 tools
The 72 tools have detailed descriptions and many explicitly say when to use one over another, but several adjacent SEO/GSC/audit tools overlap in practice (e.g. gsc_opportunities vs gsc_ctr_opportunities vs content_refresh_candidates vs gsc_question_queries, and page_audit vs site_crawl vs compare_pages). An agent often needs to read full descriptions to pick correctly, which indicates real boundary friction across the set.
There are recognizable prefix groups such as ga_, gsc_, github_, gmail_, schema_, ai_, and crux_, but many tools are un-prefixed or inconsistently grouped (page_audit, pagespeed, sitemap_check, compare_pages, brand_mentions, reviews_snapshot). The overall naming is mixed but still readable, fitting the middle of the scale.
72 tools is an extreme mismatch for a well-scoped MCP server, substantially above the 50+ threshold. Many tools are adjacent variants or niche sub-checks, making the surface difficult to discover and operate as a coherent set.
The server covers a very broad SEO/GEO lifecycle: Search Console and GA4 analytics, crawling, audits, schema, AI-search visibility, Core Web Vitals, local reviews, Wikipedia/KG entities, and GitHub/Gmail content operations. There are still minor gaps, such as no direct WordPress CRUD tool despite schema_generate referencing wp_set_schema, and no true backlink/rank-tracking API, but most workflows can be worked around.