You wrote a good post about email authentication in 2023. Then a better one in 2024, because you'd learned more. Then a third in 2025 covering DMARC specifically, which overlapped with both.
Now none of them rank well, and Google keeps swapping which one it shows.
That's cannibalisation. Your own pages competing for the same query, splitting the signals that should have concentrated on one, and all of them underperforming what a single strong page would have achieved.
It's one of the most common problems on sites that have been publishing for a few years, and one of the least diagnosed — because nothing looks broken.
The short version
Cannibalisation is when multiple pages on your site target the same query and intent, dividing your internal links, external links, and relevance signals between them.
Detect it by filtering Search Console for a query and checking how many of your pages appear, or by running a site: search.
Three fixes:
- Merge — combine into one strong page, redirect the rest
- Differentiate — genuinely separate the intents
- Redirect — kill the weaker page entirely
Merge is right more often than people expect.
What it isn't
Two clarifications first, because both cause unnecessary panic.
It isn't a penalty. Google doesn't punish you for it. What happens is subtler: Google picks one page and mostly ignores the others, and the one it picks may not be the one you'd have chosen. Your links and authority end up spread across URLs rather than concentrated.
Multiple pages ranking for one query isn't automatically a problem. If you legitimately have two pages appearing for a broad term and both are useful, you're occupying more of the results page. That's a win.
The problem is specifically when pages compete for the same query with the same intent — where one page should exist and three do.
How to spot it
Three methods, cheapest first.
1 — The site: search
site:yourdomain.com email authentication
Look at what comes back. Several pages covering substantially the same ground with the same intent is your answer, and it takes thirty seconds.
2 — Search Console (the reliable method)
Performance → Search results. Filter by a specific query, then switch to the Pages tab.
If several of your pages show impressions for that one query, they're competing.
The stronger diagnostic is position instability over time. Filter to the query, look at the position chart over six months, and watch for it swinging — 8, then 14, then 9, then 17. That oscillation is Google switching between your pages, unable to decide which one to trust.
A single page with a stable position isn't cannibalising. A query where position lurches around, with multiple pages appearing, almost certainly is.
3 — The intent test
For any two pages you suspect, ask: would the ideal answer to this query be the same page?
If yes, you have one page's worth of content spread across two. If no — genuinely different questions — you're fine.
Fix 1 — Merge
The right answer most of the time, and the one people resist because deleting work feels wrong.
When: the pages cover the same ground with the same intent, and neither is comprehensive on its own.
How:
- Pick the winner. Usually the page with more external links, better existing rankings, or the better URL. Check Search Console for which one Google already prefers — that's a strong hint.
- Move the good material across. Take what the other pages do better and fold it into the winner. Merging should produce a page better than either original, not just a longer one.
- 301 the losers to the winner. Not delete — redirect, so their accumulated authority transfers.
- Update internal links so nothing points at the redirected URLs.
- Resubmit the winner in URL Inspection.
The mistake: concatenating both posts into one long page with two introductions and repeated sections. Merging is an edit, not a paste.
Fix 2 — Differentiate
When: the pages should be separate, but you've blurred them.
Say you have "email authentication guide" and "how to set up DMARC." Those are legitimately different — one is a subject overview, one is a specific procedure. But if both open with the same 800 words explaining SPF, DKIM, and DMARC, you've made them compete.
How:
Give each a distinct primary query and stick to it. Cut overlapping sections from the narrower page and link to the broader one instead. Make titles and H1s unmistakably different. Then link them explicitly — the specific page up to the overview, the overview down to the specific page.
This is the pillar-and-spoke relationship working properly. The pillar summarises and links out; the spoke goes deep and links back. Done well, they reinforce each other instead of competing. The model.
Fix 3 — Redirect and remove
When: one page is genuinely redundant — thin, outdated, or superseded — and has nothing worth merging.
How: 301 it to the best equivalent page. Update internal links pointing at it.
Not: delete it and leave a 404. That throws away any links it had earned.
Worth including in this category: thin tag and category archives. A tag page listing two posts, competing with those posts for the same term, is cannibalisation you can fix with a noindex. The setting.
Preventing it
Cheaper than fixing it, and it's a habit rather than a system.
Keep a keyword-to-page map. A simple sheet: query, page, date published. Before writing anything new, check whether it's already covered. Thirty seconds, prevents most of this.
Search your own site before writing. site:yourdomain.com [your topic]. If you've substantially covered it, update that page rather than writing a new one.
Default to updating over publishing. On an established site, improving the existing page is usually the better move anyway — it carries authority and history a new URL doesn't. The refresh process.
Plan clusters up front. Decide which page owns which query before you write, rather than discovering the overlap two years later.
Does it always hurt?
No, and it's worth being proportionate.
Genuinely harmful: two pages with the same intent for a commercially important query, position oscillating, neither ranking well. Fix it.
Mostly harmless: slight overlap on a peripheral topic where one page clearly dominates and the other picks up occasional impressions. Leave it.
Actively good: two distinct pages both ranking on page one for a broad query. You're taking more of the results page.
The trigger for action is instability plus underperformance on a query you care about. Absent that, cannibalisation is usually a tidiness concern rather than a traffic one, and there are better uses of an afternoon.
Frequently asked questions
How do I find keyword cannibalization?
Filter Search Console by a specific query, then check the Pages tab to see how many of your pages get impressions for it. The stronger signal is position instability — a query whose average position swings between, say, 8 and 17 over months usually means Google is alternating between your pages. A site:yourdomain.com [topic] search is a faster rough check.
Should I merge or redirect?
Merge when both pages contain material worth keeping and neither is comprehensive alone — combine them into one better page and 301 the losers. Redirect and remove when one page is genuinely redundant with nothing worth salvaging. Either way, use a 301 rather than deleting, so accumulated authority transfers rather than evaporating.
Does cannibalization always hurt?
No. Slight overlap where one page clearly dominates is usually harmless, and two genuinely distinct pages both ranking on page one for a broad query is a good outcome — you're occupying more of the results page. The problem is specifically same-intent competition on a query that matters, showing as unstable positions and underperformance. That's worth fixing; mild overlap generally isn't.
What to do next
Pick the query that matters most to your business. Filter Search Console to it and look at the Pages tab.
If more than one of your pages is showing impressions, check the position chart over six months. If it's swinging around rather than holding steady, you've found the problem — and merging is probably the answer.
Free: The SEO audit checklist.
Related guides
- Keyword research without expensive tools — mapping queries to pages properly
- How to refresh old blog posts — the merge process in detail
- Internal linking and topic clusters — differentiation done right
- Technical SEO — redirects and canonicals
Join the Newsletter
Get practical marketing tactics delivered straight to your inbox.
Written by
Muhammad Basim
Related Articles
Mining Search Console for Keywords You Already Half-Rank For
There's a list sitting in your Search Console right now of keywords Google has already decided you're relevant for, where you're ranking just badly enough that nobody sees you. Nobody looks at it. Everybody buys a keyword tool instead. Those queries — roughly positions 8 through 20 — are the cheapest wins available on any […]
Long-Tail Keywords: Where a New Site Should Actually Start
Every new site owner wants to rank for the two-word term. "Email marketing." "Project management." "Running shoes." And every new site owner is competing there against domains with fifteen years of links, full-time content teams, and a brand people already search by name. You will not win that this year. You may not win it […]
How to Read a SERP and Know If You Can Rank
There's a number in every SEO tool that tells you how hard a keyword is to rank for. It's usually wrong in interesting ways. Not fabricated — it's mostly measuring the link profiles of the pages currently ranking, which is a real input. But it can't see whether those pages are any good, whether they […]