Check keyword cannibalization in Search Console
Filter a relevant query in Search Console and inspect which pages receive its clicks and impressions. Compare the pattern across periods, then read the pages. Shared keywords are only a candidate signal: the important question is whether pages serving the same intent are interfering with useful search performance.
On this page
A list of shared keywords is not a list of pages to delete. The useful investigation is narrower: do two pages try to satisfy the same searcher's task, and is there evidence that keeping them as separate destinations is unhelpful?
This guide gives you a repeatable check, a way to record the evidence, and a decision framework. You can carry out a small review directly in Search Console without buying another tool.
Start with a query that matters
Pick a query connected to an important page or customer task. Avoid beginning with every query your domain has ever appeared for: large overlap reports often bury the few decisions that deserve attention.
Open Performance → Search results, choose a complete date range, and select the query in Queries. Then switch to Pages, keeping the query filter active. Record the URLs, clicks, impressions, and average positions. Compare an equal earlier period using consistent device, country, and search-type settings.
Google's Performance report help describes the filters and dimensions. Query visibility is incomplete because of privacy filtering, so an absent row is not proof that a page never appeared.
Record the relationship between the query and the pages
For a small audit, use one worksheet per candidate query. Include the page's actual purpose alongside its numbers. That forces you to consider the visitor, not just overlap.
| Field | What to record |
|---|---|
| Query and filters | Exact query, country, device, search type |
| Comparison | Two complete date ranges |
| Candidate URLs | Every relevant URL shown under the filtered query |
| Search evidence | Clicks, impressions, and position in each period |
| Page purpose | The specific question or task each page serves |
| Decision | Keep, differentiate, investigate consolidation, or collect more evidence |
If you automate the review, request the query and page dimensions together. A global Queries export and a global Pages export cannot be reliably joined by row number: they are different aggregations. The Search Analytics API documentation describes dimension grouping and pagination. Its results have coverage limits; do not label a partial extraction a complete audit.
Distinguish three different situations
Healthy overlap
A software site's product page and installation guide both appear for a branded query. The product page helps a buyer evaluate the software; the guide helps a user install it. Different purposes can justify both pages.
Read each page and check the more specific queries it serves. If they have distinct jobs, preserve that distinction. A combined impression count is not a count of unique searchers, and adding page impressions can double-count searches where both URLs appeared.
Pages that need clearer differentiation
Two guides cover similar territory, but one should explain how to choose a solution while the other should explain how to implement it. Their headings, introductions, and internal links currently make them sound interchangeable.
Define a one-sentence purpose for each. Adjust the content and links to make the distinction useful, and cross-link at the natural handoff. If one page cannot offer a distinct useful answer, investigate consolidation rather than manufacturing a keyword variation.
Candidates for consolidation
Two substantially overlapping articles answer the same question for the same audience. Their content is fragmented, one is outdated, and the query-to-page evidence shows the weaker destination appearing instead of the useful one.
That supports a closer consolidation review, not an immediate redirect. Check other queries, unique content, links, conversions, and existing references to both pages. You need to know what would be lost before choosing a destination.
These situations are illustrative decision examples, not claims about a particular site's results.
Choose the smallest justified intervention
Keep both pages when they serve distinct jobs and there is no meaningful problem to fix. Document why the overlap is acceptable so it is not repeatedly flagged.
Differentiate them when their purposes are useful but unclear. Make the distinction visible in the content, title, and relevant internal links. Do not merely swap synonyms in the title while leaving two interchangeable pages underneath.
Consolidate after review when one stronger destination can preserve the useful content and serve the same audience. Plan the destination, content merge, relevant permanent redirect, and updates to internal links. Check for redirect chains and make sure the final page remains accessible and indexable.
Use canonical signals for actual duplicates, not as a keyword-ranking switch. Google's canonicalization guidance explains that canonical signals help consolidate duplicate or very similar URLs and that Google chooses the canonical. Our canonical issues guide can help interpret the resulting Search Console status.
Verify both implementation and performance
Save the original pages and query evidence before making a change. After publication, check the final response, canonical, content, and internal links. Later, inspect Google's chosen canonical or indexing state when relevant.
Review the same query-page relationships over comparable windows, but also check the other searches the edited pages served. Moving one query to the preferred URL is not a complete success if the change discards valuable long-tail coverage or makes the visitor's task harder.
If the investigation began with declining traffic, use the traffic-drop guide to test alternative explanations. A page swap and a click decline occurring together do not establish that cannibalization caused the decline.
Check your candidate pages with Percy
Percy can investigate query-to-page overlap and read candidate pages in the same conversation. Start with the prompt below, then ask for the evidence behind a proposed change. You review and publish any edits; shared keywords alone should not trigger destructive recommendations.
Check this site for possible keyword cannibalization using query-to-page Search Console data across comparable complete periods. Find up to three meaningful overlaps, inspect the candidate pages, and distinguish healthy multi-page visibility from competing pages serving the same intent. Show URLs and evidence, state uncertainty, and recommend either keeping, differentiating, or investigating consolidation. Do not recommend redirects or canonicals from shared keywords alone.
When there is no harmful overlap, return to finding worthwhile SEO quick wins. Resolving a theoretical problem is not more valuable than improving a page with a clear customer need.