Search Console MCP
·Updated ·6 min read·
Claude
Search Console
Guide

Connect Google Search Console to Claude

Connect Google Search Console to Claude in about a minute. Add one connector URL on claude.ai or the desktop app, sign in with Google, ask about your data.

To connect Google Search Console to Claude, add a custom connector with the URL https://mcpsearchconsole.com/mcp: on claude.ai or Claude Desktop under Customize, then Connectors, or with one command in Claude Code. Sign in with Google and approve read-only Search Console access. Claude then answers with your real queries, clicks, impressions and positions.

The connection runs through the Google Search Console MCP server we host, so there is no code, no API key and no Google Cloud project. It takes about a minute in the browser, the desktop app or the terminal.

What you need

  • A Claude account. Anthropic's help center says custom connectors work on Free, Pro, Max, Team and Enterprise plans; Free users are limited to one custom connector. On Team and Enterprise, an owner adds the connector for the organization first. Claude Code works with a Claude subscription or an API key.
  • A Google account with access to the Search Console property you want to query.
  • That's it. The MCP server is hosted and read-only; nothing gets installed.

Option 1: claude.ai and Claude Desktop (connectors)

  1. Open Customize → Connectors. The same section exists on claude.ai and in the desktop app.
  2. Add a custom connector. Click + Add, then Add custom connector, name it something like Search Console, and paste the server URL: https://mcpsearchconsole.com/mcp.
  3. Sign in with Google. Claude opens a Google window; approve the read-only Search Console scope. That is the whole authentication: the server uses OAuth, so there is no API key to create or paste.
  4. Turn it on in a chat. Click the + button at the lower left of the chat box, open Connectors and make sure Search Console is enabled.

On a Team or Enterprise plan, an owner first goes to Organization settings → Connectors, clicks Add, hovers over Custom, picks Web and enters the same URL. Members then find Search Console under Customize → Connectors and click Connect to sign in with their own Google account.

Option 2: Claude Code (one command)

In a terminal, run:

claude mcp add --transport http search-console https://mcpsearchconsole.com/mcp

Then start claude, type /mcp, pick search-console and follow the Google sign-in. The OAuth flow completes in your browser and the token is stored locally; every future session is already connected.

From then on Claude can call the server's tools on demand: search performance with filters and period comparisons, ready-made insights, URL inspection, sitemaps, PageSpeed and site-health checks. Everything is read-only by default, so Claude can analyze your site but not change it.

Check it works

Start a new chat with the connector enabled and send this first prompt:

First promptList my Search Console properties, then give me clicks, impressions, CTR and average position for the first one over the last 28 days.

What you should see: Claude calls the connector twice (first list_sites, then search_analytics; you can expand each call to see what was sent and returned). The answer lists your properties exactly as Search Console names them, such as sc-domain:example.com or https://example.com/, followed by four totals for the 28 days ending about two days ago, since Search Console data trails by roughly two days. If your sites come back, you are connected. Listing properties is free; the performance query counts as one data pull.

Prompts to try

Each prompt below works as written; the heading links to a page explaining the method and how to read the result.

Striking-distance keywordsFind my striking-distance keywords: queries where I rank in positions 6 to 20 over the last 28 days. Group them by page and tell me which three pages to improve first.
Keyword cannibalizationCheck my site for keyword cannibalization: queries where two or more of my pages rank. For each one, say which page should own the query and what to do with the others.
Low-CTR pagesList my pages with the most impressions and a CTR well below what their position suggests. Draft a better title tag and meta description for the top five.
Content decayCompare the last 28 days with the same 28 days three months ago and list the pages that lost the most clicks. For each, say whether the drop comes from position, CTR or demand.
Index coverage auditInspect my ten most-clicked pages and check my sitemaps. Tell me which pages are not indexed or have a different Google-selected canonical, and why.
Weekly SEO reportWrite my weekly SEO report: the last 7 days against the 7 before, with clicks, impressions, CTR and average position, the top three winners and losers, and one thing to do next week.
Site migration checksWe moved from old.example.com to example.com on [date]. Check the redirects on my 20 most-clicked old URLs, inspect where they land, and compare clicks before and after the move.
Technical SEO auditRun a quick technical check on my homepage: robots.txt, redirects, TLS certificate, DNS and Core Web Vitals. Report only what needs fixing.

Also available for ChatGPT, Cursor, Codex, Grok and Mistral.

Troubleshooting

Why is there no "Add custom connector" option in Claude?

Look under Customize → Connectors, then + Add. On a Team or Enterprise plan, members cannot add custom connectors themselves: an owner adds it in Organization settings → Connectors, and it then appears in your list with a Connect button.

Claude says I can't add another connector

Free plans are limited to one custom connector. Remove one you no longer use, or upgrade your Claude plan.

Why isn't Claude using the Search Console connector?

Connectors are switched on per conversation. Click + at the lower left of the chat box, open Connectors, make sure Search Console is on, and mention Search Console explicitly the first time you ask.

Google sign-in keeps looping or closing

Allow pop-ups for claude.ai and retry; the OAuth window must complete in the same browser session.

Why does Claude return no data for my site?

Ask Claude to list your properties first. sc-domain:example.com and https://example.com/ are different Search Console properties, and queries must use the exact one your Google account has access to.

Why is yesterday's Search Console data empty?

Search Console data trails by about two days. Ask for trailing windows (last 7 or 28 days) instead of yesterday.

Quota and pricing

Connecting is free: discovery and site-health tools are unlimited, and data pulls (performance queries, insights, URL inspection, sitemaps, PageSpeed) are capped at 15 a day and 40 a month on the free plan. Occasional analysis fits comfortably; if you run daily reporting or an agent on top, Solo removes the caps for €4.99 a month.

FAQ

Can I connect Google Search Console to Claude?

Yes. Claude supports remote MCP servers as custom connectors on all plans, including Free (one custom connector). Add https://mcpsearchconsole.com/mcp as a custom connector, sign in with Google, and Claude can read your Search Console data.

How do I connect Claude to GSC?

On claude.ai or Claude Desktop: Customize → Connectors → + Add → Add custom connector, paste https://mcpsearchconsole.com/mcp, then sign in with Google. In Claude Code: run claude mcp add --transport http search-console https://mcpsearchconsole.com/mcp and sign in through /mcp.

Is there a Google Search Console connector for Claude?

Not a built-in one from Anthropic or Google that we could find on 2 October 2026. You add one yourself as a custom connector pointing at an MCP server, such as ours (hosted) or an open-source server you run. Our best hosted Google Search Console MCP servers page lists the options.

Does Google Search Console have an MCP?

Google itself does not publish a Search Console MCP server that we could find on 2 October 2026. Third-party servers fill the gap using Google's public Search Console API: hosted ones like Search Console MCP, and open-source ones you run yourself.

Go further

Once the connection works, the interesting part is what you do with it: our seven SEO workflows turn these prompts into a repeatable practice, and the use-case library has a page for each prompt above. If your team lives in ChatGPT too, the ChatGPT guide is the same setup on the other side, while the Grok Bot guide covers xAI's always-on cloud agents. For what to stack next to Search Console (backlinks, crawling, conversions), see the best SEO MCP servers comparison.

Ready to put your search data in your AI?

Set up the Search Console MCP, free

Free plan included. See pricing