RecipeSearch Console
Cluster Search Console queries by intent
Query clustering as the bridge from ten thousand rows to a content plan.
IntentThe site's queries grouped into themes a strategy can address.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Content planning.
- Making sense of a large query set.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Cluster queries over the window.
Attach clicks and positions per cluster and rank opportunity.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
A cluster holds positions 4-10 at volume
Conclude
The classic opportunity band: content and links there beat new pages.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Clusters are heuristics: spot-check membership before publishing a plan on them.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.