The playbook
Keyword Cannibalization: Checklist
Use this keyword cannibalization checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect ambiguous page assignments. Check an actual page or query record; a box marked complete without evidence does not show that the customer journey works.
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.
Before you use the checklist
Name the exact item being checked and its purpose. Gather query, URL pair, intent difference, decision. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Compare overlapping landing pages and query patterns | A dated observation showing how query was verified | SEO lead |
| Decide whether each page has a distinct purpose | A dated observation showing how URL pair was verified | content or development owner |
| Consolidate or differentiate content and internal links | A dated observation showing how intent difference was verified | analytics owner |
Check the failure path
- Look specifically for this failure: merging different buyer tasks because they share one keyword.
- Judge overlap by expected answer and audience rather than wording alone. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check decision.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Compare overlapping landing pages and query patterns,” a meeting about the subject is not the evidence itself. Retain the relevant query and URL pair, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents resolve pages that compete to answer the same search intent deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow ambiguous page assignments using a consistent definition so later reviews can connect execution quality with useful results.
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