Search Console query overlap analyzer
Compare exported query-page data for queries appearing on multiple pages.
Your inputs
Your results
Ready when you areYour results will appear here.
How it works
Identify queries that appear against more than one page in supplied Search Console query–page data. Compare clicks, impressions, CTR, weighted position and each page’s share of exported impressions. Investigate the page pair and search intent before deciding whether their targeting needs adjustment.
A few things to know
Offline analysis only. Ordinary independent Queries and Pages exports cannot be joined reliably; obtain genuine query–page dimensions through filtered reports or a paired export. Anonymized queries, row limits and different aggregation methods make exports incomplete. This report does not prove harmful competition, diagnose canonicalization or recommend deletion. Repeated periods can double-count data.
When to use this tool
Two pages receiving impressions for the same query are a starting point for investigation. This query overlap analyzer compares actual query–page pairs from your supplied performance data and shows how the exported impressions and clicks are distributed. It helps you choose which page pairs to inspect first without assuming that overlap is harmful. A product tool and an explanatory article can answer different needs even when their queries intersect.
- Review the queries shared by a calculator and its supporting guide.
- Find page pairs to inspect after publishing new content in an established topic.
- Compare a cluster of similar landing pages using one consistent reporting period.
How to use search console query overlap analyzer
Obtain paired dimensions
Paste CSV with query, page, clicks, impressions and position headers. Each row must describe a real query–page pair. Independent query-only and page-only exports cannot be joined to create these relationships. Use up to 20,000 rows with the same filters.
Choose the review threshold
Set the minimum combined supplied impressions for each query. Run the analyzer to retain queries with more than one page having positive impressions. The table sorts overlapping queries by their supplied impression total.
Inspect the page relationships
Compare page CTR, impression share and weighted position, then inspect the page content and search results. Download the table as an investigation list. Decide whether the destinations complement each other before considering redirects, consolidation or targeting changes.
A calculator and guide share one query
Inputs
For bundle calculator, the tool page has 30 clicks, 1,000 impressions and position 5. The guide has 10 clicks, 500 impressions and position 8. A separate shipping query appears on only one page.
Result
The report finds 1 overlapping query among 2 distinct queries. The tool page has 3.00% CTR and 66.67% of the 1,500 supplied impressions; the guide has 2.00% CTR and 33.33%.
What it means
The leading page gets more of the exported exposure, but the report does not show whether the guide is hurting it. Review intent and actual results before deciding that one page should absorb the other.
Common mistakes to avoid
Joining independent exports
A Queries.csv total and a Pages.csv total do not identify which query belongs to which page. Inventing pair rows from them creates relationships the original evidence does not contain.
Summing overlapping date windows
Repeated query–page pairs are aggregated. Exporting the same month twice or mixing overlapping periods therefore inflates clicks and impressions rather than deduplicating events.
Calling every overlap cannibalization
A shared query can reflect useful coverage, different intents or multiple results. Harm requires additional evidence; this tool deliberately reports overlap rather than an automatic diagnosis.
Frequently asked questions
Definitions, edge cases, and practical next steps for this tool. Search all tool FAQs ↗
What data format does this require?
Use a CSV containing query and page together on each row, plus clicks, impressions and position. Metrics must be nonnegative plain numbers, with whole-number clicks and impressions. Get genuine pairs through an appropriate filtered or paired reporting export; do not infer them from separate summaries.
What counts as an overlapping query?
A query must have more than one distinct supplied page with positive impressions and meet your combined-impressions threshold. Zero-impression pairs remain part of the input analysis but do not create overlap. Query text is kept exact, so differently capitalized query strings are separate groups.
How are repeated query–page pairs handled?
Clicks and impressions are summed, and average position is weighted by impressions. This is useful for non-overlapping periods with consistent filters. It also means repeated copies or overlapping reporting windows double-count their data; prepare the export before analysis.
Why is average position weighted?
A row with many impressions should contribute more than a row with very few when combining the same pair. The tool multiplies each position by that row’s impressions, sums the products and divides by combined impressions. Rounded source positions keep the combined value approximate.
Is impression share a share of unique searches?
No. It is a page’s impressions divided by the sum of supplied page-row impressions for that query. It is not a count of unique people or guaranteed sitewide exposure. Different reporting aggregation and incomplete exports can change what those totals represent.
Should I delete the page with lower CTR?
This report cannot support that decision alone. A lower-CTR page may serve a useful secondary intent or appear in different contexts. Review content, links, devices, countries, date trends and the actual search results before changing a page’s availability.
Why is an expected query missing?
It may have only one page with positive impressions, fall below your threshold, or be absent from the supplied export. Row limits, filtering and omitted query data also affect coverage. Lowering the threshold cannot restore rows that are not in your CSV.
What is a useful next action?
Choose a few high-exposure pairs and document what each page promises. Compare their headings, purpose, internal links and result presentation. Keep complementary pages when they meet distinct needs; test a specific targeting change when evidence supports it and monitor the same reporting setup afterward.
Explore the topic in the blog
Sources and method
Use the references below to check definitions and platform guidance. The model’s scope and limits are explained above. Read our editorial standards.