# Check one query set for page cannibalisation

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

The targeted cannibalisation read on named queries, lighter than the full triage.

**Intent.** Whether the site's own pages compete on the queries that matter.

## When to use

- A money query underperforms its content quality.
- After publishing near-duplicate content.

## 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. Run cannibalisation detection on the query set. — tools: `gsc_detect_cannibalization`
2. For hits, read both pages' curves to pick the consolidation winner. — tools: `gsc_query_search_analytics`

## Decision rules

- **When** Two pages alternate rankings on one query → **conclude** Consolidation decision: the alternation itself costs position; name the candidate winner.

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

- Intentional variants (locales, formats) look like cannibalisation: check intent before merging.

## Output

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

## Related

- Skill: [organic-decay-triage](https://www.getmcpads.com/skills/organic-decay-triage.md)