The playbook
Keyword Cannibalization: Metrics and Measurement
Measure keyword cannibalization by defining ambiguous page assignments precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
Two pages called “local SEO checklist” and “local search optimization checklist” may answer the same task. Compare their content and search landing patterns before merging. A location service page that happens to mention local SEO has a different role and should not be combined merely for sharing words.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | ambiguous page assignments |
| Unit | What one page or query record or completed outcome represents |
| Included records | The scope identified by query and URL pair |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | analytics owner |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as compare overlapping landing pages and query patterns. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For keyword cannibalization, explain the condition before applying that calculation. If the question is whether the team can consolidate or differentiate content and internal links, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If URL pair changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying query records are complete.
- Look for this known failure: merging different buyer tasks because they share one keyword.
- Verify that the process still includes: decide whether each page has a distinct purpose.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, judge overlap by expected answer and audience rather than wording alone. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about ambiguous page assignments, not a favorable-looking number.
Keep a dated record of the page or query being examined. Search interfaces and external references can change. A saved observation should include enough context to distinguish an old issue from the current state.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now