Google Search Console Connector

Q: Where are the setup guides for each destination?

Setup guides: Claude , ChatGPT , MCP servers and Data Studio . Reference: the field reference and the Search Console API guide . Each destination card above links its own setup page.

Windsor.ai connects Google Search Console to your warehouse, BI tool, spreadsheet or AI assistant through the Search Console API. You get clicks, impressions, CTR and position by query, page, country, device and date, with no exports: synced on a schedule to warehouses and reports, or pulled when you ask in Claude or ChatGPT.

Because the data comes from the API, your reports are not limited to the 1,000 rows the Performance report shows, and a warehouse can keep the history after Search Console’s 16 months.

No code. Free forever plan for one data source.

Try It for Free View documentation

Free forever plan

No credit card needed

Make the most out of your Google Search Console data with Windsor.ai

Every Search Analytics dimension and metric from the API, plus fields Windsor adds: branded vs non-branded, words in the query, results page number and URL path levels.

10 metrics43 dimensions

Search Query Page Path Clicks and Impressions Branded vs Non-branded Sitemaps

Data fields documentation

Start from a ready-made Search Console dashboard template for Data Studio, Power BI or Google Sheets, then change the fields and filters to match your site.

View all templates

Send your Google Search Console data to any destination

Import your Google Search Console data into any destination using Windsor.ai.

Data Studio

Learn more

Google Sheets

Learn more

ChatGPT

Learn more

Claude

Learn more

Power BI

Learn more

Excel

Learn more

Tableau

Learn more

Google BigQuery

Learn more

Amazon S3

Learn more

Azure Blob Storage

Learn more

Snowflake

Learn more

MySQL

Learn more

PostgreSQL

Learn more

Python

Learn more

Azure SQL

Learn more

Amazon Redshift

Learn more

Databricks

Learn more

Windsor MCP

Learn more

Microsoft Fabric

Learn more

Copilot Agent

Learn more

Perplexity

Learn more

Lovable

Learn more

Antigravity

Learn more

Supabase

Learn more

What the Google Search Console connector gives you

Windsor.ai reads Search Console through Google’s API and sends the rows to the destination you choose: on a schedule to a warehouse or report, or when you ask in an AI assistant. Three things change compared with exporting from the interface:

More than 1,000 rows. The Performance report table and its export stop at 1,000 queries. On windsor.ai in September, those 1,000 queries brought most of the clicks but only 55% of the impressions; the other 45% came from more than 50,000 smaller queries. Google returns its top rows for each request, so to get that long tail, split the data, for example by device.
Query and page together, by day. Cannibalization checks and before-and-after comparisons need query, page and date in one table, which the interface does not export.
Next to your other data. GA4, Google Ads and 350+ other sources go through the same account, so you can join them with Search Console on date and URL in your destination.

Here is a query, page and date pull from the connector for windsor.ai, 22 to 28 September 2026. Two of our pages showed for “google search console mcp claude”: the Claude how-to and the MCP connect page.

Date	Claude how-to		MCP connect page
Date	Impressions	Position	Impressions	Position
22 Sep	4	4.0	4	7.3
23 Sep	9	7.9	5	7.8
24 Sep	8	5.1	2	4.0
25 Sep	3	6.7	7	7.7
26 Sep	3	1.0	5	7.6
27 Sep	7	6.6	2	9.0
28 Sep	10	3.0	6	8.0

The how-to ranked higher on five of the seven days and got the week’s only click, 44 impressions against 31. Two of our pages sharing one query is what a cannibalization check looks for. We moved the MCP comparison to its own Search Console MCP article, and the connect page will redirect there.

Two limits come from Google, so they apply in the Search Console interface and in every connector that uses the API, Windsor.ai included: Google hides rare queries (on windsor.ai, rows with a query covered 68% of clicks), and the latest 2 to 3 days are incomplete.

Search Console Performance report for windsor.ai with the Queries table capped at 1,000 rows

With the Google Search Console connector you can:

Load daily query and page data into BigQuery, Snowflake or another warehouse, where you can keep history beyond Search Console’s 16 months.
Build Data Studio, Power BI or Sheets reports from ready-made Search Console templates.
Ask Claude or ChatGPT about your search data in plain language. See the setup for Claude and ChatGPT.
Split branded and non-branded clicks, find pages that compete for the same query, and compare organic clicks with GA4 sessions or Google Ads spend.

Join over 19,000+ businesses that trust Windsor.ai to streamline Google Search Console data integration

How to export Google Search Console data with the Windsor.ai connector

Sign up and start for free

Create your Windsor.ai account and log in.

Select Google Search Console as a data source

Choose Google Search Console, sign in with a Google account that has access to the property, and select the properties. Use the domain property if you want every subdomain and protocol in one dataset.

Connect your Search Console account in Windsor.ai

Choose report fields and metrics

Select the fields that you’d like to add to your report, for example clicks, impressions, position, query and page.

Select a data destination

Choose a destination where you want to stream your Google Search Console data.

FAQs

What data can I get from Google Search Console with Windsor.ai?

Search Analytics: 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, page path, hostname and URL path levels. Sitemaps: submitted URLs, errors, warnings and last download. URL Inspection and the Page indexing report are not included. Full list: Search Console field reference.

Which AI tools integrate with Google Search Console?

Google publishes no Search Console MCP server, so AI assistants reach Search Console through third-party connectors or open-source servers. Through Windsor.ai, Search Console works in Claude, ChatGPT, Gemini Enterprise, Copilot and Perplexity, next to GA4 and ad data. The options are compared in Google Search Console MCP.

Does the connector get more than 1,000 rows?

Yes. The interface table and export stop at 1,000 rows. The API returns up to 25,000 rows per request, and only its top rows, so for a large site the request has to be split, for example by device. For 2 to 28 September 2026, our own property had 54,577 queries split by device; one unsplit request returned 21,228.

Is the data complete?

No connector or export gets every query. Google hides rare queries for privacy, so rows with a query add up to less than the site total (68% of clicks on windsor.ai in September). The last 2 to 3 days are also incomplete.

Can I combine Search Console with GA4 or Google Ads?

Yes. Connect them in the same Windsor.ai account and join on date and URL in your destination. Check that both sources use the same form of the URL: Search Console reports full URLs, GA4 page paths and hostname.

Which property type should I connect?

The domain property (sc-domain:example.com) covers every subdomain and protocol; a URL-prefix property covers only the URLs under its prefix. For site-wide reporting and cannibalization checks, use the domain property.

Can Windsor.ai change my Search Console settings?

No. Windsor.ai can make changes on some ad and social platforms, such as pausing a Google Ads campaign, but not in Search Console: the Search Console connector only reads data. It does not submit sitemaps, request indexing or change settings.

How much does it cost?

The free forever plan covers one data source, with no credit card. Paid plans start at $19 a month for three sources and $99 a month for seven. See pricing.