Content cannibalization decision record
Key takeaways
- Name the content cannibalization decision record owner and reader task.
- Preserve sources, exceptions, and approval boundaries.
- Verify the rendered route and close with dated evidence.
Operating data
Playbook
Content cannibalization decision record starts with a editorial outcome question for a site owner who sees multiple pages appearing for related queries. The recurring failure is simple: two ranking URLs do not automatically mean either article should disappear. Write down the intended reader outcome before anyone proposes an edit or assigns a release date.
The working record should contain routes, audiences, reader tasks, evidence, internal links, inbound links, conversions, canonical intent, decision, and owner. Keep the governing source beside the decision, not in a private message that another editor cannot inspect. The recurring decision inventory provides a related operating pattern for handoff.
Keep one practical limit visible throughout the handoff: Choose preservation, clearer differentiation, consolidation, or retirement and write down the reason. The support role closes administrative gaps without inventing a position the responsible editor has not accepted.
If one route has useful links but an outdated purpose, preserve its equity only through a destination that genuinely completes the same task. Preserve uncertainty instead of rounding it into polished language. A documented expiry is easier to resolve than a confident sentence whose source and owner are unclear.
Preview content cannibalization decision record on a narrow screen and inspect its heading order, link destinations, media dimensions, metadata, and byline. The blog index and sitemap must name the same canonical route before acceptance.
Close the case with checks for redirects, internal references, sitemap membership, titles, and canonical tags. Google canonicalization guidance supplies the external reference for this workflow, while site policy and the named editor control the final decision. Teams that need help maintaining the routine can request a tailored support plan.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.