Connect Google Search Console to your AI chat agent

Search Console is Google's own record of how your site performs in search: clicks, impressions, rankings, and indexing status for every query and page you rank for.

SourcetoMCP connects it straight to Claude, ChatGPT, or any MCP-compatible agent, so it can query real performance data instead of guessing.

Agent asks

Which pages lost the most clicks this month?

/blog/mcp-for-ai-agents: 412 clicks, down 18% vs last month

Agent asks

Is our sitemap fully indexed?

482 of 511 submitted URLs indexed · 3 warnings, 0 errors

Why Search Console data matters for your agent

Search performance data doesn't live anywhere else. Google Analytics tells you what happened once someone landed on your site. Search Console is the only record of how you actually show up in search before that.

  • It's the only source with this data. No other analytics tool shows how Google actually serves your pages in search results.
  • Query and page-level detail means real answers. Your agent can point at exactly which pages to fix, instead of reporting a vague traffic number.
  • Indexing status catches problems early. Pages Google can't find or won't index show up here before they ever show up as lost traffic.

How it works

1

Connect Search Console. OAuth in about a minute: webmasters.readonly is a non-sensitive scope, so there's no waiting on Google review to get started.

2

Your agent asks in plain language. It calls the right MCP operation behind the scenes and gets real clicks, impressions, rankings, or indexing status back, never a guess.

3

Every answer shows its work. Structured data comes back with the exact dimensions and filters used, so you can see how the answer was built rather than take it on faith.

search_console.performance

dimensions: [query, page] · period: last 28 days

QueryClicksImpr.Pos.
mcp server for ai agents2143,1024.2
connect search console to claude961,8456.1
ai agent data access589028.7
See it work

Ask about your search performance. Get real data back.

master — ✳ Claude Code — claude — 120×30
Claude Code v2.1.224
Sonnet 5 · Claude Pro
/Users/master
⚠ 1 MCP server needs authentication · run /mcp
| Using Sonnet 5 (from .claude/settings.json) · /model
  +1 more · /status
master Sonnet 5
‖ manual mode on
What's included

Built for real answers, beyond raw numbers

Every dimension Search Console supports

Break clicks, impressions, CTR, and position down by date, query, page, country, device, or search appearance, up to three at once.

Sitemap health at a glance

Submitted vs. indexed URL counts, processing status, and warning/error counts, per sitemap. No manual checking in Search Console itself.

Real-time URL inspection

Ask about one URL and get its live index status, canonical, mobile usability, and rich-results eligibility back.

Every property you can access

List every site your connected Google account can see, with permission level, not just the one you've already selected as a connection.

Filter without a spreadsheet

Up to five filters per query (equals, contains, regex) so your agent narrows straight to the rows that matter.

Read-only, always

Every Search Console operation only ever reads data. Nothing your agent asks can change a setting or delete anything.

Real prompts teams run against Search Console

Every SourcetoMCP account gets these in the Prompt Library, ready to run against your own connected property.

Performance & rankings

  • Search Console Performance Overview
  • Keyword Ranking Analysis
  • Top Pages Performance Report

Indexing & sitemap health

  • Search Console Indexing Status Check
  • Sitemap Optimization Report

Ask anything else

Your agent can call these operations directly too. The library is a starting point, not the limit.

Search Console MCP FAQ

Common questions from teams connecting Search Console to an agent.

Clicks, impressions, CTR, and position broken down by date, query, page, country, device, or search appearance, plus sitemap status and per-URL indexing detail. That's everything the four registered Search Console operations expose.

Claude, ChatGPT, Cursor, or any MCP-compatible client. Connect once from your dashboard's "Connect an agent" page and every tool you've paired can use it.

No. Connecting uses Google's own OAuth sign-in. SourcetoMCP never sees your password, and you can revoke access from your Google account at any time.

Roughly 16 months, Search Console's own retention window. We don't extend or shorten it.

No. Every Search Console operation is read-only. There's no write or manage operation for this connector.

Search Console is available on every paid plan. See Pricing for how many connections each plan includes.

Securely connect your Google Search Console to AI chat agents.

Connect your first source in minutes.