Search Console mcp

Where you rank is not what you earn.

Search Console shows you the numbers. It never tells you which of them is costing you money. Connect it to Claude and ask in plain language.

Connect Google Search ConsoleHow it works

Read-only access. Bing Webmaster Tools optional. No credit card.

0%10%20%30%15101520search positionposition 3 · 11% of clicksposition 13.6 · 1.2%
Clicks collapse faster than rank does. A page sitting at 13.6 earns roughly a ninth of what the same page earns at 3 — which is why the position number on its own tells you almost nothing.

How to connect

Connect Google

Sign in and approve read access to Search Console. No Google Cloud project of your own, no API keys to generate.

Add the server

Paste one URL into Claude, or run a single command. Your assistant handles the rest of the handshake itself.

Ask

“Run an SEO review of my site.” The server picks the right analysis and returns the findings.

Connect Google Search ConsoleStep one. The rest takes a minute.

Claude Code

claude mcp add --transport http search-console https://seomcp.namitjain.com/api/mcp

Claude desktop and web

Settings, then Connectors, then Add custom connector:

https://seomcp.namitjain.com/api/mcp

Everything else

Streamable HTTP with OAuth 2.1 and dynamic client registration. Point any MCP client at the same URL and it will discover the rest.

Guidance is built in

The server tells your assistant how to use it — which analysis answers which question, how to read the numbers, and what this data cannot tell you. That arrives over the connection, so there is nothing to install and it works in every client.

Claude Code users can add a skill file on top, for named workflows like /search-console-mcp drop mysite.com.

npx skills add https://github.com/Namit2111/search-console-mcp

Ask it the questions you would ask an analyst

Every answer is computed from your own data before it reaches the model, so you get findings and priorities rather than a table to interpret yourself.

What should I fix first?

Finds keywords ranking just off the money positions, then ranks them by the clicks a realistic three-place gain would actually add — measured against your site's own click-through curve, not a generic table.

Why did traffic drop?

Separates a ranking loss from falling demand from a snippet that stopped earning clicks, and runs a significance test so a 40% swing on twelve impressions never gets reported as a trend.

Which pages fight each other?

Finds queries where several of your own URLs compete, splitting the relevance signal, and names the page to consolidate onto.

What is quietly dying?

Tracks four consecutive windows to catch slow decay that month-over-month comparison hides entirely, and says whether the cause is competitive or a shrinking market.

Is slow loading costing me?

Joins real-user Core Web Vitals with your click data, so pages get ranked by traffic at risk. A slow page nobody visits stays at the bottom of the list.

What is broken on the page itself?

Reads your live HTML for titles, canonicals, robots directives and structured data, then flags the problems that repeat across pages, because those are template bugs.

What it can and cannot touch

ReadsYour Search Console properties, performance data, index status and sitemaps. Your name and email, to know whose account this is.
WritesNothing, unless you ask it to submit a sitemap or a URL for indexing. It cannot change your site or your settings.
StoresYour access credentials, encrypted. Performance data is fetched when you ask and cached for ten minutes, never warehoused.

Revoke any time at myaccount.google.com/permissions. Full detail in the privacy policy.

Start with your worst month

The fastest way to judge this is to point it at a drop you never explained.

Connect Google Search Console