MCP connectorsGoogle Search Console

Google Search Console MCP: connect Google Search Console to Claude and ChatGPT

Ask Claude or ChatGPT which searches brought the most clicks last month, which pages lost ground in Google since the redesign, or why the new pricing page is not showing up at all. The answer comes straight from Google Search Console. No exports to clean up, no filters to rebuild every Monday.

With Deployed OS everyone connects with their own Google account. The AI sees the properties that person has in Search Console, and it only reads: nothing in Search Console is submitted or changed.

4 read actions · read-only · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Google Search Console in Claude and ChatGPT

Marketing

Search before the Monday meeting

Clicks, impressions and the biggest queries last week against the week before, summarised in the chat in two minutes. No report to build first.
Content and SEO

Which pages to fix first

Pages with many impressions and few clicks, or queries where you sit just outside the first page. A list of what to rewrite next, with the numbers behind it.
Founders

Is the new page in Google yet?

Ask about one address and hear whether Google has indexed it, when it last came by, and whether something is telling it to stay away.
Agencies

Client reports without the exports

The same questions for each client site you have access to: how search did this month, by country and device, in words the client can read.
Examples

Ask it like this

  • “Which 20 queries brought the most clicks to the site in the last 28 days, with CTR and average position?”

  • “Which pages lost the most clicks in September compared with August?”

  • “Show clicks and impressions per day since the new site went live on 1 September.”

  • “Is https://www.brightwellhomes.com/pricing indexed, and when did Google last crawl it?”

  • “Do any of our submitted sitemaps have errors or warnings?”

  • “How does mobile compare with desktop in the United Kingdom for queries that contain “kitchen fitter”?”

The connector

What the Google Search Console MCP connector does today

  • Readssearch_console_list_sites

    Lists the Search Console properties your Google account has access to, with your permission level on each.

  • Readssearch_console_query

    Reads search performance for one property: clicks, impressions, CTR and average position by query, page, country, device or date, filtered as you ask, for the last 28 days up to yesterday unless you say otherwise.

  • Readssearch_console_list_sitemaps

    Lists the sitemaps submitted for a property, with when each was last submitted and read by Google, its warnings and errors, and how many URLs it holds.

  • Readssearch_console_inspect_url

    Inspects one URL as Google’s index knows it: whether it is indexed, the last crawl, the canonical Google chose, robots.txt and noindex state, and the link to the report in Search Console.

Need it to do more? We extend connectors for the companies that use them.

Security

Who sees what

Read-only
The connector reads Search Console: properties, search performance, submitted sitemaps and how Google indexes a URL. It cannot submit a sitemap, request indexing, add users or change any setting.
Each person’s own rights
Everyone connects their own Google account, so the AI sees the properties that account has in Search Console. Someone without access to a client’s site gets nothing from it through the AI either.
You choose who gets it
Admins decide which groups at the company can use the Google Search Console connector at all. Everyone else never sees it.
Every call logged
Who asked, which connector, when. Deployed OS shows reads per connector and per person, and the log can be exported.
Setup

Set up the Google Search Console connector in three steps

01
An admin switches on Google Search Console in Deployed OS and chooses which groups get it.
02
The admin decides what the AI may read there, per group.
03
Each person connects their own Google work account. From then on they just ask, in Claude, ChatGPT or Copilot.
Questions

Google Search Console MCP: common questions

Your admin sets up Google Search Console in Deployed OS once. You add your company’s Deployed OS connection in Claude, connect your own Google work account and start asking. The same connection works in ChatGPT and Copilot.

No. It reads search performance, sitemaps and how a URL is indexed, nothing more. No sitemap is submitted, no indexing is requested and no user or setting is changed. If you want it to do more, we can extend it for you.

Only the properties they already have in Search Console. The AI uses each person’s own Google account, so an agency colleague who is not added to a client’s property cannot ask about that client.

Answers cover the last 28 days up to yesterday unless you ask for something else. Ask for any range you like, and the answer says which property and dates it covers. URL inspection shows what Google’s index knows about the page right now.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. On-premises is possible too. Search data is fetched from Google Search Console when someone asks for it.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.