SEO 2026 · Query × Page
Keyword Cannibalization Checker: Find Query–URL Overlap in Search Console
Find search queries associated with two or more URLs on your site. This free browser-local tool matches paired Query + Page data and shows page-level clicks, impressions and the secondary URL's relative visibility without invented Google scores.
Browser-local SEO utility
Query–URL Overlap Finder
Paste one CSV with Query, Page, Clicks, Impressions or API JSON for dimensions ["query", "page"]. Parsing stays in your browser; no CSV upload. Demo data are fictional.
Preparing analyzer…
How to export Query + Page data
Send an authorized POST to Search Analytics API at /webmasters/v3/sites/{siteUrl}/searchAnalytics/query. The request body below uses illustrative dates. Paste rows[] response JSON, never an access token. The second value in rows[].keys must be an HTTP(S) URL.
{
"startDate": "2026-09-01",
"endDate": "2026-09-28",
"dimensions": ["query", "page"],
"type": "web",
"rowLimit": 25000
}The dimension order must be ["query", "page"]. API data has internal row limitations and startRow pagination. This browser utility accepts up to 3,000 rows per paste.
A practical keyword overlap workflow
1. Export genuinely paired dimensions
Request dimensions: ["query", "page"] in Search Analytics API for one complete period. Paste the API rows[] JSON or a CSV with Query, Page, Clicks, Impressions and optional Position. Two independent Queries and Pages CSV exports cannot reconstruct query → URL relationships.
2. Identify material overlaps
Set a minimum impression count and exported page-row share for the second-most-visible URL. Start with queries where two different URLs both receive meaningful impressions. Summed page-level impressions are not the property's unique search impression total.
3. Review the underlying intent
Compare the primary question and task of each page. An informational guide and a service landing page can legitimately both appear for ambiguous searches. Overlap alone is not a reason to remove an indexed page.
4. Check SERPs, indexing and canonicalization
Inspect the actual country/device SERP, URL Inspection, indexing, rel=canonical, HTTP status, page title, H1 and internal links. If you confirm duplicate content, choose consistent canonical or redirect signals.
5. Apply the smallest valid fix and remeasure
Keep useful distinct pages, clarify content and internal links, or consolidate genuine duplicates with a considered canonical or 301. Record the change date and compare equivalent GSC periods after reprocessing.
Frequently asked questions
Does ranking more than one URL cause a Google penalty?
No. These are observed query–page overlaps, not proof of a ranking penalty or an official Google cannibalization score.
Why can’t I paste a standard GSC Queries CSV?
It has no page linked to each query. Use a joint export with query + page dimensions, such as Search Analytics API data.
Why do summed URL impressions differ from the property total?
Multiple pages can each have impressions for the same query. The displayed share is computed from exported page rows, not total search demand.
Should I immediately 301 or canonicalize the second URL?
No. Automatically consolidating different useful pages can lose valuable intent coverage. Use redirects and canonicalization for genuine duplicates.
Is my private GSC data uploaded?
No. Input is parsed in your browser. Never paste access tokens, credentials or other secrets.
Primary sources and methodology
The algorithm groups query+page pairs by case-insensitive query, sorts URLs by impressions, and calculates the second URL's share of exported page-row impressions. This prioritizes manual checks, not a Google cannibalization score or proven lost clicks.