How to connect Google Search Console to Claude AI (2026 guide)

If you want to connect Google Search Console to Claude AI so Claude can pull your real rankings, indexing data, sitemaps, and search analytics, you have two options in 2026: spin up a local MCP server with uvx and your own OAuth client, or use a hosted MCP URL that handles auth for you. This guide walks through both, but the hosted route takes about 60 seconds and works the same in Claude Desktop, Claude on the web, Cursor, Codex, and Antigravity.

TL;DR

1. Sign in to GenieSeo with Google. 2. Approve Search Console scopes (read-only). 3. Click Create URL on the dashboard. 4. Paste the URL into Claude → Settings → Connectors. 5. Ask Claude: "What were my top 10 queries by clicks last week?"

That's it. Claude now has live, per-property Search Console data.

Why use Claude with Google Search Console at all?

Search Console is the source of truth for how your site appears in Google — impressions, clicks, average position, indexing state, mobile usability, structured data errors. Reading the dashboard is fine, but asking is faster:

• "Which pages dropped position by more than 5 places this week?"
• "Find queries where I'm ranking 8–15 with high impressions and low CTR."
• "Are there any pages indexed without a canonical?"

Claude with the right MCP server can answer all of these without you opening a single tab.

What is MCP and why does it matter for SEO?

MCP (Model Context Protocol) is the open standard Anthropic released in late 2024. It lets any AI assistant talk to any data source through a uniform interface — like USB for AI tools. Before MCP, every integration was bespoke. After MCP, "connect X to Claude" is one URL.

For SEO specifically that means Claude can call Google Search Console's API on your behalf, with your scopes, and return structured results the model can reason about. No copy-pasting CSVs.

Option 1 — Hosted MCP URL (recommended)

This is what GenieSeo provides. The flow is the same as connecting Slack or GitHub to Claude:

1. Sign up with Google. One click. We use Google's OpenID Connect to identify you, then ask for the webmasters scope so we can read your verified properties. 2. Generate your MCP URL on the dashboard. The URL has a long random token in the path — treat it like a password. 3. Paste into Claude. In Claude Desktop, go to Settings → Connectors → Add custom MCP. In Claude on the web, the same setting lives under Connectors. 4. Ask a question. Claude will list the available tools (get_search_analytics, list_properties, inspect_url, etc.) and call them when relevant.

No client_secrets.json on your laptop. No uvx runtime. Works the same on Mac, Windows, iPad, web — because the MCP server runs in our infrastructure.

Want to try it? Connect Google Search Console to Claude in 60 seconds.

Option 2 — Self-hosted with uvx

If you'd rather run the MCP server locally, the open-source gsc-mcp project on GitHub is the same code we use under the hood. The setup looks like this:

{
  "mcpServers": {
    "gsc": {
      "command": "uvx",
      "args": ["gsc-mcp"]
    }
  }
}

You'll also need to:

• Create a Google Cloud project
• Enable the Search Console API
• Configure OAuth consent screen (internal or external)
• Download client_secrets.json to your home directory
• Run the local server once to complete the OAuth dance

Total setup: 30–60 minutes if you've done it before, longer if you haven't. Fine for a developer; not great for a marketing team.

What can Claude do with Search Console data?

Once connected, Claude can call any of these tools on your behalf:

• list_properties — Every verified property on your account.
• get_search_analytics — Rows of (query, page, country, device) with clicks, impressions, CTR, position. Filter by date range, dimensions, and search type.
• inspect_url — Live URL Inspection results: indexability, last crawl, canonical, mobile usability, structured-data errors.
• list_sitemaps / submit_sitemap — Manage submitted sitemaps.
• compare_search_periods — Week-over-week or month-over-month deltas without you exporting two CSVs.

The full tool catalogue lives on the GenieSeo dashboard once you're signed in.

Common questions

Is read-only Search Console access safe?

Yes. The default scope (webmasters.readonly) does not allow Claude to add or delete properties, submit sitemaps, or change site settings. Destructive actions are gated behind an opt-in flag.

Does Claude store my Search Console data?

No. Each call goes from Claude → MCP server → Google → MCP server → Claude in real time. The MCP server holds your encrypted refresh token; nothing else is persisted.

Can I use the same URL in Claude AND Cursor?

Yes — one URL works across every MCP-compatible client. Pasting it into Cursor uses the same scopes and the same data.

What happens if my URL leaks?

Click Rotate URL on your dashboard. The old URL stops working immediately, and the new one is shown once.

Next steps

If you came here looking to connect Google Search Console to Claude, the fastest path is the hosted route — sign up, click Continue with Google, and you'll have a working URL in under a minute.

For deeper reading on what MCP unlocks, see What is MCP? The Model Context Protocol explained for SEOs.