calendar Last updated: 17 November 2026
Data integration
Data Pipelines
Google Search Console
How to's

How to Connect Google Search Console to Claude (Including Claude Code)

Try It Free

Connect your data in 1 min. Free forever plan

Got insights from this post? Give it a boost by sharing with others!

You can connect Google Search Console to Claude in three ways. The Windsor.ai connector takes about a minute and works in the Claude apps and in Claude Code. An open-source MCP server runs on your own computer with your own Google Cloud credentials. A CSV export works for one question about one period.

For a full comparison of the MCP options and the data checks I run before trusting an answer, see Google Search Console MCP.

Is there an official Search Console connector for Claude?

No. When I checked Claude’s connector directory on 4 November 2026, Google had five listings there (Gmail, Google Drive, Google Calendar, Google Cloud BigQuery and Google Compute Engine) and none for Search Console. Windsor.ai is a listed connector that includes Search Console; Method 1 below adds it with one click.

Other companies host Search Console servers too: Porter Metrics, Data Bloo, RightBlogger and mcpsearchconsole.com each publish a server address that you add in Claude as a custom connector. I have not tested them, so check their pages for what each one reads and costs. If your organization adds connectors by address, Windsor.ai’s is https://mcp.windsor.ai.

Three ways to connect Search Console to Claude

Method Setup Works in Best for
Windsor.ai connector Sign in, pick the property, add Windsor in Claude Claude web, desktop and mobile apps, Claude Code Daily analysis, and Search Console next to GA4 or ad data
Open-source MCP server Google Cloud project, OAuth client, uv Claude Desktop, Claude Code URL inspection and sitemap management
CSV export and upload Export from the Performance report Any Claude chat One question about one period

Method 1: the Windsor.ai connector

Before you start

  • A Windsor.ai account. The free forever plan covers one data source, with no credit card.
  • A Google account with access to the Search Console property.
  • A Claude account on any plan.

Step 1: connect Search Console to Windsor.ai

Go to onboard.windsor.ai, choose Google Search Console, sign in with Google and select the properties you want to use in Claude. Pick the property type you use in Search Console: a domain property (sc-domain:example.com) includes every subdomain and protocol, a URL-prefix property only the URLs under that prefix. I always pick the domain property for windsor.ai, because a cannibalization check needs every URL that gets impressions for a query, and a URL-prefix property shows only part of them.

Connect your Search Console account in Windsor.ai with Grant Search Console Access

Step 2: add Windsor.ai in Claude

In Claude, select Plugins in the sidebar, search for Windsor and click Add. Sign in to your Windsor.ai account when prompted. You can also open the Windsor.ai listing in Claude’s directory and click Add. The connector you add on claude.ai is also available in the Claude desktop and mobile apps.

The Windsor.ai connector in Claude's connector directory

The first time Claude calls the connector in a chat, it asks for permission. Allow once approves that call only; Always allow stops the question for that tool. I use Allow once when I want to see every request Claude makes, for example when I am checking how it built a number.

Claude asking to use a Windsor.ai tool, with Deny, Always allow and Allow once

Step 3: check the connection with a number you know

Using Windsor, show clicks and impressions for [property] for the last 28 days. Tell me the latest date in the data.

Compare the answer with the Performance report for the same dates. Search Console data is usually 2 to 3 days behind, and the delay can be longer during reporting incidents, so ask for the latest date every time.

Claude reporting that the latest Search Console date for windsor.ai is 28 September 2026, with clicks and impressions for the seven most recent days

Claude’s answer on windsor.ai, 1 October 2026. A calendar “last 7 days” held only four days with data, so Claude said so and used the seven most recent days.

In Claude Code

Install the Windsor.ai plugin from Anthropic’s official plugin marketplace, which Claude Code includes by default:

claude plugin install windsor-ai@claude-plugins-official

Or add Windsor’s MCP server directly from your terminal:

claude mcp add --transport http windsor https://mcp.windsor.ai

Either way, Claude Code asks you to sign in to Windsor.ai the first time, and every Search Console property you connected in Step 1 is available. The prompts in this guide work the same in the terminal.

Method 2: an open-source MCP server

Google does not publish a Search Console MCP server, so this route uses community code. It needs a Google Cloud project with the Search Console API enabled, an OAuth Desktop client, and uv to run the server. The server asks for full read and write access to Search Console, so add it only for people who should be able to change Search Console settings.

Use this route if you need URL inspection from Claude (index status, last crawl, canonical), which the Windsor connector does not have. The full setup for Claude Code and Claude Desktop, with the configuration and the scope warning, is in Google Search Console MCP.

Method 3: CSV export and upload

  1. In Search Console, open Performance, then Search results.
  2. Set the date range and search type.
  3. Click Export, then Download CSV. The download is a ZIP with one file per tab (Queries, Pages, Countries, Devices, Search appearance, Dates) plus the chart and filter settings.
  4. Upload the files you need to a Claude chat and say what each one is.

The interface exports at most 1,000 rows per table, and each file is a snapshot of one period. For a site with many queries, the long tail is missing, and comparing two periods means two exports.

I measured what that leaves out on windsor.ai for 2 to 28 September. The Performance report table stops at 1,000 queries (“1-10 of 1000”), the same limit as the export. Through the Windsor connector, the same dates held 54,577 queries once the request was split by device; a single request returned 21,228, because Google returns only its top rows. Sorted by clicks, as the export is, the 1,000 queries in the export brought most of the clicks but only 55% of the impressions. The other 45% came from more than 50,000 smaller queries, about 1,750 of which also brought clicks. For a report on clicks the export is close; for long-tail or impression work it is not.

Search Console Performance report for windsor.ai, 2 to 28 September 2026: 71.8K clicks, 4.44M impressions, and a Queries table capped at 1,000 rows

The Performance report for windsor.ai, 2 to 28 September 2026. The query rows are not shown.

For history past 16 months

The Search Console API keeps 16 months, and so does every connector built on it. For longer history, I have worked a lot with Search Console data stored in BigQuery: it keeps every day you load, and on large sites it can return answers faster than the API. Google’s bulk data export writes Search Console data to BigQuery every day from the day you set it up, with no backfill. Claude can read those tables through the Google Cloud BigQuery connector in its directory, or through Windsor.ai’s BigQuery connector.

What Claude can analyze through Windsor

Data Fields
Search performance Clicks, impressions, CTR and average position by query, page, date, country, device, search type and search appearance
Fields Windsor adds Branded or non-branded (domain name in the query), words in the query, results page number, URL path levels (pathlevel1 to pathlevel4), page path, hostname
Sitemaps Submitted URLs, errors, warnings, last download and last submission per sitemap

The connector does not include URL Inspection or the Page indexing report, so Claude cannot tell you why a specific URL is not indexed. Search Console is read-only through Windsor.ai: Claude can analyze it and draft changes, and you make them in Search Console. The full list is in the Search Console field reference.

Prompts to start with

I use the connector almost every day. The question I ask most is whether a content update worked, so it comes first.

Did a page update work?

I updated [page URL] on [date]. Compare the 21 days before and after, ending three days ago: queries that are new with impressions, the average position of the 5 queries with the most impressions before the update, and CTR. Tell me whether the page is moving toward or away from where it was.

When a page moves away from its target, I look at what else changed in the same weeks: competitors’ pages, new Google features on the results page, or a shift in how people phrase the query. Some of that comes from other connectors in the same chat, for example Ahrefs.

Queries close to page one

Using Windsor, list queries with an average position between 11 and 20 and at least 1,000 impressions in the last 28 days, ending three days ago. Show clicks, CTR and the page that ranks for each. For each query, tell me whether another of our pages also gets impressions for it.

On windsor.ai in September this returned 19 queries with 36,214 impressions and 17 clicks between them. I ask the second half because when two of our pages share a query, the fix is usually to update or merge the weaker page, and a new article would add a third.

Claude answering the page-two queries prompt on windsor.ai Search Console data through the Windsor.ai connector: 19 queries, 36,214 impressions, 17 clicks

Claude’s answer on windsor.ai’s Search Console data, 1 October 2026. The query table below the summary is not shown.

Pages losing visibility

Show the pages that lost the most impressions in the last 7 days compared with the 7 days before. For each page, list the queries that lost position and the queries that lost the most impressions.

Titles that underperform their position

Show pages with more than 2,000 impressions in the last 28 days whose CTR is below the average for their position on our site. Suggest two new titles for each, based on the queries they rank for.

Sitemap problems

List our sitemaps with submitted URLs, errors, warnings and the last download date. Flag any sitemap Google has not downloaded in the last 7 days.

More prompts, including the ones I use every week, are in Google Search Console MCP.

Search Console data not showing in Claude?

  • Property mismatch. The property selected in Windsor.ai (domain or URL-prefix) must be the one you want to analyze. A URL-prefix property only reports URLs under its prefix.
  • Fresh data. Search Console finalizes a day about 2 days later. Ask Claude to include fresh data if you need the last day or two; Google can still change those figures.
  • Permissions. The Google account you signed in with must have access to the property in Search Console.
  • Totals that look low. Rows that carry a query add up to less than the site total, because Google hides rare queries. On windsor.ai in September, rows with a query covered 68% of clicks. Ask Claude whether a total is for all clicks or for clicks with a query.

Still stuck? See the troubleshooting guide.

Checks before you act on an answer

I have not had a wrong number from these prompts, and I think that is mostly because I name the property, the date range, the search type and the fields in every request. I recommend three habits:

  • Be specific. One property, one date range and one search type per question, and the fields you want by name.
  • Have a second agent check the first. Ask a new chat to recompute the figure from the raw rows, without showing it the first answer.
  • Open Search Console when something looks off. Check even a small gap in the Performance report before you change a page.

Two limits come from the connector itself. The search type field covers web, image, video and news, and Discover and Google News traffic are not included. Search Console has no write actions through Windsor.ai. Some other connectors, such as Google Ads and Meta Ads, do; the write actions documentation lists them per connector.

Analyze Search Console next to GA4 and Google Ads

With more than one source connected in Windsor.ai, one prompt can join them:

  • Search Console and GA4. Which pages get organic clicks but few engaged sessions. Check that both sources use the same form of the URL first; the GA4 to Claude guide covers the GA4 side.
  • Search Console and Google Ads. Queries you pay for while you already rank in the top three organically.

The free forever plan covers one source. Using two or more sources after the first 30 days needs a paid plan, from $19 a month for three sources or $99 a month for seven. See pricing.

Conclusion

For daily work in Claude, add the Windsor.ai connector: sign in, pick the property, add Windsor in Claude, and check one number you know. Add an open-source server only if you need URL inspection, and limit who gets it. Use a CSV export for a single question. Before acting on an answer, ask for the latest date in the data and whether a total includes the hidden queries.

For the comparison of MCP options and the checks I run, read Google Search Console MCP. The Search Console to Claude connector page has our October 2026 measurement of what the API returns beyond the export. For the method I use on competing pages, read how I catch content cannibalization with Claude. If your team works in ChatGPT, the plugin setup is in how to connect Google Search Console to ChatGPT. Teams on Gemini Enterprise can follow how to connect Google Search Console to Gemini Enterprise.

🚀 Connect Search Console to Claude with Windsor.ai. Free forever plan, no credit card. Try Windsor.ai.

FAQs

Is there an official Google Search Console connector for Claude?

No. Google has no Search Console connector in Claude’s directory. The Windsor.ai connector is listed there and includes Search Console; other vendors and open-source projects offer servers you add yourself.

Tired of juggling fragmented data? Get started with Windsor.ai today to create a single source of truth

Let us help you automate data integration and AI-driven insights, so you can focus on what matters, growth strategy.
g logo
fb logo
big query data
youtube logo
power logo
looker logo