How to Fix Keyword Cannibalisation Between Your Pages

Keyword cannibalisation happens when two or more of your pages show up for the same Google query and split its impressions, so neither ranks as well as a single strong page would. By the end of this guide you will have found every competing query in Search Console, chosen one owner page per query, and either merged or clearly differentiated the others.

By Updated ⏱ 2-4 hours, plus 4-8 weeks for Google to re-evaluate🎯 Advanced● High impactOn-Page
Illustration: Keyword cannibalisation fix guide
ON-PAGE · FIX GUIDE Keyword cannibalisation IMPACTEFFORT TIME2-4 hours, plus 4-8 weeks for Google to re-evaluate LEVELAdvanced

Why it matters

When Google cannot tell which of your URLs best answers a query, it rotates between them. Clicks, links and engagement are split, rankings fluctuate, and the weaker page often appears instead of the one you want. AI answer engines that cite a single source per topic face the same ambiguity and may cite a thin or outdated page.

Consolidating signals onto one URL usually lifts its position and makes the right page appear more consistently in search results and AI summaries.

✕BeforeThe query "waterproof hiking boots"has 1,200 impressions in 90 days: 55%go to /blog/best-hiking-boots and 40%✓After/collections/hiking-boots gets 95%+ ofimpressions for "waterproof hikingboots"; the blog post now targets "how

What you need

Google Search Console access (Full or Owner) for the property
A spreadsheet tool or Node.js to analyse a query + page export
Access to your CMS or server to edit content and add 301 redirects
A list of your site's main topics and conversion pages

Step-by-step fix

1

Export query and page data from Search Console

The standard Performance export lists queries and pages separately, so you need both dimensions together. Options:

  • Looker Studio: add the Search Console connector, choose URL Impression, and build a table with dimensions Query and Landing Page and metric Impressions, date range last 90 days. Export as CSV.
  • Search Analytics for Sheets add-on or the Search Console API with dimensions: ["query","page"].

Save the file with columns query,page,impressions.

Pro tip: Use the last 90 days; that is the window the audit evaluates, and shorter ranges miss seasonal overlaps.
2

Flag queries where 2+ pages each get 20% or more

A query counts as cannibalised when it has at least 50 total impressions and two or more pages each receive at least 20% of them. Run the script below on your CSV, or replicate it in a sheet with a pivot (query rows, page columns, % of row total). Sort the output by total impressions so you fix the queries with the most traffic first.

javascript
// node find-cannibal.js export.csv
const fs = require('fs');
const rows = fs.readFileSync(process.argv[2], 'utf8').trim().split('\n').slice(1)
  .map(l => { const p = l.split(','); return { query: p[0], page: p[1], imp: +p[2] }; });
const by = {};
rows.forEach(r => (by[r.query] ||= []).push(r));
const hits = Object.entries(by).map(([q, rs]) => {
  const tot = rs.reduce((s, r) => s + r.imp, 0);
  const big = rs.filter(r => r.imp / tot >= 0.2);
  return { q, tot, pages: big.map(r => `${r.page} (${Math.round(r.imp / tot * 100)}%)`) };
}).filter(h => h.tot >= 50 && h.pages.length >= 2)
  .sort((a, b) => b.tot - a.tot);
hits.forEach(h => console.log(h.tot, h.q, '\n   ', h.pages.join('\n    ')));
console.log(hits.length, 'cannibalised queries');
Pro tip: If the CSV has commas inside queries, export as TSV and split on \t instead.
3

Pick one owner page for each query

Group flagged queries by the pair of pages involved; many queries usually trace back to the same few pairs. For each pair, choose the owner using:

  • Search intent: commercial queries belong on product/category pages, how-to queries on guides.
  • Performance: higher clicks, conversions and backlinks (check Links > Top linked pages in Search Console).
  • Content depth: the page that answers the query more completely.

Record the decision in a sheet: query, owner URL, competing URL, action (merge or differentiate).

Pro tip: If two pages have the same intent and neither is clearly better, merging is almost always the right call.
4

Merge duplicates with a 301 redirect

When the competing page serves the same intent, move any unique, useful content (sections, FAQs, images, data) into the owner page, then permanently redirect the old URL to it. Do not use a 302 or a canonical tag alone for pages you are retiring; a 301 passes signals and removes the URL from results. Afterwards remove the old URL from your XML sitemap.

nginx
# Nginx (inside the server block)
location = /blog/best-hiking-boots { return 301 https://example.com/collections/hiking-boots; }

# Apache (.htaccess)
Redirect 301 /blog/best-hiking-boots https://example.com/collections/hiking-boots
Pro tip: Redirect to the closest matching owner page, never to the homepage; Google treats irrelevant redirects as soft 404s.
5

Differentiate pages that should both exist

If both pages have a real purpose, retarget the secondary page to a distinct query. Change its <title>, H1, opening paragraph and subheadings so the main topic is clearly different, and remove repeated sections that answer the owner's query. The audit also compares the first significant words of each H1, so H1s like "Best Waterproof Hiking Boots" and "Waterproof Hiking Boots: Best Picks" will still be flagged; make the topic itself different.

html
<!-- Owner: /collections/hiking-boots -->
<title>Waterproof Hiking Boots | Example Co</title>
<h1>Waterproof Hiking Boots</h1>

<!-- Secondary: /blog/waterproofing-guide -->
<title>How to Waterproof Leather Hiking Boots (Step by Step) | Example Co</title>
<h1>How to Waterproof Leather Hiking Boots</h1>
Pro tip: Check the new target query in Search Console first so you retarget to something people actually search.
6

Point internal links and anchors at the owner

Internal links are a strong signal of which page you consider authoritative. Search your site for links using the target query as anchor text and make sure they point to the owner URL. Update links to merged URLs so they go directly to the destination instead of through a redirect.

Add one contextual link from the secondary page to the owner using the target query as anchor text.

text
# Find internal links to a retired URL in a static export or theme files
grep -rn "/blog/best-hiking-boots" ./public ./templates
Pro tip: Screaming Frog: Bulk Export > Links > All Inlinks, then filter the Destination column by the old URL.
7

Request recrawl and check the result

In Search Console use URL Inspection on the owner page and any differentiated page, then click Request indexing. Resubmit your sitemap under Indexing > Sitemaps. After 4-8 weeks, rerun the export from step 1 and the script from step 2: each fixed query should show one page with 80%+ of impressions.

Because the audit uses a rolling 90-day window, old split data fades out fully about three months after the fix.

text
curl -sI https://example.com/blog/best-hiking-boots | grep -iE "^(HTTP|location)"
Pro tip: Annotate the change date in your reporting so you can compare positions before and after.

Platform-specific notes

WordPress

Add 301s with the Redirection plugin (Tools > Redirection), Rank Math (Rank Math > Redirections) or Yoast SEO Premium (Yoast SEO > Redirects). Watch for tag and category archives that repeat a post's topic; set thin archives to noindex in your SEO plugin.

Shopify

Create redirects under Content > Menus > URL redirects (older admins: Online Store > Navigation > URL redirects). Shopify only lets you redirect URLs that no longer exist, so delete or rename the old page or blog post first. Blog posts and collections often compete for the same product query; differentiate the post toward informational intent.

Wix

Add redirects in Dashboard > Marketing & SEO > SEO > Tools and settings > URL Redirect Manager. Edit titles in each page's SEO settings (Page menu > SEO basics) and H1s directly in the editor.

Webflow

Add 301s in Site settings > Publishing > 301 redirects, then republish. CMS collection templates often generate H1s from the Name field; rename collection items so their topics differ.

Next.js

Add redirects in next.config.js via async redirects() returning { source, destination, permanent: true }, or in middleware for dynamic routes. Make sure generateMetadata produces distinct titles for each dynamic route.

Check that it worked

✅ How to verify

  • Rerun the query + page export for the last 90 days and confirm no query with 50+ impressions has two pages each above 20%.
  • In Search Console Performance, filter Query = your target term and open the Pages tab; one URL should dominate impressions.
  • Run curl -I on each merged URL and confirm a single 301 hop to the owner page.
  • Rerun the audit and confirm the cannibalisation count has dropped or cleared.

⚠️ Common mistakes

  • Using a canonical tag instead of a 301 on a page you are retiring; Google may ignore the canonical and keep both URLs competing.
  • Rewording H1s and titles with the same core words in a different order, which leaves the topic identical.
  • Deleting the competing page without redirecting it, losing its backlinks and creating 404s.
  • Leaving internal links and navigation pointing at the secondary page with the target query as anchor text.

Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.

Check my site free

FAQ

How do I know if two pages are cannibalising each other?

Filter Search Console Performance by the query and open the Pages tab. If two or more of your URLs each get a meaningful share of impressions (20% or more) for the same query over 90 days, and rankings swap between them, they are competing.

Is it always bad to have two pages ranking for the same keyword?

No. If both hold positions 1 and 2 with different intents, that can be fine. It becomes a problem when impressions are split and neither page reaches the position a single consolidated page would.

Should I use a 301 redirect or a canonical tag to fix cannibalisation?

Use a 301 when the secondary page has no separate purpose. Use a canonical only when both URLs must stay accessible to users, such as filtered or parameter variants of the same content.

How long does it take for rankings to recover after merging pages?

Google usually processes redirects within days to a few weeks, and consolidated rankings typically settle within 4-8 weeks. Reports based on 90 days of data will show the full effect around three months later.