Google Search Console, in your AI chat.

Ask your data anything

• “Which of my pages lost the most clicks this month vs last?”
• “Show queries at position 8–15 with real impressions — what's closest to page 1?”
• “Is /pricing indexed? If not, why not?”
• “How much Google Discover traffic do I get?”
• “Which new queries started showing up in the last 28 days?”

Claude for SEO: copy a research prompt and review the result →

Built-in analyses

Five ready-made analyses ship as slash-commands:

• /seo_checkup — trend, movers, top 3 moves
• /cannibalization_check — pages competing for one query
• /striking_distance — position 5–15 wins, fix per page
• /traffic_drop — what fell, where, most likely cause
• /indexing_audit — sitemaps + index status of top pages

Setup

1. 1. Sign in (once)
   npx search-console-mcp-server login
2. 2. Add to your client
   Claude Code:
   claude mcp add gsc -- npx -y search-console-mcp-server
   Claude Desktop / Cursor (mcpServers config):
   "gsc": { "command": "npx", "args": ["-y", "search-console-mcp-server"] }
3. 3. Ask

   Six tools: your properties, search analytics (every dimension + Google Discover), period comparison with the deltas computed, single + batch URL inspection, and sitemaps.

Privacy

• Read-only Google scope — modifying your properties is impossible, not disabled.
• Tokens are minted by Google directly to your machine and stored only in ~/.search-console-mcp/. No proxy, no telemetry.
• Prefer your own Google Cloud project? Set SEARCH_CONSOLE_MCP_CLIENT_ID / SEARCH_CONSOLE_MCP_CLIENT_SECRET.