RecipeSearch Console
Check one query set for page cannibalisation
The targeted cannibalisation read on named queries, lighter than the full triage.
IntentWhether the site's own pages compete on the queries that matter.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- A money query underperforms its content quality.
- After publishing near-duplicate content.
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.
Run cannibalisation detection on the query set.
For hits, read both pages' curves to pick the consolidation winner.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Two pages alternate rankings on one query
Conclude
Consolidation decision: the alternation itself costs position; name the candidate winner.
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.
- Intentional variants (locales, formats) look like cannibalisation: check intent before merging.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.