# Cluster Search Console queries by intent

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Query clustering as the bridge from ten thousand rows to a content plan.

**Intent.** The site's queries grouped into themes a strategy can address.

## When to use

- Content planning.
- Making sense of a large query set.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: Search Console

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Cluster queries over the window. — tools: `gsc_cluster_queries`
2. Attach clicks and positions per cluster and rank opportunity. — tools: `gsc_query_search_analytics`

## Decision rules

- **When** A cluster holds positions 4-10 at volume → **conclude** The classic opportunity band: content and links there beat new pages.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- Clusters are heuristics: spot-check membership before publishing a plan on them.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.