How to fix keyword cannibalization

Two conditions have to hold together. The pages must target the same query, and they must serve the same intent. Miss the second and you will consolidate pages that were doing different jobs.

A comparison page and a definition page can both surface for the same term without competing, because someone typing that term might want either. What genuinely cannibalizes is two pages that answer the same question for the same kind of reader — three near-identical "best X tools" posts written eighteen months apart, or a category page and a landing page built for the same term by different teams.

This is the diagnostic that settles it, and it is free.

1. Open Performance → Search results.
2. Add a query filter for the exact term you suspect.
3. Switch to the Pages tab with that filter still applied.
4. If two or more of your URLs appear with meaningful impressions for that single query, you have candidates.

Then check stability. Compare two date ranges — a recent month against the one before it. The signature of real cannibalization is Google swapping which URL it serves: page A ranks for a few weeks, then page B, then back. That oscillation is the engine failing to settle, and it costs you the position consistency that earns clicks.

• chevron_rightBoth URLs stable, one clearly dominant — usually fine. The weaker one is picking up long-tail variants.
• chevron_rightURLs swapping between periods — genuine cannibalization; fix it.
• chevron_rightBoth URLs mid-page with neither breaking through — the classic split-authority case, and the most costly.
• chevron_rightOne URL with impressions and no clicks while the other converts — check intent before merging; you may have two different jobs.

The Search Console method verifies a suspicion you already had. It does not find cannibalization you have not thought to look for, and on a site of any size that is most of it.

For that you need to compare pages against each other rather than against queries: title and heading overlap, body similarity, and whether the internal links pointing at each use the same anchor text. The free Keyword Cannibalization Checker crawls the site and groups competing pages automatically, and the Duplicate Content Checker catches the near-duplicate cases that are cannibalization by another name.

  same intent?   traffic split?      do this
  ------------   ----------------   ----------------------------
  yes            both weak          consolidate into one page
  yes            one clearly wins   redirect the weaker to it
  no             both earn          differentiate; keep both
  no             one earns nothing  improve or remove the weak one

Consolidate

The strongest fix when both pages do the same job and neither is winning. Pick the page with the better backlink profile and the more useful URL, merge the genuinely valuable content from the others into it, then 301-redirect the rest to it. Concentrating the signals into one page is the whole point — a merged page that is simply longer, without the redirects, achieves nothing.

Differentiate

Right when the pages genuinely serve different intents but were written carelessly enough to look identical to a crawler. Rewrite titles and H1s so each targets a distinct query, cut the overlapping sections, and make sure the internal links pointing at each use different, descriptive anchors. Differentiation that stops at the title tag does not work — the body has to actually diverge.

Leave it alone

Underrated. If one page clearly dominates and the other picks up a bit of long-tail, you are not losing anything worth a migration. Consolidation carries real risk: redirects lose a little authority, and merging a page that was quietly earning is a self-inflicted wound. The bar for acting should be evidence of instability or a genuine split, not the mere existence of two related pages.

Once you have decided to consolidate, picking the wrong survivor undoes the benefit. Weigh these in order:

1. External backlinks. The page with real inbound links from other sites is almost always the survivor — that authority is the hardest thing to replace, and a redirect preserves most but not all of it.
2. Existing rankings. Check Search Console for both URLs across a wide date range. A page already ranking, even at position 30, has accumulated trust that a fresher page has not.
3. Conversions. If one page converts materially better, that often outweighs a small ranking edge — you are optimising for outcomes, not positions.
4. URL quality. A clean, descriptive, shallow URL beats a dated or parameterised one, and the URL is the thing you are committing to long-term.
5. Age and stability. All else equal, keep the older URL. It has more link history and is more likely to be the one third parties already reference.

When the criteria disagree — the older URL has the backlinks but the newer one converts — keep the URL with the backlinks and move the better content onto it. You can rewrite a page; you cannot manufacture its link history.

Cannibalization is rarely random. It clusters in predictable places, and knowing your site's pattern is faster than auditing everything.

• chevron_rightBlogs — “best X” and “how to Y” posts rewritten every year or two without retiring the originals. The single most common source, and the easiest to fix by consolidating into one maintained page.
• chevron_rightEcommerce — category pages competing with filtered or faceted URLs targeting the same term, and near-identical product variants. Decide which facets are indexable and noindex the rest.
• chevron_rightService businesses — the service × location matrix, where “plumber Springfield” and “plumber Shelbyville” differ by a place name and split every signal. Differentiate with genuinely local content or cut the matrix down.
• chevron_rightDocumentation — versioned docs where /v1/ and /v2/ pages both rank for the same feature query. Canonical to the current version rather than redirecting, since old versions still need to be reachable.
• chevron_rightSaaS — feature pages and use-case pages describing the same capability from two angles, usually written by different teams a year apart.
• chevron_rightAfter migrations — bulk imports that bring across both the old and new versions of a page. Audit immediately after, not six months later.

The documentation case is the one worth flagging, because the instinct to redirect is wrong there. Old version docs have to stay accessible for people still running that version, so a canonical to the current page consolidates the ranking signals while keeping the content reachable.

Consolidating without repairing internal links leaves the job half done, and the half left undone is the half that caused the problem.

1. Find every internal link pointing at the pages you redirected. They now hop through a 301, which wastes a little authority on every pass.
2. Repoint each one directly at the surviving URL.
3. Rewrite the anchor text so it describes the surviving page, not the merged-away one.
4. Check that the surviving page has more inbound internal links than either original had alone. If it does not, the consolidation gained you nothing structurally.
5. Re-crawl and confirm no internal links still point at redirected URLs.

Step 4 is the one that decides whether this worked. The reason cannibalization suppresses rankings is split authority, so the fix has to end with authority actually concentrated — which is a question about how authority flows through your link graph, not about which page you deleted.

• chevron_rightKeep a record of the primary query each page owns, and check it before commissioning anything new.
• chevron_rightGive each cluster one clear hub and let supporting pages target distinct subtopics — the structure described in content clusters.
• chevron_rightUse distinct anchor text per target. Identical anchors pointing at different pages is how cannibalization gets manufactured internally.
• chevron_rightAudit after migrations and bulk imports, which are where near-duplicates arrive in batches.
• chevron_rightRe-check quarterly. Cannibalization accumulates quietly as a content library grows.

Measuring afterwards is straightforward: the surviving page should show a more stable position for the target query in Search Console, and the URL swapping should stop. Expect weeks, not days — the redirects have to be recrawled and the signals reconsolidated before positions settle.

Four things this guide compresses, each of which has more to it:

• chevron_rightFinding cannibalization in Search Console — the full workflow, including regex query filters and the export ceiling that hides your long tail.
• chevron_rightWhen cannibalization is fine — the false positives, and why consolidating unnecessarily costs more than leaving it alone.
• chevron_rightCannibalization vs duplicate content — two different problems with different fixes, and what happens when you apply the wrong one.
• chevron_rightPlatform specifics: ecommerce, where facets and variants generate the competition automatically, and WordPress, where tag and author archives do.