Keyword Cannibalization: Detecting Pages That Compete With Each Other

Cannibalization is usually diagnosed by searching the site for a keyword and finding three pages that mention it. That is not cannibalization; that is topical coverage. Actual cannibalization shows up in Search Console as multiple URLs ranking for the same query, alternating positions over time. The distinction matters because the fixes are opposite: coverage should be linked together, cannibalization should be consolidated or differentiated.

Measure it from query-page data

Export Search Console's query-page report for the last 90 days. If the API limit prevents a full export, segment by query and pull the top pages per query.

For each query, count distinct URLs with impressions. A query with two or more URLs each holding more than 5% of impressions is a candidate. Sort candidates by total impressions to focus on queries that matter.

For each candidate, chart the URLs' average positions over time. Alternating positions — page A ranking third one week and page B ranking third the next — is the signature. If page A consistently outranks B, there is no conflict; there is a hierarchy.

Separate the three patterns

True cannibalization — two pages target the same intent and compete. Fix by merging or by differentiating one page's angle and internal links.

Intent split — pages serve different intents for the same query, such as a guide and a product page. This is healthy if each ranks for its own variant; the fix is clearer titles and internal anchors, not deletion.

SERP instability — the same page fluctuates and other URLs appear occasionally. This is not cannibalization, and merging pages will not help.

Classify before acting. Merging pages that serve different intents destroys coverage and is the most common self-inflicted wound in these audits.

Decide merge versus differentiate

Merge when both pages answer the same question with overlapping content and neither has a distinct backlink profile worth preserving. Consolidate into the stronger URL, redirect the other, and update internal links.

Differentiate when the pages serve different stages of the funnel or different sub-intents. Rewrite titles to signal the difference, change the primary keyword of one page, and link between them with descriptive anchors. Then monitor whether each settles into its own query set.

Keep the weaker URL only if it earns traffic for a distinct cluster. Traffic from unrelated queries is a reason to keep it, not a reason to merge it.

Measure the outcome, and prevent recurrence

After consolidation, expect a temporary dip while Google reprocesses. Track the target query's position and the merged URL's impressions over six weeks. A successful merge usually produces a higher, more stable position and more total clicks than the sum of the competing pages.

If position drops and stays down, check that the redirect target retains the merged content and that internal links point to the final URL without chains. A merge that loses content is not a merge.

Assign one primary keyword per page in the content brief, and check for an existing page targeting it before publishing. The only reliable prevention is a keyword-to-URL map that new content must consult, plus a quarterly query-page review for the top 200 queries.

Pulling the data reliably, and when positions alternate

The Search Console API's query-page report is the safest source. Export 90 days, filter to queries with at least two URLs above a minimum impressions threshold, and store the result with the export date.

Beware of the row limit: a high-traffic site exceeds it, and the API returns the top rows by clicks. Filter per query prefix or per page group to get complete data for the queries you care about.

Alternating positions can reflect personalization, device differences, or genuine ranking instability. Segment by device before concluding cannibalization. A page that ranks third on mobile and eighth on desktop may be a responsive content problem rather than two pages competing.

Check the query's SERP features too. If an AI Overview or a featured snippet appears intermittently, the URL that "wins" may change with the feature rather than with your content.

Consolidation mechanics, the post-merge window, and intent splits

When merging, move the unique sections from the weaker page into the stronger one before redirecting. Keep the stronger URL's slug; changing it adds a redirect for the page that was already ranking.

Update internal links to the final URL, remove the weaker page from the sitemap, and redirect with a 301. Do not leave both URLs returning content for a "grace period".

Expect a two-to-six-week period of unstable rankings. Track the merged page's position for the primary query and for the cluster's top ten queries. If the merged page ranks lower than either predecessor after eight weeks, the merge may have diluted focus; consider splitting the topic again with clearer differentiation.

A guide and a product page ranking for the same query may be healthy if the query has mixed intent. Before merging, check which page earns clicks. If each earns a meaningful share, they are serving different intents; improve titles and internal links instead of consolidating.

Maintenance rules, and a lightweight weekly check

Assign a primary query to every page and record it in the CMS. Before publishing, search that query within the site and review any page already targeting it. This one step prevents most future cannibalization without any reporting work.

Pull the top queries for pages published in the last quarter and look for two of your URLs in the same query's results. New content is where cannibalization starts.

Add the check to the publishing checklist rather than waiting for a quarterly audit.

When to do nothing, and confirming before merging

If both pages earn clicks for different query variants, they are serving different intents. Leave them and improve the internal links between them.

Deleting a page that earns traffic to fix a theoretical overlap is a net loss.

Two pages ranking for one query may serve different intents. Check the query's SERP: if it mixes product and guide results, both pages have a reason to exist.

Merge only when the pages target the same intent and one consistently outranks the other. Otherwise differentiate the titles and internal links instead.