Be Seen Digitally

Two pages appearing for one query is a signal to investigate, not proof of a problem. Use your own Search Console data to decide whether to separate, merge or leave them alone.

Cannibalisation: when two pages split one query

Keyword cannibalisation is easy to over-diagnose. Two pages can appear for the same query because they answer different needs, and that overlap may be useful. It becomes a problem when the pages serve the same intent, the wrong page receives the visibility, or Google repeatedly switches between them. The practical test is not “Do two URLs appear?” but “Should one page clearly own this query?”

What keyword cannibalisation actually means

Keyword cannibalisation describes two or more pages from one site competing for the same query and the same search intent. The second condition matters. A product page and a buying guide can both appear for a broad product query without being interchangeable: one supports a purchase, while the other supports research.

The overlap needs attention when the pages do the same job. Typical cases include:

  • two articles answering the same question;
  • an old landing page and its replacement remaining indexable;
  • location or product pages whose content is not distinct;
  • a category page and an article both trying to be the main answer;
  • URL variants that should resolve to one canonical page.

“Cannibalised” is therefore a working label for a query with competing pages, not a Google status or a penalty. The data identifies the overlap. You still have to inspect the pages and decide whether the overlap is harmful.

Read the query and page data together

Google Search Console records queries and pages as separate dimensions. For a cannibalisation check, the useful unit is the query-page pair: which URL appeared for a specific query, and what happened when it did.

Compare the following signals over one fixed date range:

Signal What to look for
Pages Whether two or more URLs appear for the query
Impressions How often each page was shown
Clicks and CTR Which page searchers chose when it appeared
Average position Whether one page consistently performs better
Page share How much of the query's visibility belongs to the main page
Position over time Whether the same page leads consistently or the URLs trade places

Average position needs context. Google reports the topmost position for a property differently from the position of each individual page, so property-level and page-level figures can differ. Its Performance report documentation explains the aggregation rules.

Search Console also omits anonymised queries and may not expose every lower-volume row. That means the report is evidence from the available first-party data, not a complete inventory of every search. Google documents those query data limitations.

How to check this

In Be Seen Digitally, open Positions and competing pages. The Cannibalised queries table groups the site's own Search Console rows by query and lists cases where at least two pages appeared during the selected period.

Start with a useful range, such as 28 days, and set a minimum-impressions threshold high enough to remove accidental one-off appearances. For each query, the table shows the number of pages, clicks, impressions, CTR, average position, the main page and its share of the impressions.

Expand a query to compare its pages directly. The detail view shows clicks, impressions and average position per URL, plus a daily position trend for the leading pages. Look for one of three patterns:

  1. One clear owner. One page receives most impressions and performs consistently. The other URL is incidental, so a change may not be necessary.
  2. Different purposes. Both pages appear, but they serve different intents. Keep both and make their titles, headings and internal anchors clearly distinct.
  3. Real competition. The pages answer the same need, share the impressions, or alternate as the main result. Decide which page should own the query.

Before choosing the owner, compare the pages in Search performance, then inspect their indexability, canonical and status in Pages. Use the Link graph to see which URL your own internal links currently support.

What to do about it

The right fix depends on why both pages exist. Do not redirect or remove a page only because it shares a query.

  1. Keep both when the intents differ. Rewrite the title, H1 and opening so each page states its own purpose. Adjust internal anchor text so links describe the correct destination. The goal is a clear boundary, not forced keyword variation.
  2. Choose one owner when the intents match. Compare relevance, existing clicks and impressions, internal links, indexability, content quality and the page's role in the site. Pick the URL that should remain the primary answer.
  3. Merge overlapping material. Move any unique, useful sections from the weaker page into the owner. Avoid leaving two reduced versions of the same answer.
  4. Redirect a retired page. If the weaker URL no longer has a separate purpose, return a 301 redirect to the owner. Update internal links and the sitemap so they point directly to the destination.
  5. Use a canonical only for genuine variants. A canonical is appropriate when duplicate or near-duplicate URLs must remain available. If Google has selected a different URL from the one you intended, work through the canonical conflict fix guide.
  6. Turn the finding into work. Add a content task from the competing-page detail and attach it to the relevant crawled page. Record the intended owner and chosen action so the decision survives hand-offs.

After the change is live, use the same date range length for the next comparison. Check whether the intended URL now receives the query's impressions consistently, while also confirming that the retired or repositioned page has not lost visibility for other queries it was meant to serve.

Avoid the quick fixes that hide the decision

Adding noindex to the weaker page may remove it from search, but it does not preserve its useful material or explain where its internal links should point. A canonical is also not a substitute for deciding whether two pages have separate purposes.

The same caution applies to deletion. A page that competes for one query may still serve other queries. Check its full query set before merging or redirecting it. The objective is not to force one URL per word; it is to give each search intent one unambiguous primary page.

Closing

Cannibalisation is a diagnosis, not a count. Start with queries that have several pages, use clicks, impressions, page share and the position trend to identify real competition, then inspect the content and internal links before changing anything. Be Seen Digitally keeps that investigation tied to the site's own Search Console and crawl data, and turns the final decision into a trackable task.

Common questions

Is it bad if two pages appear for the same query?
Not necessarily. The pages may serve different intents or both may be useful results. Treat the overlap as a problem only when the pages do the same job, the wrong page appears, or visibility keeps shifting between them.
How do I find keyword cannibalisation in Google Search Console?
Filter the Performance report to one query, then open the Pages tab. Compare the URLs, clicks, impressions, CTR and average position over the same period. Search Console may omit anonymised and lower-volume queries, so the list is not complete.
Should I use a canonical tag to fix cannibalisation?
Use a canonical when two URLs are duplicate or near-duplicate versions that must remain accessible. Do not use it to combine two genuinely different pages; differentiate them or merge and redirect the weaker page instead.
How long should I measure after making a change?
Use the same date range before and after the change, and allow enough time for Google to crawl and process the affected URLs. The useful signal is whether the intended page consistently receives the query's impressions and clicks.