Connect Google Search Console to Claude

Ask Claude about your Search Console clicks, impressions, CTR and positions in plain language. Windsor.ai is listed in Claude’s connector directory, and Claude queries your Search Console data each time you ask, with no scheduled exports.

No CSV exports and no code. Set up in a few minutes.

Free forever plan No credit card needed
logo connect
Windsor.ai is your proven Google Search Console to Claude connector
google cloud
meta partner
google partner
snowflake
users love us
medal
soc2
google cloud
meta partner
google partner
snowflake
users love us
medal
soc2

What SEO teams ask Claude about Search Console

Claude picks the Search Console fields, runs the query through Windsor.ai and explains the result in the same chat. Three questions we ask about windsor.ai’s own property:

Did a page update work?

Give Claude the page and the date you changed it. It compares the weeks before and after: impressions for new queries, position for the main target queries and ctr after a title or meta description change.

Which pages compete for the same query?

Claude groups query by page and lists queries where two or more of your URLs collect impressions, with each URL’s clicks and position.

Search Console next to GA4

Connect GA4 to Claude as well and ask about both together: Search Console clicks per landing page against GA4 organic sessions, or the site total against the sum of query rows, to see how many clicks Google reports without a query.

Using Windsor.ai to connect data from Google Search Console to Claude

Supported fields: 10 metrics43 dimensions

Windsor.ai is a connector in Claude’s directory. It works on every Claude plan, including Free, in Claude on the web, Claude Desktop and Claude Code. Claude can read every Search Console property your Google account has access to, by query, page, country, device, date, search type (web, image, video, news) and search appearance, plus the status of your sitemaps.

Each question runs as a query on Search Console data through Windsor.ai when you ask it. Windsor.ai keeps the result of an identical query for up to 6 hours. Search Console usually finalizes a day about 2 days later, and Claude can include Google’s fresh, not yet final data for the most recent days when you ask for it. Access is read-only: Claude reports on your properties and cannot change settings, submit sitemaps or request indexing (see the write actions documentation).

Claude answer through Windsor.ai: latest finalized Search Console day 2 November 2026, with fresh data for 3 and 4 November
Join 40,000+ businesses that trust Windsor.ai to streamline Google Search Console to Claude integration
audi logo
colgate
asics
roche
novo nordisk logo
UBS
unicef
verisure
wpp
club med
skoda
heineken
puma
audi logo
colgate
asics
roche
novo nordisk logo
UBS
unicef
verisure
wpp
club med
skoda
heineken
puma

How to connect Google Search Console to Claude with Windsor.ai

Explore our video tutorial and a step-by-step guide to integrate your data from any source into Claude with the Windsor.ai connector.

1

Select your data source

Choose Google Search Console as your data source in Windsor.ai, sign in with Google and select the properties Claude should read.

Google Search Console data source
Google Search Console data source
windsor.ai connector claude
Claude listing windsor.ai Search Console queries on page two of Google, through the Windsor.ai connector

Is there an official Google Search Console connector for Claude?

No. On 4 November 2026, Claude’s directory had no Search Console connector from Google; Google’s own listings there are Gmail, Google Drive, Google Calendar, Google Cloud BigQuery and Google Compute Engine. Search Console reaches Claude in one of four ways:

  • Windsor.ai connector: listed in Claude’s directory, added with one click, with Search Console next to GA4, Google Ads and 350+ other sources in the same chat. Read-only.
  • Other hosted servers: Porter Metrics, Data Bloo, RightBlogger and mcpsearchconsole.com publish their own server addresses, which you add as a custom connector. Their reach, limits and prices are on their own pages.
  • Open-source servers: mcp-gsc and similar projects usually run on your computer with your own Google Cloud project and OAuth client. Some can inspect URLs, submit sitemaps or send indexing requests, which Windsor.ai does not do. Setup steps are in the Search Console MCP guide.
  • CSV export: download a report from Search Console and upload it to a chat. The export holds up to 1,000 rows and stops at the day you exported it.

The setup for each route, with prompts, is in how to connect Google Search Console to Claude.

Which one to choose

Matei Nicolae-Onea, Director of SEO at Windsor.ai, has run Search Console through his own Google Cloud OAuth setup, through a BigQuery export and, almost daily, through the Windsor.ai connector:

  • Performance data next to other sources: the Windsor.ai connector. No Google Cloud project, and GA4 or ad data is in the same chat.
  • URL inspection or indexing requests: an open-source server. It takes more time to set up and needs maintenance when Google changes its API.
  • Long history at scale: Search Console’s bulk export to BigQuery keeps every day from the day you set it up, past the 16 months the API returns. Claude can read BigQuery as well.

What the API returns that the export does not

Google does not report the query for a share of clicks; it withholds rare queries to protect searchers’ privacy. For windsor.ai in October 2026, web search recorded 93,203 clicks, and the rows that carry a query added up to 65,213 of them (70%).

Through the API, split by device, windsor.ai had 59,758 different queries that month. The 1,000 queries with the most clicks, the most a CSV export holds, had 97% of those query clicks and 64% of their impressions. The other 36% of query impressions came from queries a CSV export leaves out.

Method: Search Console API through Windsor.ai, pulled on 4 November 2026 for 1 to 31 October, web search type. The site total comes from a request by device; the query counts come from one request by query and one by query and device.

Claude answer through Windsor.ai: windsor.ai had 93,203 web search clicks in October 2026, 65,213 of them in rows with a query, a 30% gap

Claude’s answer in claude.ai on 4 November 2026, through the Windsor.ai connector. Its totals match the API pull above.

Checks before acting on a number

  • Ask for one property, one date range and one search type at a time, and name the fields you want.
  • Compare the property total with the sum of query rows. The difference is the clicks Google reports without a query.
  • Ask a second chat to recompute the figure from the raw rows, and open the Performance report when a number looks even slightly off.

FAQs

Is there an official Google Search Console connector for Claude?

No. Google does not list a Search Console connector in Claude’s directory. Windsor.ai is a listed connector that includes Search Console, and open-source servers and other hosted services are also available.

Tired of manual Google Search Console data exports? Try Windsor.ai today to automate your reporting

Access your data from various sources in one place. Get started for free.
g logo
fb logo
big query data
youtube logo
power logo
looker logo