Keyword cannibalisation is when two or more of your own pages target the same search intent, so Google cannot pick a clear winner. Instead of one strong page ranking well, you get several weaker pages splitting the clicks, links and authority between them, and your visibility suffers.
What is keyword cannibalisation?
The word "cannibalisation" makes it sound dramatic, but the idea is simple: your pages are eating each other's lunch. When two pages chase the same query with the same intent, Google has to choose between them, and it often chooses badly, or keeps changing its mind. The key word is intent. The same keyword appearing on many pages is normal and fine. The problem is only when the pages compete for the same job. For a quick definition, see keyword cannibalisation in the glossary.
Why does it hurt?
- Your links and authority are split across pages instead of concentrated on one.
- Google flip-flops between URLs for the query, so rankings are unstable.
- The weaker page can outrank the one you actually want to convert.
- Click-through and analytics get muddy, because the traffic is spread thin.
- It confuses AI answer engines too: a split, unclear winner is harder to cite than one definitive page. It is the same clarity that helps AEO.
What causes it?
Cannibalisation is almost always accidental. The usual culprits:
- Several blog posts written over time on near-identical topics.
- A category page and a product or service page targeting the same head term.
- Location or service-area pages that are too similar to each other.
- Tag, archive or filter pages that duplicate real content.
- Over-optimising many pages for one important keyword, hoping one sticks.
How do you find it?
Do not rely on gut feel, and do not chase keyword density, which is not the signal. The truth lives in two places: Search Console, where two of your pages show up for the same query or the ranking URL keeps flip-flopping week to week, and on-page prominence, where the same target sits in the title, H1 and intro of more than one page. For the step-by-step, including the exact Search Console workflow and a quick site search, see how to find keyword cannibalisation.
How do you fix it?
There is no single fix; the right one depends on intent. When two pages serve the same intent, consolidate them: merge the weaker into the stronger and set a permanent redirect so the winner inherits the signals. When they serve genuinely different intents, differentiate one so they stop competing. When they are near-duplicates that must both exist, canonicalise. Above all, review each cluster against the data first: bulk-merging on a hunch, or merging pages that actually served different intents, can cost you more than the cannibalisation did.
For the full playbook, how to choose between the fixes, the step-by-step for each, and how to confirm it worked, see how to fix keyword cannibalisation.
How do you prevent it?
Prevention is a keyword map: one primary target per page, written down, and checked before you publish anything new. Keep a simple content inventory so you can see, at a glance, whether a new page overlaps an existing one. A little mapping discipline saves a lot of untangling later.
How does Limecube help?
Finding cannibalisation by hand across a large site is slow and error-prone. Limecube's Site Audit crawls your sitemap into a page-by-page inventory, then finds cannibalisation clusters using Search Console overlap and on-page prominence, not density, and turns each one into a plain-English Action Plan: which page should win, and what to change on the others. The features tour shows it, and pricing starts with a 7-day trial.