---
title: "Keyword Cannibalisation Fix: One Page per Question | Aemorph"
url: https://aemorph.com/guides/cannibalisation-fix/
description: "Keyword cannibalisation splits one buyer question across two of your pages. See how to confirm it, consolidate the pages and fill the gaps it hides."
schema_type: TechArticle
publisher: Aemorph
publisher_entity: https://aemorph.com/entitymap.json#org_aemorph
entities: [concept_keyword_cannibalisation]
language: en-SG
updated: 2026-11-01
---

Guides

# Keyword Cannibalisation Fix: Why Two of Your Pages Compete for One Buyer Question

**A keyword cannibalisation fix gives each buyer question one owning page.** Google then ranks one preferred URL instead of splitting your rankings between two pages that answer the same thing, and the AI chats find one current source for that answer. Aemorph's technical SEO merges the competing pages and redirects the duplicates. It also fills the questions your site leaves unanswered. Remarkable Furniture's monthly organic visits rose from 3,883 in September 2019 to 12,172 in October 2020. That followed Aemorph's advice to consolidate its duplicate categories and repeating pages.

[Book a strategic conversation](https://aemorph.com/contact/)

Written by [Kevin Dam](https://aemorph.com/about/), founder of Aemorph, who has practised SEO since 2010 and sits on the [Forbes Agency Council](https://councils.forbes.com/profile/Kevin-Dam-Global-Search-Architect-%7C-SEO-GEO-AEO-IMO-LLM-Visibility-Aemorph/4c8c7a38-1285-470d-8ea8-e517a310a00b). Aemorph is a [Google Partner](https://www.google.com/partners/agency?id=4441861842). [LinkedIn](https://www.linkedin.com/in/kevindam)

---

## Cannibalised Pages Show Up as Core Terms Stuck on Page Two

**Keyword cannibalisation shows up as two of your URLs taking turns to rank for one query while neither climbs onto page one, so buyers searching your core terms meet a competitor first.** Aemorph's working trigger for a review is a core term held between positions 11 and 20, and the overlap is confirmed at the URL level before any page changes.

| Symptom | Where you see it | Likely cause to test | Fix | Where it gets fixed |
| --- | --- | --- | --- | --- |
| Two URLs swap positions for one query from week to week | Search Console performance report, filtered by the query, Pages tab | Two pages answering the same buyer question | Assign the question to one owning page and consolidate the other | Content plan and redirect list |
| A core term held between positions 11 and 20 | Ahrefs or Semrush position history | Duplicate intent across pages, or incomplete coverage of the question | Confirm the URL overlap for the query before acting | Question-to-page register |
| Google shows a different page from the one built for the term | Search results and Search Console | Google selected another URL as the better match | Point redirects, canonical tags and internal links at the owning page | Templates, server rules and internal links |
| Category or tag archives outrank the service page | A Screaming Frog crawl and Search Console | Archive pages repeating service terms | Keep archives out of the index or consolidate them | CMS settings |
| AI answers cite an old blog post instead of your service page | Tested prompts in the AI chats | The older page states the fact more plainly | Move the plain statement to the owning page, then redirect or update the older one | Owning page copy |

*Symptoms, likely causes and fixes for keyword cannibalisation. The positions 11 to 20 trigger is Aemorph's own guideline, not a search engine rule.*

Cannibalisation has a mirror image: a site that answers one buyer question on two pages leaves other questions with no page at all, and the [topical thinness fix](https://aemorph.com/guides/topical-thinness-fix/) covers the questions your site never answers. A staging copy, migration redirect failures, responsive template heading failures, single-page app rendering failures and schema markup errors sit in the same group of technical faults that stop the right page being read.

### How do you know if two pages are cannibalising each other?

**Two pages are cannibalising each other when Search Console shows both URLs collecting impressions for the same query and their positions alternate instead of one page holding the result.** A shared keyword alone proves nothing: two pages that answer different questions rank side by side without harm, so Aemorph confirms the overlap at the question level before merging anything.

The same Search Console query data shows your [non-branded impression diversity](https://aemorph.com/guides/non-branded-impression-diversity/), the share of your impressions that come from searches without your name.

---

## Pages Compete When Your Site Answers One Question Twice

**Cannibalisation forms when a site publishes a second page for a buyer question it already answers, such as a blog post, a category page or a location variant, so search engines receive two candidate answers and the links each page earns stay divided.** Google states that duplicate content is not a violation of its spam policies, and that search engines choose one URL, the canonical URL, to show for each piece of content. When two of your pages compete, Google makes that choice from its own signals, and those signals ignore which page you built to convert.

Google ranks its canonical signals by strength: [a redirect and a rel="canonical" tag are strong signals, sitemap inclusion is a weak one, and Google advises against using robots.txt to choose a canonical URL](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) (Google Search Central, checked October 2026).

*[Sources: Google Search Central, October 2026](https://aemorph.com/sources/#google-search-central-october-2026-cannibalisation-fix)*

Aemorph's [EAV Exhaustion Methodology](https://aemorph.com/guides/eav-exhaustion-methodology/) records each fact a buyer wants confirmed as a slot with three parts: your business, a thing that is true of it and the specific detail. Each slot gets one owning page. Cannibalisation is a slot answered twice, and the same audit lists the slots answered nowhere, because a site that repeats one answer has spent pages it needed for others. Two pages stating one fact with different details also hand the AI chats two versions of your business to reconcile.

### What causes keyword cannibalisation?

**Keyword cannibalisation is caused by publishing more than one page for the same buyer question: new blog posts on topics a service page covers, category and tag archives, location or service variants with near-identical copy, and old pages left live after a rewrite.** Each one adds a second candidate for a question that already has an answer.

---

## Consolidation Gives Each Buyer Question One Owning Page

**The cannibalisation fix assigns each buyer question to one owning page, merges the useful content of the competing pages into it, redirects the duplicates with 301s and then fills the questions the audit shows unanswered.** A redirect on its own moves the URL and drops whatever the redirected page said that the owning page lacks, so Aemorph consolidates the facts first and the URLs second:

1.  **Maps** each indexed page to the buyer questions it answers, from Search Console queries, an Ahrefs or Semrush export and a Screaming Frog crawl.
2.  **Confirms** each overlap at the question level: two URLs with impressions for the same query and alternating positions.
3.  **Chooses** the owning page for each question: the page that matches the buyer's intent, carries the strongest inbound links and converts.
4.  **Merges** each fact, figure and example from the competing page that the owning page lacks, checked against your verified record.
5.  **Redirects** each retired URL to its owning page with a 301, then updates internal links, canonical tags and the XML sitemap to name the owning page.
6.  **Fills** the unanswered questions the register shows, one page or one section per question.
7.  **Measures** the result across the whole cluster of questions, not one keyword.

Aemorph specifies the consolidation, your developers or IT vendor implement it, and Aemorph verifies it once live.

> **Case study · Outdoor furniture retail, Australia**
>
> **Remarkable Furniture's monthly organic visits rose from 3,883 in September 2019 to 12,172 in October 2020, up 213%.**
>
> The store's database and product tables carried duplicate categories and subcategories, plus repeating keyword and product pages. Aemorph advised consolidating them, with each old URL redirected to its correct new page, alongside the store's move from WordPress to Magento. The comparison covers two dates, so it does not separate the consolidation from the migration and the work around it. [Read the Remarkable Furniture case study](https://aemorph.com/case-studies/remarkable-furniture/)

*[Source: Ahrefs, October 2020](https://aemorph.com/sources/#ahrefs-october-2020)*

### Do you delete or redirect a cannibalising page?

**Redirect a cannibalising page with a 301 to its owning page once its useful content is merged, and delete it outright only when it carries no inbound links, no traffic and no fact the owning page lacks.** When both pages need to stay live for visitors, such as filtered product views, a rel="canonical" tag on the duplicate names the owning page instead.

---

## Unfixed Cannibalisation Spreads Across a Service Line

**Cannibalisation left in place spreads with each new page published on a covered topic, so Aemorph checks each planned page against the question register before it is written.** The cost grows from one stalled term to a whole service line that ranks below competitors who answer each question once.

| Stage | What happens | What it costs you | Check | What triggers a recheck |
| --- | --- | --- | --- | --- |
| One pair of competing pages | Two URLs alternate for one query | The term holds on page two | Confirm the overlap and consolidate | A new page on a covered topic |
| Several pairs across one service line | Duplicates across blog, category and service pages | The service cluster ranks below competitors with one page per question | Question register for the cluster | A content calendar that adds posts without checking the register |
| Duplicates beside unanswered questions | Pages repeat answered questions while others stay empty | AI answers name competitors on the empty questions | Count filled questions against the full list | A new service, market or audience |
| Consolidated and mapped | One owning page per question | Links and engagement concentrate on one URL | Register checked before each new page | A new page brief |

*Cost and recheck point by cannibalisation stage, as illustrative scenarios.*

Aemorph reports the result with [cluster-level measurement](https://aemorph.com/guides/cluster-level-measurement-for-aeo-geo/): the share of questions inside one buying decision where your owning page ranks or where AI answers name your business, tracked over time. That view covers [SEO](https://aemorph.com/glossary/#seo-search-engine-optimisation), search engine optimisation, which earns your place in Google's results; [AEO](https://aemorph.com/glossary/#aeo-answer-engine-optimisation), answer engine optimisation, which gets you quoted in Google AI Overviews; and [GEO](https://aemorph.com/glossary/#geo-generative-engine-optimisation), generative engine optimisation, which gets you cited inside the AI chats. A single keyword's position hides whether the consolidation lifted the rest of the cluster.

### Does cannibalisation come back after a fix?

**Cannibalisation returns whenever a new page answers a question an existing page already owns, so the question register gets checked before each new page is briefed.** A register kept current turns that check into a short lookup.

---

## One Owning Page Keeps Your Facts in One Version

**One owning page per question keeps the price, scope and eligibility rules a buyer reads in a single, current version, because two pages answering one question drift apart over time.** A buyer reading a stale duplicate has no way to tell it from the page you updated, and your business made both statements.

Consumer protection law in the markets Aemorph serves applies to misleading claims made in trade, and a stale page still counts as a claim you published. Aemorph checks each merged fact against your [verified record](https://aemorph.com/glossary/#verified-record), the one approved set of facts about your business, before the owning page goes live. A question about a specific claim is one for a qualified legal adviser in your jurisdiction.

*General guidance, not legal advice.*

### Does duplicate content cause a Google penalty?

**Duplicate content does not cause a Google penalty: Google states it is not a violation of its spam policies, and the cost is a split between competing pages and a canonical choice Google makes for you.** The commercial risk sits with the stale page a buyer reads.

---

## Technical SEO Gives Each Buyer Question One Page That Answers It

**Aemorph's [technical SEO](https://aemorph.com/services/technical-seo/) maps your pages to buyer questions, specifies the consolidation and redirects, and verifies them once live, so each question your buyers ask has one page that answers it.** Cannibalisation work sits inside Aemorph's SEO service, and the free [Money on the Table audit](https://aemorph.com/glossary/#money-on-the-table-audit) puts a number on the revenue lost at your current visibility in search.

The [Showstopper Sensor](https://aemorph.com/glossary/#showstopper-sensor-sprint-1) (Sprint 1), a 30-day showstopper-answer sprint for ChatGPT, Claude, Gemini and Perplexity, publishes your approved answers to your [showstopper questions](https://aemorph.com/glossary/#showstopper-questions), the buyer questions that stop a purchase when AI answers them badly, on your site. The question register from a cannibalisation fix keeps each of those answers on one page.

### Who fixes keyword cannibalisation, Aemorph or your developers?

**Aemorph specifies the fix and your developers or IT vendor implement it: Aemorph lists the questions, chooses the owning pages, specifies the merged content and the redirect list, and verifies the redirects and canonical tags once live.** Your team keeps control of the CMS and the release schedule.

Start with a free [strategic conversation](https://aemorph.com/glossary/#strategic-conversation), which includes prompting the AI chats for your current brand answers. Technical SEO fixes are scoped from the audit findings and set out in your quote; starting points are on the [pricing page](https://aemorph.com/pricing/).

[Book a strategic conversation](https://aemorph.com/contact/)

[See technical SEO](https://aemorph.com/services/technical-seo/)

THE STRATEGIC CONVERSATION

## Start with a free *strategic conversation*.

Every Aemorph engagement starts with a free strategic conversation. It is the fastest way to see whether Aemorph fits your business before you commit budget.

[Book a strategic conversation →](https://aemorph.com/contact/)

STARTING POINT

Free

You talk through your goals with Aemorph, and Aemorph quotes your engagement after the conversation.
