The playbook
Keyword Cannibalization: Template and Field Guide
This keyword cannibalization template turns a broad task into a record another person can use. It captures query, URL pair, intent difference, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| query | Record the query associated with this page or query record. Use a stable reference so later updates can be matched. |
| URL pair | Record the URL pair associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| intent difference | Record the intent difference associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| decision | Record the decision associated with this page or query record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with query. Use the same reference throughout the record so notes are not attached to the wrong item. Then compare overlapping landing pages and query patterns. This establishes the information required before the worksheet becomes a request for action.
Next, decide whether each page has a distinct purpose. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as merging different buyer tasks because they share one keyword, rather than a broad instruction to “improve performance.”
Finally, consolidate or differentiate content and internal links. Put judge overlap by expected answer and audience rather than wording alone in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Merging different buyer tasks because they share one keyword |
| Action | Judge overlap by expected answer and audience rather than wording alone |
| First check | Compare overlapping landing pages and query patterns |
| Follow-up check | Consolidate or differentiate content and internal links |
| Outcome to define | ambiguous page assignments |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If URL pair changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep ambiguous page assignments connected to the item so the team can later assess whether the action was useful.
Keep page purpose visible throughout the work. A technically valid page can still fail to answer the reader’s question. Separate access and discovery problems from content problems so that the assigned action matches the cause.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now