Start a project

Tool 22 of 194 · SEO

Keyword Cannibalisation Finder

Spot the queries where your own pages compete with each other, using real Search Console clicks and impressions.

Keyword Cannibalisation Finder

Query and page data

Search Console's Performance report exports queries and pages separately. To get both on one row, use the Search Analytics API (dimensions query and page), the BigQuery bulk export, Looker Studio, or a connector such as Search Analytics for Sheets. Nothing is uploaded.

    Queries with competing pages

    SeverityQueryPagesImpressionsClicksClicks not on the top pageWhat to do
    Results (CSV)

    Page pairs

    PageCompetes withQueriesImpressionsFor example

    Clicks not on the top page

    01

    What it does

    Finds the queries where two or more of your pages compete in Google, from Search Console query and page rows, and says which to merge, redirect or re-target.

    • Reads query + page rows from the Search Analytics API, bulk export or Looker Studio
    • Adds up device and date rows, with position weighted by impressions
    • Shares of clicks and impressions per page, and the clicks that miss the top page
    • High, medium and low severity with a suggested fix

    02

    Private by design

    Everything happens in your browser. Nothing you type, paste or upload is sent anywhere, and it keeps working offline once the page has loaded.

    03

    What you get

    Queries with competing pages, page pairs and a CSV, with a Copy and a Download button on every result.

    • SEO
    • Search Console
    • Content

    Why it matters

    Keyword cannibalisation is when several pages on one site rank for the same query, so Google keeps swapping between them and neither ranks as well as one strong page would. It's easy to miss because each page looks fine on its own; the problem shows only when you put query and page side by side.

    This finder takes Search Console rows with both a query and a page, picks the page that wins most clicks for each query, and flags any other page with a real share of the impressions. Queries where clicks are genuinely split come first. The page-pair table shows where two pages overlap on many queries, which usually means they should be merged.

    How to use it

    1. Export query and page rows from Search Console (API, bulk export or Looker Studio).
    2. Open the CSV or paste it in.
    3. Set the share threshold and your brand terms.
    4. Work down the list: merge, redirect or re-target the competing pages.

    FAQ

    What is keyword cannibalisation?

    Two or more of your pages ranking for the same query, splitting clicks and signals so neither ranks as well as one page could.

    Is it always a problem?

    No. Different intents can deserve different pages, and a page that gets a few stray impressions is harmless. It matters when clicks are split or the wrong page ranks.

    Why can't I use the normal Performance export?

    It exports queries and pages as separate tables, so you can't see which page got which query. The API, bulk export and Looker Studio give both on one row.

    How do I fix it?

    Choose one page for the query. Merge the other into it and redirect, re-target the other at a different query, or link to the chosen page and take the query out of the other's title.

    Work with me

    Want a site that gets these right?

    I build fast, accessible websites and web apps that pass these checks from day one. Tell me about your project and I'll reply personally with honest next steps.

    All developer tools · Back to leej.uk