See every conflict, ranked by the traffic at stake
Open one view and see every search two or more of your URLs compete for, ordered by the clicks and impressions split between them. You no longer click into queries one at a time.
Find the queries your own pages compete for
Some of your searches return two of your own pages at once — and you'd have to hunt query by query to ever find which.
Search Console hides cannibalization one query at a time. We pull every query–page pair into your own warehouse and flag every search where two or more of your URLs compete. Each is ranked by the traffic at stake.
Query
/guide/running-shoes
—
/blog/best-running-shoes
—
/shop/running-shoes
—
Illustration. Every query where two or more of your URLs compete, ranked by the traffic at stake, from your own data.
Open Search Console in another tab. Can you answer these right now?
- Pick any query. Can you see every page of yours that appears for it — without clicking into the query and opening the Pages tab?
- Across all your searches, how many return two or more of your own URLs at once? Could you produce that list today?
- Right now, are two of your pages quietly competing for the same search — and would anything in Search Console tell you, without hunting query by query?
If you hesitated on any of these, the answer is already in your data — just not in a shape Search Console will show you.
Built for teams who own their data
- Northpeak
- Datawise
- Quantly
- Meridian
- Brightline
- Corewave
Why you can trust the data
-
Read-only access
We only ever read your data. Nothing on your site or in Search Console is ever changed.
-
Your warehouse
All data lives in your own Google Cloud project. It is never copied into a tool you do not control.
-
Your rules
Grouping and classification are tailored to your site, and stay fully editable as it changes.
-
Yours to keep
Leave and the tables stay. Export on your terms, with no rolling deletion window and no lock-in.
-
Founder pedigree
Built by a team that has run analytics for high-traffic platforms, with a Google Product Expert among the founders.
-
Built on Google’s stack
BigQuery storage and the full Search Console API, not a third-party scrape.
You have said one of these, but could not see you were the competition
Search Console will show you the pages for one query — but only if you click into that query and open the Pages tab, one at a time. So it never answers the question that reveals the problem: across your whole site, which searches return more than one of your own URLs?
Two of your pages chase the same query, split the clicks and the position between them, and the default view stays silent — because you'd have to go hunting, query by query, to ever find them.
In-house, measured on traffic
One of our key pages has been stuck at the bottom of page one for months. I have refreshed the content, added links and fixed the on-page work. Still it will not move. It never crossed my mind that two other pages of ours compete for the same query and split the ranking. The only way to check is to click into every query one by one.
The real problem Cannibalization only shows if you open each query's Pages tab by hand, across thousands of rows capped at 1,000. So two of your own URLs competing for one search stays invisible while the position quietly bounces between them.
Editorial / content marketing
We keep publishing around the topics we own. We add a guide, then a best of, then a how-to, and it feels like thorough coverage. What I cannot see is that each new piece competes with the last one for the same search. So the back catalogue quietly undercuts itself every time we add to it.
The real problem There is no view of which existing URLs a new page will compete with. So every addition to a topic you already cover can split its own ranking. The conflict grows with the content library instead of being caught as it forms.
Reporting to clients
The client's main term is stuck on page two and they are on me about it. I am working on links and on-page tweaks while the real cause is two of their own pages competing for the search. Finding that by hand across the whole site takes hours I do not have. Even when I do fix it, I have no clean way to show the ranking settled.
The real problem With no automatic scan for competing URLs, the conflict gets treated with external fixes instead of consolidation. Without full history there is nothing to confirm a fix held. So effort goes to symptoms and the win cannot be proven.
Exec, owns the budget
I keep greenlighting more content on our core themes. More pages should mean more coverage. But the traffic on those topics has flattened, and it never occurred to me that the new pages might be cannibalising the old ones. The strategy I am funding could be the thing holding the rankings back.
The real problem When new pages compete with existing ones for the same searches, adding content stops compounding and starts diluting. With no visibility into the conflicts, the exec cannot see that the content investment is capping the very terms it is meant to grow.
How working with us works
A managed setup, scoped to your site. It is not a plan you configure yourself.
- 01
Discovery call
We look at your site and Search Console together, and agree on the pages and queries that matter most to you.
- 02
We build it in your BigQuery
We pull every query–page pair into your own warehouse and flag the conflicts, read-only, with nothing changed on your site.
- 03
It runs every day
New conflicts surface automatically as you publish, and every report stays current. Nothing for you to maintain.
A managed setup. You give read-only access, we run it, and your data stays in your own warehouse.
One query, more than one of your pages
The signature of cannibalization is a single search several of your URLs compete for at once, splitting the clicks and the position between them.
-
/blog/keyword-research-guidepos 8.2 210 clicks72% -
/blog/how-to-do-keyword-researchpos 14.6 64 clicks22% -
/guides/keyword-researchpos 22.1 18 clicks6%
-
/blog/site-audit-checklistpos 6.4 142 clicks73% -
/guides/technical-site-auditpos 11.9 53 clicks27%
Example conflicts. Yours are flagged from your own Search Console query–page data.
What you actually do with it
In the order you will use it, from the first conflict you spot to the report that flags the next one.
Watch Google switch between your URLs
Track a conflict over time. See when it started and which URL Google is showing, so once you consolidate you can confirm the position settled.
New conflicts flagged as you publish
Publish a page and it is checked against the queries it starts ranking for, so a fresh clash with an existing URL shows up on its own. There is no quarterly audit.
Every query–page pair, past the 1,000-row cap
The clashes that matter rarely sit in the top 1,000 rows. We pull every query–page pair into your warehouse, so conflicts below the fold surface too.
In every report, not one dashboard
Because the conflict list lives in your data layer, it joins Looker Studio, your BI and the digest email. New clashes reach you without anyone hunting for them.
The difference from doing it by hand
You can hunt cannibalization in Search Console, clicking query after query into the Pages tab. Here is what changes when every query–page pair is scanned in your warehouse instead.
By hand in Search Console
Manual, session-bound
- Finding a conflict
- By hand Click each query, open the Pages tab
- Insightlytics Every query scanned at once
- Coverage
- By hand The top 1,000 rows
- Insightlytics Every query–page pair, no cap
- Prioritising
- By hand Eyeball which one looks worse
- Insightlytics Ranked by the traffic at stake
- Ranking instability
- By hand 16 months, hard to compare
- Insightlytics Full history of URL switching
- Confirming a fix
- By hand Re-check by hand weeks later
- Insightlytics The conflict clears in view
- New conflicts
- By hand A manual audit each quarter
- Insightlytics Surfaced as pages publish
Pricing
Priced to your site, not a plan you pick
No tiers to choose between. Pricing depends on your site's size and data. We scope it with you on a quick call, and your data is always yours.
Frequently asked questions
If something is still unclear, a discovery call clears it up fast.
It is when more than one page on your site competes for the same search. Instead of one strong page, Google sees several overlapping ones and is unsure which to rank. So it may alternate between them, and each tends to perform worse than a single consolidated page would.