How to Connect Google Search Console to Claude (2026 Guide)

To connect Google Search Console to Claude, add a Search Console MCP server. Either use a hosted connector in Claude's Connectors settings, or run the open-source mcp-gsc server in Claude Desktop with a Google Cloud OAuth client. Claude can then read your clicks, queries, pages, index status and sitemaps on request.

  • By Praveen Jha · Updated 2026-10-22 · 9 min read · SEO, AEO & search
Best for
Site owners, marketers and SEO consultants
Time
10 minutes (hosted) or 25-30 minutes (self-run)
Cost
Search Console API is free; mcp-gsc is MIT open source
Works in
Claude Desktop, Claude Code; claude.ai web via hosted connectors
Level
Beginner to intermediate

What you get once Search Console is connected

Search Console is the only free source of your real Google search data: the queries people typed, how often you appeared, how often they clicked and whether Google has indexed each page. Connecting it to Claude turns that data into a conversation. Instead of building filters and exporting CSVs, you ask a question and Claude calls the Search Console API, reads the rows and explains what changed.

  • Performance: clicks, impressions, CTR and average position by query, page, country and device.
  • Comparisons: this month against last month, or any two date ranges.
  • URL inspection: whether a page is indexed, when Google last crawled it and which canonical Google chose.
  • Sitemaps: which sitemaps are submitted, when they were last read and whether they have errors.

Good to know: As of October 2026, Google does not publish an official Search Console MCP server. You connect through a community server or a hosted connector that uses Google's Search Console API with your permission.

Choose your route

  • Hosted connector (no code): a third-party service runs the MCP server for you. You add its URL under Claude Settings > Connectors > Add custom connector, then sign in with Google. Fastest, and it works in claude.ai on the web. Check the provider's privacy policy before you grant access.
  • Self-run server (free, private): you run the open-source mcp-gsc server on your own computer through Claude Desktop or Claude Code. Your data goes from Google to your machine to Claude, with no extra service in between. The steps below cover this route.

Step 1: Create Google Cloud OAuth credentials

  1. Open Google Cloud Console (console.cloud.google.com) and create a new project, for example "search-console-claude".
  2. Go to APIs & Services > Library, search for "Search Console API" and click Enable.
  3. Go to APIs & Services > OAuth consent screen. Choose External, add an app name and your email, and save.
  4. Still on the consent screen, add your own Google account under Test users. While the app is in testing, only test users can sign in.
  5. Go to APIs & Services > Credentials > Create credentials > OAuth client ID. Choose Desktop app and click Create.
  6. Download the JSON file and save it somewhere permanent, for example Documents/client_secrets.json. Do not share this file.

Step 2: Install uv (it runs the server for you)

mcp-gsc is published as a Python package. The simplest way to run it is uvx, which downloads and starts it without a manual Python setup. On macOS or Linux, run these in Terminal:

Terminal

curl -LsSf https://astral.sh/uv/install.sh | sh
source $HOME/.local/bin/env
which uvx

Copy the path that which uvx prints, for example /Users/yourname/.local/bin/uvx. Claude Desktop needs the full path because it does not read your shell profile.

Step 3: Add the server to Claude Desktop

Open Claude Desktop > Settings > Developer > Edit Config. This opens claude_desktop_config.json (on macOS it lives in ~/Library/Application Support/Claude/). Add the server inside mcpServers, using your own uvx path and JSON file path:

claude_desktop_config.json

{
  "mcpServers": {
    "gscServer": {
      "command": "/Users/yourname/.local/bin/uvx",
      "args": ["mcp-search-console"],
      "env": {
        "GSC_OAUTH_CLIENT_SECRETS_FILE": "/Users/yourname/Documents/client_secrets.json"
      }
    }
  }
}

If other servers are already listed, add a comma between entries. Then quit Claude Desktop completely (Cmd+Q on Mac) and reopen it.

Step 4: Sign in and run a read-only test

  1. In a new chat, ask: "Call get_capabilities for the Search Console server."
  2. A browser window opens the first time. Sign in with the Google account that has access to your Search Console property, then approve.
  3. Ask: "List my Search Console properties." You should see entries such as sc-domain:example.com or https://example.com/.
  4. Ask one small question first, such as top 10 queries for the last 28 days, before running anything larger.

Safety: Most tools only read data, but mcp-gsc can also submit or delete sitemaps and add or remove properties. Keep Claude's tool approval prompts on and approve write actions one by one.

Using it in Claude Code

The same server works in Claude Code. Add it once with your uvx path and secrets file, then ask the same questions from your project folder. This is useful when you want Claude to read Search Console data and edit your site's code in the same session.

Terminal

claude mcp add gscServer \
  --env GSC_OAUTH_CLIENT_SECRETS_FILE=/Users/yourname/Documents/client_secrets.json \
  -- /Users/yourname/.local/bin/uvx mcp-search-console

What I check first on a new site

When I review a site, the first question is not rankings, it is coverage: how many pages Google actually indexed. On praveenjha.com, Search Console showed 31 pages as "Discovered - currently not indexed" and a sitemap Google had not re-read for five weeks. That single check decided the next week of work: fix the sitemap, test a live URL, then request indexing for the pages that matter. Connecting Search Console to Claude makes this kind of check a one-line question.

Copy-paste prompts

Monthly winners and losers

Using Search Console for sc-domain:example.com, compare the last 28 days with the previous 28 days. List the 10 pages that lost the most clicks and the 10 that gained the most. For each, show clicks, impressions and average position for both periods and one likely reason.

Page-two opportunities

Find queries from the last 90 days with average position between 8 and 20 and at least 100 impressions. Group them by the page that ranks, and suggest one specific content change per page to move it onto page one.

Low CTR titles

List pages with more than 500 impressions in the last 28 days and a CTR below 1.5%. Show the current title tag if you can see it, and write two alternative titles under 60 characters that match the top queries for each page.

Indexing health check

Inspect these URLs and tell me which are indexed, when each was last crawled and whether Google chose a different canonical: [paste up to 10 URLs].

Troubleshooting

  • spawn uvx ENOENT, or the server never appears Use the full path from which uvx in the config, check the JSON for a missing comma, then fully quit and reopen Claude Desktop.
  • Access blocked: app has not completed verification Add your Google account as a Test user on the OAuth consent screen and sign in with that same account.
  • No properties returned The signed-in Google account has no access to the property. Add it under Search Console > Settings > Users and permissions, or sign in with the owner account.
  • Yesterday's numbers look low Search Console data lags by about two days. Compare complete date ranges that end three days ago.

FAQ

Is there an official Google Search Console MCP server for Claude?

Not as of October 2026. Connections run through community MCP servers such as mcp-gsc or through hosted third-party connectors, all of which use Google's official Search Console API with your OAuth permission.

Is connecting Search Console to Claude free?

Yes on the self-run route: the Search Console API is free and mcp-gsc is MIT-licensed open source. You only need a Claude plan that supports MCP servers. Hosted connectors may charge.

Does it work in claude.ai on the web?

A server running on your own computer works in Claude Desktop and Claude Code. For claude.ai on the web, use a hosted connector added under Settings > Connectors.

Can Claude request indexing for my pages?

Claude can inspect URLs and manage sitemaps through the API. The Request Indexing button for normal pages is still a manual action inside Search Console's URL Inspection tool.

Should I use a domain property or a URL-prefix property?

Use the property you already verified. Domain properties appear as sc-domain:example.com and cover all subdomains and protocols; URL-prefix properties cover one exact address.

Related pages