Find keyword cannibalization in Search Console

Spot overlapping URLs in Google Search Console, distinguish normal multi-page rankings from harmful cannibalization and choose a safe SEO fix.

TL;DR

Several URLs appearing for the same search query are a clue, not proof of harmful keyword cannibalization. Compare their search intent, rankings and click trends before you merge, redirect or rewrite anything.

What keyword cannibalization actually means

Keyword cannibalization is usually described as two pages competing for the same keyword. In practice, multiple pages from one site can rank for the same query without any problem. One might serve an informational intent while another serves a product-comparison intent.

A potential issue emerges when two substantially overlapping URLs target the same user need, search traffic is split in an unhelpful way, or the wrong page consistently earns visibility. The decision should be based on query and page evidence—not simply on two URLs sharing a keyword.

How to find overlaps in Google Search Console

  1. Open Search results → Performance for the relevant property.
  2. Choose a meaningful time range, such as the last 90 complete days.
  3. Select a query that matters to your business.
  4. Open the Pages tab to see which URLs received impressions or clicks for that query.
  5. Compare each URL’s clicks, impressions, average position and trend over time.
  6. Repeat for your commercially important queries and the pages you want to rank.

The Search Console API can help automate this review using combinations of query and page dimensions. Keep in mind that reporting is not a complete export of every rare query: privacy filtering and data limits can hide low-volume terms.

For technical background, see Google’s Search Analytics API documentation.

The prompt to start with

For the last 90 complete days, find meaningful non-branded search queries for which two or more URLs on my site received impressions. For each query, show the URLs, clicks, impressions and average position. Flag potential overlapping intent, but do not label it cannibalization until we review the pages.

A better follow-up is: “Which URL best satisfies the dominant search intent, and what evidence supports that choice?”

An example: overlap versus a real problem

Imagine two fictional pages rank for ‘google search console api’:

PagePurposeDecision
/blog/search-console-apiDeveloper documentation and examplesKeep as an informational guide.
/product/search-console-integrationA product connection walkthroughKeep if it serves a distinct setup intent.

Now imagine two blog posts both explain the same API setup with nearly identical headings and examples. If neither serves a unique intent, consolidating the content may make sense.

There is no automatic rule that the URL with fewer clicks should be deleted. It could rank for valuable subtopics or earn useful backlinks.

Choose the right fix

What you findWhat to consider
Duplicate intent and nearly identical contentConsolidate into one stronger page, then redirect the retired URL where appropriate.
Different search intents but vague headingsClarify titles, H1s, intros and internal anchor text.
Wrong page earns most impressionsImprove the intended page’s relevance and contextual internal links.
Seasonal or temporary ranking shiftsMonitor a longer period before making structural changes.
Both pages perform well for distinct queriesLeave them alone. No fix is required.

Before any redirect, check the old page’s organic traffic, external links, conversions and unique query coverage. A redirect is not a harmless housekeeping operation.

How to measure whether the fix worked

Record a baseline of target queries, URLs, clicks, impressions and average position. After publishing, compare matched periods once Search Console has complete data. Watch both the target URL and the combined performance of the original page set.

If the target page gained clicks but another previously useful URL lost even more, the change may have been a net loss.

A decision framework: when overlapping pages become a problem

Finding two URLs for one query is only the beginning. Use a simple evidence checklist before deciding they are competing in a harmful way.

SignalMore concerningOften harmless
Search intentBoth pages answer the same question in almost the same wayOne is a tutorial and one is a product page
Query coverageNearly identical top query setsDistinct keyword clusters despite some overlap
Ranking trendThe intended landing page consistently loses relevant visibilityBoth pages serve different useful queries
Conversion goalSearchers land on a less relevant page for their goalEach page moves users toward an appropriate next step
Content differentiationRepeated headings, examples and substanceClear distinctions in task, audience and depth

Do not create a numerical ‘cannibalization score’ from impressions alone. High impressions on two URLs do not prove their rankings are harming one another.

Example: how to review two competing tutorials

Suppose these are illustrative, not real Search Console numbers:

QueryURL A clicksURL B clicksNext question
gsc api example14095Do both pages teach the same API call?
search console oauth652Is URL A primarily an authentication guide?
search console api limits3130Is URL B the better reference for quotas?

Even though both URLs rank for the first query, their broader query patterns suggest distinct user needs. A forced merge could make both worse.

Now suppose both articles cover authentication, pagination and quotas in nearly the same order, target the same audience, and consistently split clicks on the same major queries. A consolidated guide with a stronger information architecture may be worth testing.

The difference between these situations is intent and usefulness, not whether Search Console lists two URLs.

A safe consolidation playbook

If the pages truly duplicate each other, use this sequence rather than deleting the weaker URL immediately:

  1. Export each URL’s query and landing-page performance for an established baseline.
  2. Check whether either URL earns important external backlinks or conversions.
  3. Inventory unique examples, sections and answers across the two pages.
  4. Choose the canonical destination based on usefulness, link signals and user intent—not the shorter URL alone.
  5. Combine valuable sections, remove genuine repetition and update internal links to the preferred URL.
  6. Add a permanent redirect from the retired URL where appropriate; do not redirect unrelated pages to the homepage.
  7. Check the new page and redirect behavior, then monitor combined clicks and relevant rankings over time.

If the pages serve different intents, do not merge them. Give each a precise headline, stronger internal anchor text and clearly differentiated content.

Cannibalization FAQ

Can the same website rank twice for one query?

Yes. Multiple results from a domain are not, by themselves, an SEO failure.

Will changing a canonical tag always fix cannibalization?

No. A canonical is a signal for duplicate or similar content selection, not a replacement for making pages satisfy distinct search intents. Google may choose a different canonical.

Should I delete the page with fewer clicks?

Not without checking its unique queries, external links, conversions and the intent it serves. It might be the more valuable page for a narrow audience.

How quickly will merged pages improve?

There is no guaranteed improvement or timeline. Google must discover and process the changes, and search demand and competing content can move during the same period.

Overlaps are one possible cause of weak performance, not the default explanation. If rankings are stable but CTR is poor, follow our low-CTR opportunities guide. If clicks fell suddenly, use the traffic-drop diagnosis checklist.

Want to ask these questions without manually downloading CSV files? Explore GSC Magic, an MCP-based approach to using your search data with an AI assistant.

Join the waitlist

Coming soon. Get 30% off Pro for 6 months when you join.

Join the waitlist