Google Search Console MCP

Google Search Console in your AI, with your server next to it

Connect Search Console once, read-only, and Claude, ChatGPT, Cursor or Claude Code can read your queries, pages, indexing and sitemaps in plain words. Because SudoWhizzy is also connected to your server, your AI can check Google's numbers against what Googlebot really fetched and fix the cause.

Connect your server free See the prompt

Works with Claude, Claude Code, ChatGPT and Cursor.

How your AI does it

STEP 1
Connect Google
In your dashboard, open Search Console and sign in with Google. SudoWhizzy asks only for the read-only Search Console permission.
STEP 2
Pick your properties
Choose which verified properties your AI may read, up to your plan's limit. Agency can connect up to three Google accounts, for clients who keep their own.
STEP 3
Use the address you already have
The Search Console tools come through the same SudoWhizzy MCP address as your server tools. Reconnect your AI client once so it loads them.
STEP 4
Ask
"Why did clicks drop last week?" Your AI compares the periods, finds the losing pages and queries, checks Google's update history, inspects the URLs, and looks at the server logs for errors Google got.

What your AI can read

Clicks, impressions, CTR and position by query, page, country, device and date
Any two periods side by side, with what appeared and vanished
The biggest winning and losing queries and pages in one call
Index status, last crawl and Google's chosen canonical for up to 20 URLs at a time
Submitted sitemaps with their errors and warnings
Queries where your own pages compete (Pro and Agency)
Google's ranking updates, to line up with your traffic
Up to 16 months of history on Agency, for year-over-year and seasonality

The tools your AI gets

All through the same SudoWhizzy MCP address as your server tools. How to connect Google.

Tool	What it does	Plan
`gsc_performance_overview`	Clicks, impressions, CTR and position against the period before, with the biggest winning and losing queries and pages	Starter and up
`gsc_search_analytics`	Performance by query, page, country, device or date, with filters and two-period comparisons	Starter and up
`gsc_inspect_url`	Google's own view of up to 20 URLs: indexed or not and why, last crawl, the canonical Google picked	Starter and up
`gsc_sitemaps`	Submitted sitemaps with errors, warnings and when Google last read them	Starter and up
`gsc_cannibalization`	Queries where two or more of your pages split the impressions and compete with each other	Pro and up
`google_updates`	Google's core, spam and helpful content updates, to line up with traffic changes	Starter and up
`crawl_report`	What Googlebot, Bingbot, AI crawlers and SEO bots really fetched, from your access logs: errors, crawl waste, fake Googlebots	Every plan

Start with this prompt

Paste it into your AI with SudoWhizzy connected. It fetches the matching playbook and explains its plan before changing anything.

Using SudoWhizzy, find out why traffic to <domain> changed <recently / since date>. Start with gsc_properties and ga4_properties. Compare the last 28 days with the 28 before using gsc_performance_overview and ga4_overview, then drill down by page and query (gsc_search_analytics) and by landing page and channel (ga4_landing_pages). Check google_updates for core or spam updates rolling out at the time, and ga4_ai_traffic for visits from AI assistants. If it points at the site itself, check the server: crawl_report for errors served to Google, and core_web_vitals for the pages that lost the most. Tell me what changed, the evidence, and what you would do, before changing anything.

Why did my traffic change? · all prompts

Which plan

Search Console is on every paid plan. Starter: 3 properties, the last 30 days. Pro: 10 properties, the last 90 days. Agency: 25 properties, all 16 months Google keeps. Pricing.

Questions

Can my AI change anything in Search Console?

No. SudoWhizzy asks only for Google's read-only Search Console permission. Submitting sitemaps, requesting indexing and removals stay with you in Search Console.

Is my Search Console data stored?

No. Your AI's request goes to Google and the answer goes back to your AI. SudoWhizzy logs that the call happened and how many rows came back, not the data.

What makes this different from other Search Console MCP servers?

The server. Your AI can match Search Console's "Not found (404)" with the 404s Googlebot gets in your logs, "Duplicate, Google chose different canonical" with the canonical tags your shop outputs, and slow pages with the server's response time, then fix the cause with your approval.

I manage clients' sites in other Google accounts.

Agency connects up to three Google accounts. Your AI reads each property through the account that can see it.

Safety on every task: destructive actions wait for your approval, /etc is saved before changes, and every action is logged. How it works.

More your AI can do

Magento and Mage-OS

Connect your first server

Start free with one server in read-only mode. Upgrade when you want your AI to fix things.

Get started

Google Search Console in your AI, with your server next to it

How your AI does it

Connect Google

Pick your properties

Use the address you already have

Ask

What your AI can read

The tools your AI gets

Start with this prompt

Questions

More your AI can do

Your Magento server, run by your AI

A fast, secure WordPress server, run by your AI

From an empty VPS to a secure web server, by asking

Harden your Linux server without locking yourself out

Hacked shop or site? Find it, clean it, close the door

Move your site to a new server with minutes of downtime

Technical SEO with your AI, from Google's data to the fix on your server

Ask your AI about your GA4 traffic, and see what AI assistants send you

Connect your first server