Are you doing SEO or Ads?
Get a free consultation with us
Stop wasting money on ads that are not working.
Get advertising that is intentional and measured properly.
- Reach your ideal target audience.
- Maximise ad spend efficiency.

The most common problem I find on an Australian site is not a technical fault at all. It is two pages saying the same thing, written at different times by different people, quietly splitting the attention that should be going to one of them. In 13 years of doing this work, I have lost count of the businesses with a blog post and a service page both trying to rank for the same phrase, and no idea which one search should be showing. The owner usually assumes it is fine because both pages still get some traffic. What they cannot see is what the pair would do if they were one page. This is a working method rather than a scare story. It covers what genuinely counts as cannibalisation and what does not, why search can pick a page you did not choose, how to detect real conflicts with data you already have, how to tell a genuine conflict from pages that are simply related, how to consolidate when that is the answer, and when the right move is to leave a page alone. The plain definition is easy to hold on to. Per the Ahrefs blog, "Keyword cannibalization is an SEO issue that happens when multiple pages on a website target the same or similar keywords." Two pages, one job, and a fight over which one should be doing it. The fight is the problem, not the overlap. When two pages answer the same question, each one collects part of the signal that a single stronger page would have collected in full. Overlap on its own is ordinary. A business page and a blog post can both mention the same service without competing, because they are trying to do different things for the reader. The line is drawn by harm. Per the Ahrefs blog, "But it's crucial to remember that you only have a real cannibalization issue when multiple pages target the same keyword and hurt a site's organic performance." If both pages are doing well, or if neither would be better alone, there is nothing to fix. Per the Semrush blog, "Keyword cannibalization occurs when multiple pages on a site target the same keyword(s) and harm each other's search visibility." The harm is the test in both definitions, and it is the test I use. Per Search Engine Journal, "Keyword cannibalization is known as such because you're "cannibalizing" your own results by splitting CTR, links, content, and (often) conversions between two pages that should be one." Split a signal two ways and neither half is strong enough to do the job. When several pages could answer the same query, search picks one to represent the group. It looks at which page best matches the query and which one carries the stronger signals, and it decides. That is not the same as deleting the others. The other pages still exist and still may rank for other queries. What has happened is that one of them has been chosen for this one. You can tell search which page you would prefer, using a canonical tag or the links between your own pages. Per Google Search Central, "You can indicate your preference to Google using these techniques, but Google may choose a different page as canonical than you do, for various reasons." The documentation puts the reason plainly. Per Google Search Central, "That is, indicating a canonical preference is a hint, not a rule." So the fix is not to argue with the choice. It is to remove the competition so there is only one sensible page to pick. Start with the report you already own. In Search Console, open the performance report, look at a query, and switch the view so you can see the pages. Where two or more of your own URLs collect impressions for one query, you have a candidate. Then read both pages and ask whether they answer the same question. That single view finds most real cases on a small business site, and it costs nothing but an hour. A site search for the phrase, restricted to your own domain, shows how your pages appear to the wider web. If two of your URLs appear for the same phrase with the same kind of title, that is worth a closer look. For a larger site, group the pages that share a theme and check whether any group has more than one page competing for the same head term. The clustering is a shortlist, not a verdict, and each entry still needs to be read. The third check is movement over time. If a single keyword has bounced between two of your URLs across several months, the two pages are competing. A keyword that settles on one URL is not a problem, even if a second page mentions it. The fourth check is the landing page. If the page that ranks for a commercial phrase is an old blog post rather than the page you want people to buy from, the pair is misaligned, and that is a conflict worth resolving. Per the Ahrefs blog, "The trick to finding real cannibalization issues is to look for pages that target the same keywords" and then working out whether they serve the same or a very similar intent. That second half is the part a tool cannot do for you. Some queries have mixed intent, which means people using them want different things. A phrase can mean both a piece of information and a service to buy, depending on who is typing it. Where the intent is genuinely mixed, two pages can legitimately serve it. One answers the question, the other offers the service, and consolidating them would serve neither group well. This is where a mechanical check goes wrong and a person reading the query does not. A product page and a category page can look like competitors and be nothing of the sort. So can a location page and a service page that both mention the same suburb. The question is whether each page has a distinct job. If each page has a clear reason to exist and answers a different question, leave both alone. If the only difference is wording, that is the pair to look at. Consolidation means making one strong page out of two weak ones. You take the better page, move in anything useful from the other, and then deal with the page you are retiring. Do it only where the harm is real. Where two pages genuinely compete, the merged page collects the links, the content and the signals that were split between them, and that is what makes the survivor stronger than either was alone. Before a redirect goes in, check what each page ranks for. A page you think is weak may be bringing in traffic for a phrase you had not considered, and redirecting it sends that visitor to a page that does not answer their query. Also check what links to each page. Where a page has earned links from elsewhere, you want them pointing at the survivor, which a redirect handles. Write down both pages' current queries and positions before you touch anything, so you can tell later whether the change helped. Sometimes the right answer is not to merge but to rewrite one page so it stops chasing the same phrase. Give the weaker page a different job, aimed at a question it can win, and both pages stop competing. This keeps the content and any links the page has earned, while removing the overlap. It is often the better move when both pages have something worth keeping. Sometimes the honest answer is that nothing needs to change. Where the overlap is harmless, where each page serves a real audience, or where the pair performs well as it is, the correct decision is to leave it alone. I would rather say that than start a restructure for its own sake. A change that removes a page people use, in pursuit of tidiness, is a cost with no return. Before any change, record where each page stands. Note the queries it collects impressions and clicks for, its average position for the phrase in question, and any links pointing at it. Without that baseline you cannot tell an improvement from normal movement. With it, the picture over the following weeks is readable. After a merge or a rewrite, watch the surviving page's impressions and position for the target phrase, and watch overall clicks for the group of queries both pages used to serve. A short dip is common while search reassesses the change. What you want to see is the survivor settling above where either page sat before, and the traffic you expected to lose not going missing altogether. The tool that makes this repeatable is a simple query to page map. List your top twenty queries, then list the pages that collect impressions for each one. Where a query has more than one URL beside it, you have found your candidates. Keep it to one page or one spreadsheet. The value is in the pattern it shows, such as a cluster of pages all circling the same phrase after a restructure or a rebrand. Twice a year is enough for most small sites. Run it sooner after any content push, site restructure or rebrand, because those are the moments when duplicate pages get created. If you would rather have somebody work through it with you, an SEO audit that checks for competing pages covers exactly this ground, and it sits inside a wider marketing audit when you want the full picture. Where the fix needs to be worked through properly, that is working through the fix with an SEO consultant, and if you already suspect two URLs are fighting, you can send me the two URLs and I will look. Not necessarily. Pages legitimately rank for many keywords, and overlap on its own is normal. The problem only exists when two pages target the same intent and are making each other worse. If merging them would not produce a better outcome for the business, leave them where they are. Use the query and page data in Search Console. Look for one query where two or more of your own URLs are collecting impressions, then check whether both pages answer the same question. That single view finds most real cases on a small business site. It can, briefly, which is why you set a baseline and watch the right measures. Consolidation works by pushing the links and signals into one page instead of two, and the point is that the surviving page ends up stronger. Do it for genuine conflicts only, and check what each page ranks for before you redirect anything. Rarely. Deleting throws away whatever the page ranks for and whatever links into it. A redirect to the page you want to keep is usually the safer move. Delete only when the page has no value to the business at all. They can, particularly when a business adds a location page or a category page without differentiating the content. Check what each page is actually for, then give each one a distinct job or consolidate. Twice a year for most small sites, and after any content push, site restructure or rebrand, because those are the moments when duplicate pages get created. It takes an hour once you have the query to page map. Are you doing SEO or Ads? Stop wasting money on ads that are not working. Get advertising that is intentional and measured properly.What keyword cannibalisation really is
Two pages, one intent
When overlap is normal and when it is a problem
Why Google shows the page you did not choose
How Google settles on a representative page
Why your preference is a hint, not an instruction
Four ways to detect it on your site
Query and page data you already have
A site search and a host clustering check
Ranking history for one keyword
Separating real conflicts from false alarms
Keywords with genuinely mixed intent
Product, location and blog pages that should both exist
When consolidation is the right answer
Merging two pages into one
What to check before you redirect anything
When to fix it another way
Rewriting the losing page
Deciding to change nothing
Measuring whether the fix worked
Set the baseline first
What to watch over the next 90 days
A cannibalisation review you can repeat
The query to page map
How often to run it
Frequently asked questions
If two of my pages rank for the same keyword, is that cannibalisation?
How do I actually find it without expensive tools?
Will consolidating lose me traffic?
Should I just delete the weaker page?
Can my product and service pages cannibalise each other?
How often should I check?
Get a free consultation with us





Latest Blog

WINNER

FINALIST

FINALIST

WINNER

WINNER

FINALIST

FINALIST

WINNER

Xugar Holiday Offer