Google Search Console in Claude and ChatGPT: your search data in a conversation

You can now read your Google Search Console data from Claude or ChatGPT through Fezola: clicks, impressions, click-through rate and position by query, page, country or device, URL inspection and sitemaps, across several properties and Google accounts. You sign in with Google once, tick Search Console, and ask questions in plain language. Facts below are read from Fezola's tools and from Google's documentation of the Search Console API.

How to connect it

1. In the Fezola app, open Sources, add Google Search Console and sign in with Google. Tick Search Console on the Google screen. Fezola asks for one Search Console permission, which includes write access (needed to submit or remove a sitemap and add a property); accounts connected earlier in read-only mode keep reading and must reconnect to write.
2. Connect Fezola to your assistant once, at https://api.fezola.com/mcp: see how to add a custom connector to Claude. ChatGPT custom connectors are available on Business, Enterprise and Edu plans.
3. Ask a question. A short version of this article is on the Search Console connector page.

What you can ask

• "Which pages lost clicks this month compared with last month?"
• "Which queries have many impressions but few clicks?"
• "Show my top queries in France on mobile over the last 28 days."
• "Are these 10 pages indexed, and when did Google last crawl them?"
• "List my sitemaps and tell me whether any has errors."

What the tools do

• Properties. Lists every Search Console property the Google account can see, domain or URL-prefix, with the permission level. Unverified properties return no data.
• Performance. Clicks, impressions, CTR and average position, grouped by query, page, country, device, date or search appearance, with filters, a choice of search type (web, image, video, news, Discover), sorting, and a comparison with a previous period. Up to 1,000 rows per call, 100 by default.
• URL inspection. For up to 10 URLs per call: the verdict, the coverage state (for example "Crawled, currently not indexed"), the last crawl time, the canonical Google chose, and rich-result issues. It shows the status as Google last saw it, not a live test.
• Sitemaps. Lists and details your sitemaps.
• Changes (the permission includes write access): submit or resubmit a sitemap, remove a sitemap, add a property.

Limits, said plainly

• Delay. The last 2 to 3 days are often incomplete, and dates follow Pacific Time.
• Fewer rows than asked. Google returns only the top rows by clicks and anonymizes some queries.
• No indexing requests. Google's API cannot request indexing of a single URL. Resubmitting a sitemap asks Google to read it again; it does not force indexing.
• No unverified data. A property you add stays unverified until you verify it in Search Console: Fezola cannot do that for you.

Guardrails

• Mostly reading. Most tools only read. The three that change something rely on the write access included in the single permission you grant, so keep your assistant's approval prompts on, and removing a sitemap needs your explicit confirmation of that exact sitemap.
• Your assistant should ask. Keep its approval prompts on before it submits or removes anything.
• Third-party text is data. What Google returns, such as a query, is data and never instructions.
• Only what you tick. You can hide Search Console from an assistant: see choose which tools Claude or ChatGPT can see.

Several properties and accounts

Agencies and in-house teams often have properties across several Google accounts. With Fezola each Google account is a source, and one assistant works across them, as with several Google Ads accounts. For keyword data and rankings beyond your own site, see DataForSEO in Claude and ChatGPT. New to MCP? Start with what is MCP.