google-search-console-mcp

Measure how Google AI Overviews are cannibalizing organic CTR. Use when asked about AI Overview impact, SGE cannibalization, or why CTR is dropping despite stable rankings.

Detect keyword cannibalization, meaning queries where multiple pages compete for the same rankings. Use when asked about competing pages, keyword overlap, or cannibalization.

Find content optimization targets across two zones: striking distance

Audit indexing status with a site-wide overview first, then per-page deep-dive on top pages. Use when asked about crawling, indexing issues, or whether pages are indexed by Google.

Full diagnostic for a single URL combining indexing status, search performance, Core Web Vitals, and query breakdown. Use when asked to analyze a specific page or diagnose why a particular URL is underperforming.

Audit structured data (schema markup) across the top pages to surface errors blocking rich results eligibility. Use when asked about rich results, schema errors, or structured data health.

Generate a complete weekly SEO performance report for a site, including alerts, anomalies, and period-over-period comparison. Use when asked for a site summary, performance overview, or weekly report.

Audit sitemap health and coverage across all submitted sitemaps. Use when asked about sitemap issues, submitted vs. indexed counts, or sitemap errors.

Diagnose sudden or sustained traffic drops by finding the affected period, lost queries, and most likely root cause. Use when asked why traffic fell, what changed, or whether a Google algorithm update had an impact.

Review Python code in the gsc-mcp codebase for clean code violations. Checks function size, single responsibility, type hints, naming, error handling patterns, and adherence to the project's module contracts. Use when refactoring a module or before code review.