How to analyse Search Console data with an AI assistant
Search Analytics, cannibalisation, query clustering and indexation, in plain questions.
Both readings are on this page.
For you
What the answer looks like, and what to type to get it.
The way this normally goesLink to this section
- Filter, export, repeat per dimension, then join it all yourself.
- Hit the row limit and split the query by date to get past it.
The way it goes with an assistantLink to this section
- Ask for the comparison directly.
- The gateway plans the query, splits it when the row limit demands it, and returns the join.
Prompts to start fromLink to this section
PerformanceLink to this section
Where did we lose clicks between this month and last?
Compare Web, Image and Discover for this property.
Which queries improved in position but lost clicks?StructureLink to this section
Which of our pages are competing against each other in Search?
Cluster last quarter's queries by intent.
Is anything in the sitemap not being indexed?Tools this usesLink to this section
| Tool | Why |
|---|---|
gsc_ | The core query, planned around the API's row limit. |
gsc_ | Query and page pairs where two URLs compete. |
gsc_ | Groups what is left by intent rather than by string. |
gsc_ | Sitemap totals and data freshness. |
What it will not doLink to this section
- Search Console is read only. Requesting indexing is not exposed.
- URL Inspection is capped by Google at 2,000 calls per property per day, so a bulk inspection over a large site is not possible at any price.
For your agent
The tool sequence, the parameters that matter, and what will be refused.
Both readings as Markdown: /guides/search-console-analysis.md
This job reads one source, across 4 tool calls. It changes nothing, so it works on every plan.
SequenceLink to this section
| Step | Tool | Purpose |
|---|---|---|
| 1 | gsc_ | The core query, planned around the API's row limit. |
| 2 | gsc_ | Query and page pairs where two URLs compete. |
| 3 | gsc_ | Groups what is left by intent rather than by string. |
| 4 | gsc_ | Sitemap totals and data freshness. |
Constraints that will refuse youLink to this section
- Only the ad accounts the account owner ticked are reachable. Call
list_accountsfirst rather than guessing an identifier. - Search Console is read only. Requesting indexing is not exposed.
- URL Inspection is capped by Google at 2,000 calls per property per day, so a bulk inspection over a large site is not possible at any price.
What the person is likely to askLink to this section
Where did we lose clicks between this month and last?
Compare Web, Image and Discover for this property.
Which queries improved in position but lost clicks?
Which of our pages are competing against each other in Search?
Cluster last quarter's queries by intent.
Is anything in the sitemap not being indexed?