SiteWide MCP Search Console
Google Search Console MCP for Claude and ChatGPT.
Connect Search Console to Claude, ChatGPT or Cursor with one Google sign-in. Ask about clicks, queries, indexing and sitemaps in plain English, on your own verified properties. No Google Cloud project, no Python, no JSON key.
Free: 500 requests a month, no card. Paid: $9/mo after 30 days free.
“Which pages lost the most clicks in the last 28 days, and are they still indexed?”
- 1 gsc_search_analytics Search Console
- 2 gsc_inspect_url Search Console
Three pages account for 71% of the drop. /pricing/ fell from 1,240 to 310 clicks, and Google now picks /pricing-old/ as its canonical, so the page you want ranking has dropped out of the index.
The other two are still indexed and still rank in the top 5. Their clicks fell with impressions, which points to a seasonal dip rather than anything on the site.
Does Google Search Console connect to Claude?
Yes, through MCP (Model Context Protocol). Search Console has no built-in Claude connector, so you add an MCP server that reads the Search Console API for Claude. SiteWide is that server, hosted: paste one URL into Claude’s Settings → Connectors, sign in with the Google account that owns the property, and Claude can read your clicks, queries, index status and sitemaps.
The same steps work in ChatGPT (developer mode), Cursor and Claude Code.
The Search Console tools.
You never call them by name. Ask the question and Claude picks the tool.
All SiteWide tools →-
gsc_search_analyticsGoogle sign-inClicks, impressions, CTR and average position, plus top queries and pages. Filter by query, page, country, device — across web, image, video, news, Discover and Google News. (Google reports pages but no queries for Discover and Google News, and the tool says so instead of failing.)
-
gsc_inspect_urlGoogle sign-inIs this URL indexed? Coverage state, robots and fetch state, last crawl, Google’s chosen canonical vs yours, mobile usability, rich results.
-
gsc_sitemapsGoogle sign-inSubmitted sitemaps, when Google last downloaded each, warnings and errors, and submitted-vs-indexed counts.
Things to ask it.
Paste any of these into Claude once SiteWide is connected.
- Which queries rank 8–15 with lots of impressions and a CTR under 1%?
- Compare clicks this month to last month by page. What dropped, and why?
- Is /pricing/ indexed? If it isn’t, tell me why.
- Which sitemap has the biggest gap between submitted and indexed?
- Show my Discover clicks for the last 90 days.
- Which pages get Google clicks but aren’t in Bing’s index?
- Write new titles for my 10 lowest-CTR pages that rank in the top 5.
Connected in about a minute.
No Google Cloud project, no JSON key, nothing to install.
Full setup steps →-
Create your account
Sign in with Google or an email link. The free plan switches on straight away: 500 requests a month, no card.
Create a free account → -
Connect Search Console
On your account page, click Connect Google. Search Console is included in the first sign-in, and every site you’ve verified in Search Console switches on.
-
Paste one URL into Claude
In Claude: Settings → Connectors → Add custom connector. Name it SiteWide and paste this.
https://mcp.alejandrorioja.com
SiteWide or the alternatives?
There are good free Search Console MCP servers on GitHub. Most run on your own computer, so they suit someone comfortable with Python and the Google Cloud console.
| SiteWide | Open-source GSC server | Build your own | |
|---|---|---|---|
| Setup | One Google sign-in | Google Cloud project, OAuth client JSON, Python | All of that, plus writing the server |
| Works in claude.ai and the mobile app | Yes, it’s hosted | Usually desktop only (runs locally) | Only if you host it |
| Other sources in the same chat | GA4, Google Ads, Bing, Ahrefs, a site crawler, Core Web Vitals | Search Console only | Whatever you build |