How to Connect Google Search Console to Gemini Enterprise

To connect Google Search Console to Gemini Enterprise, authorize your Search Console property in Windsor.ai, then add Windsor.ai as a data store in the Google Cloud console. You can then ask Gemini about clicks, impressions, CTR and position by query, page, country and device. Gemini Enterprise has no Search Console connector from Google, and Windsor.ai is listed among its third-party data stores.

Search Console through Windsor.ai is read-only. Gemini can analyze the data, but it cannot submit sitemaps, request indexing or run a URL inspection. Windsor.ai’s write actions cover other connectors, such as Google Ads and Google Business Profile.

Connect Search Console to Windsor.ai on the free forever plan, no credit card: onboard.windsor.ai/app/searchconsole.

Before you start

• Gemini Enterprise Standard, Plus, Frontline or Pay-as-you-go, set up in the Google Cloud console. The Business edition has its own setup and a smaller selection of connectors.
• A Google Cloud project under your organization (Google Workspace or Cloud Identity), with billing turned on and Gemini Enterprise activated. A project created with a personal Gmail account does not work.
• The Discovery Engine Editor role on that project, or the Owner role.
• A Google account that is a user on the Search Console property.
• A Windsor.ai account. The free forever plan covers one data source. Questions that combine Search Console with GA4 or Google Ads need a paid plan after the first 30 days: from $19 a month (billed annually) for 3 sources, or $99 a month for 7. See Windsor.ai pricing.

Step 1: Connect Search Console to Windsor.ai

1. Open onboard.windsor.ai/app/searchconsole and sign in or create an account.
2. Sign in with the Google account that has access to your property and allow access.
3. Select the property. A domain property reports every URL and subdomain of the site; a URL-prefix property reports only URLs under that prefix. The two report different totals for the same site.

Step 2: Add Windsor.ai to Gemini Enterprise

You do this once per Google Cloud project, and every source you connect in Windsor.ai later uses the same data store. The full Gemini Enterprise setup guide covers each screen, encryption keys and error messages.

1. In the Google Cloud console, open Gemini Enterprise, click Data stores, then Create data store. Under Third-party data sources, find Windsor.ai and click Add data source.
2. Under Entities to search, select Connectors. On the Actions step, Search Console questions work with both actions off. Turn on Execute Action only if you also want Gemini to make changes in a source that supports them, such as pausing a Google Ads campaign.
3. Select the location. Google recommends global unless your organization must keep data in the US or EU, and the location cannot be changed later. If the console asks you to configure access control, choose Google Identity if your company signs in with Google accounts.
4. Keep General pricing, click Create, and wait until the data store shows Active. Google bills the data store to your Google Cloud billing account, separately from Windsor.ai.
5. Open a Gemini Enterprise app in the same location, or create one under Apps. Click Connected data stores, then Add existing data stores, select the Windsor.ai data store and click Connect.
6. Open the app’s web app URL. Click the puzzle piece icon below the Ask Gemini Enterprise box, click Authorize next to Windsor.ai, then Allow Access, and sign in to Windsor.ai. Click Finish and check that the Windsor.ai toggle is on.

The Windsor.ai data store is in public preview under Google’s Pre-GA terms. Data can take about 10 minutes to appear after you connect the data store to the app.

Step 3: Check the connection with a number you know

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

Compare the totals with the Performance report in Search Console for the same dates. Search Console data is usually 2 to 3 days behind. A “last 7 days” question may cover only four or five days with data, and asking for the latest date shows which.

What Search Console data Gemini can use

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

Two limits come from Google and apply to every tool that uses the Search Console API, Windsor.ai included. Google does not report rare queries, to protect searchers’ privacy, and totals by query are lower than the property total for that reason. One request also returns only Google’s top rows. For long-tail questions, ask Gemini to split the request, for example by device or by month. The full list is in the Search Console field reference.

Questions to ask Gemini about your Search Console data

Queries close to page one

List queries with an average position between 11 and 20 and at least 500 impressions in the last 28 days. Show clicks, CTR and the ranking page, and tell me whether another of our pages also gets impressions for the same query.

The second part flags two of your own pages competing for one query before you rewrite either.

Pages losing visibility

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

Search Console keeps 16 months of data, but Windsor.ai’s free forever plan returns only the last 30 days of it, and this 56-day comparison and the 3-month questions below need a paid plan.

Clicks by site section

Group clicks and impressions for the last 3 months by the first path level of the URL, month by month.

Windsor.ai adds the path levels. When your sections are separate folders, “how is the blog doing compared with the product pages” becomes one question.

Branded and non-branded clicks

Split clicks for the last 3 months into branded and non-branded queries, month by month. Treat any query matching this pattern as branded: [your brand name and its common misspellings].

Windsor.ai’s branded field only looks for the domain name in the query. If people misspell your brand, give Gemini your own pattern.

Search Console next to GA4 and Google Ads

With GA4 or Google Ads connected in the same Windsor.ai account, Gemini can answer questions that one tool alone cannot:

• For our top 20 landing pages from organic search, compare Search Console clicks with GA4 organic sessions and key events for the last 28 days.
• List Google Ads search terms with spend in the last 30 days where we also rank in the top 3 organically for the same query, with paid clicks, organic clicks and cost.

Search Console counts clicks and GA4 counts sessions, and the two never match exactly. A page where the gap is much larger than on the others is worth checking. Combining sources needs a paid Windsor.ai plan (see Before you start).

Other ways to bring Search Console into Gemini

• Gemini CLI with an open-source Search Console MCP server. It runs on your computer with your own Google Cloud credentials, and some servers include URL inspection. The servers and their setup are compared in Google Search Console MCP.
• Other connectors in Gemini Enterprise’s third-party list also offer Search Console data. Compare which sources each one covers and how it is priced.
• A CSV export from the Performance report works for one question about one period, within its 1,000-row limit.

Troubleshooting

Your property is not in the list in Windsor.ai

Windsor.ai lists only the properties that the Google account you signed in with can open in Search Console. Sign in again with that account, tick the Search Console permission on Google’s consent screen, and select the property before you click Finish. If a different Google account has the property, connect it as a second account, or ask a property owner to add yours under Settings, then Users and permissions (a restricted user can read Performance data).

Gemini reads Search Console but will not pause a Google Ads campaign

Changes need two settings. In the Google Cloud console, open the data store, click Actions and make sure Execute Action is enabled; after you change it, click Reload custom actions. In Windsor.ai, Write actions must be on for your user, which you set when you authorize Windsor.ai in the web app. Search Console has no write actions; the list of write actions shows which sources have them.

Conclusion

Once Steps 1 and 2 are done, Gemini Enterprise answers questions about your Search Console queries, pages and sitemaps, and about GA4, Google Ads and any other source you connect in Windsor.ai. Start with the check question in Step 3, then the page-one and losing-pages questions above.

• The open-source servers and the checks to run before trusting an answer: Google Search Console MCP.
• The same setup for ChatGPT: how to connect Google Search Console to ChatGPT.
• The Claude version: how to send Google Search Console data to Claude.
• Every screen of the Google Cloud setup: Gemini Enterprise setup guide.
• Other sources you can add: Gemini Enterprise connectors.

Start with Search Console on the free forever plan, no credit card: onboard.windsor.ai/app/searchconsole.