# Read Search Console

> Search Analytics, cannibalisation, query clustering and indexation, in plain questions.

[Guides](https://www.getmcpads.com/guides)

## For you

## The way this normally goes

- 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 assistant

- 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 from

### Performance

```text
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?
```

### Structure

```text
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 uses

| Tool | Why |
| --- | --- |
| `gsc_query_search_analytics` | The core query, planned around the API's row limit. |
| `gsc_detect_cannibalization` | Query and page pairs where two URLs compete. |
| `gsc_cluster_queries` | Groups what is left by intent rather than by string. |
| `gsc_monitor_indexation_freshness` | Sitemap totals and data freshness. |

## What it will not do

- 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

This job reads one source, across 4 tool calls. It changes nothing, so it works on every plan.

## Sequence

| Step | Tool | Purpose |
| --- | --- | --- |
| 1 | `gsc_query_search_analytics` | The core query, planned around the API's row limit. |
| 2 | `gsc_detect_cannibalization` | Query and page pairs where two URLs compete. |
| 3 | `gsc_cluster_queries` | Groups what is left by intent rather than by string. |
| 4 | `gsc_monitor_indexation_freshness` | Sitemap totals and data freshness. |

> **Note** Tools not announced in your list are reachable through `search_tools`, then `describe_tool` for the schema, then `run_tool` to execute. `run_tool` runs the same plan check and account allowlist as a direct call.

## Constraints that will refuse you

- Only the ad accounts the account owner ticked are reachable. Call `list_accounts` first 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 ask

```text
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?
```

---

This page as HTML: https://www.getmcpads.com/guides/search-console-analysis
Every page under /guides and /docs is available as Markdown: append `.md`, or send `Accept: text/markdown`.