How can I use Google Search Console data from Claude or ChatGPT?
There are three ways. Export the Performance report and upload the file to the assistant; call the Search Console API with a script; or connect an MCP server that reads your property for the assistant. Uploads are simplest but manual, the API needs code, and an MCP server lets the assistant ask for fresh data itself.
By SEOBolt. Published , updated .
Why this happens
Claude and ChatGPT cannot log in to your Search Console account on their own, and they should not. Search Console data is private to the verified owners of a property, so any route has to hand the assistant either a file you exported, or a credential with limited, read-only access.
The three routes differ in how much of your data the assistant sees and who does the work. An upload is a snapshot: whatever you exported, up to the limits of the export. The API is the most complete source: Google documents a maximum of 25,000 rows per request and 50,000 rows of data per day per search type, sorted by clicks, and some data can be dropped when you group by both page and query. An MCP server wraps those API calls in named tools so the assistant can request exactly the analysis you ask for, without you writing queries.
Whichever route you choose, remember what the data is. Search Console reports averages for queries that already produced impressions. It does not tell you your rank for a keyword nobody searched, and its numbers are reported with a delay of a couple of days.
How to do it, step by step
Start with the upload route: it needs no setup and shows whether an assistant adds value for your questions.
1. Export the data
In Search Console open Performance, then Search results. Set a date range, pick the Queries tab (and again for Pages), and use the Export button to download the table. Google's help page says the export button downloads both chart and table data.
2. Upload it and ask specific questions
Ask things a spreadsheet makes tedious: which queries have more than 100 impressions and an average position between 8 and 15; which pages lose clicks versus the previous period; which queries are brand versus non-brand. Ask it to show its working so you can check a few rows by hand.
3. Move to the API when exports stop being enough
The API lets you pull up to 25,000 rows per request and page through results with startRow. Google recommends running one query a day for one day of data to stay inside quota, and notes data is typically available after two to three days.
4. Use read-only access for anything automated
Whatever tool you connect, grant read-only access. Search Console's read-only scope is webmasters.readonly: it can read performance data and cannot change your property.
5. Connect an MCP server for conversational use
An MCP server turns the API into tools an assistant can call. You add the server URL as a connector in the assistant, sign in once, and ask in plain language. You still review what the assistant proposes before any change goes live.
6. Keep a human check on conclusions
Search Console figures are averages and samples. Before acting on a recommendation, open the page, look at the query in a private window, and confirm the change makes sense for the reader.
The three routes compared
| Route | Setup | Data scope | Main limit |
|---|---|---|---|
| Export and upload | None: click Export, attach the file | What you exported: one view, one date range | A snapshot; you repeat it for every refresh |
| Search Console API script | Google Cloud credentials and code | Up to 25,000 rows per request; 50,000 rows per day per search type | Needs code; some data is dropped when grouping by page and query |
| MCP server on your account | Add the connector, grant read-only access | Whatever the server's tools request via the API | Limited to the tools the server provides |
When to use SEOBolt for this
SEOBolt's MCP server includes nine Search Console tools that read your connected property read-only (webmasters.readonly) and return suggestions only: seo_gsc_reality (why pages get or lack traffic), seo_gsc_content_opportunities (keywords you rank for but do not target), seo_gsc_cannibalization, seo_gsc_content_decay, seo_gsc_low_ctr, seo_gsc_repoint, seo_gsc_secondary_keywords, seo_gsc_prune_candidates and seo_gsc_index_coverage. Each takes a property id such as sc-domain:example.com. They need Google sign-in on your SEOBolt account and a plan that includes the Search Console integration; /pricing shows which.
If you do not want to connect an account yet, the free GSC Keyword Opportunities tool at /tools/gsc-keyword-opportunities accepts an uploaded export, which is the same upload route described above with a purpose-built analysis.
MCP tools involved: seo_gsc_reality, seo_gsc_content_opportunities, seo_gsc_cannibalization, seo_gsc_content_decay, seo_gsc_low_ctr, seo_gsc_index_coverage.
When SEOBolt is not the right tool
SEOBolt's Search Console tools are read-only and suggest changes; they cannot submit sitemaps, remove URLs or edit anything in your property. If you need an assistant with write access to Search Console itself, use Google's own API with your credentials.
Prompt to give your AI assistant
With the SEOBolt MCP server connected (setup), copy this into Claude, ChatGPT, Cursor or Gemini CLI:
Assign to SEOBolt: for sc-domain:example.com run seo_gsc_reality and tell me the real growth bottleneck, then run seo_gsc_content_decay and list the pages losing the most clicks with the cause for each. These tools only read data. Show me what you did so I can approve any change to the site.
Frequently asked questions
Can ChatGPT or Claude access my Search Console directly?
Not without you granting access. You either give the assistant a file you exported or connect a tool, such as an MCP server, that holds read-only credentials for your property.
Is the Search Console data complete?
Not entirely. Google documents a maximum of 50,000 rows per day per search type through the API, and says some data may be dropped when you group by both page and query.
How fresh is the data?
Google says data is typically available after two to three days, and the newest data can be preliminary.
Will the assistant change my site or my property?
SEOBolt's Search Console tools are read-only and return suggestions. Any change to your site happens in your own repository or CMS after you approve it.
Sources
- Search Console Help: Performance report (Search results), read 13 November 2026
- Search Console API: Getting your performance data, read 13 November 2026
- Search Console API: Usage limits, read 13 November 2026