Keyword cannibalization

Cannibalization built as a workflow, not a chart.

Detection is the easy part. SERPVoyager runs every cannibalization pair as a ticket: detected, triaged, decided on, monitored. Re-opens it the moment a “resolved” issue creeps back.

The workflow

Closer to Linear than to a CSV export.

Every cannibal pair carries a status, an owner, and an audit trail. The chart is a side-effect; the queue is the product.

Issue · CA-138
Resolved
Keyword
nike pegasus 41
Pattern
Wrong Page
URLs
/running-shoes/nike/winning
#4
/running-shoes/nike/pegasus-41/
#11
Decision
301 → /running-shoes/nike/pegasus-41/
Activity
  • May 02DetectedNightly scan flagged the pair.
  • May 03Triaged@maja · pattern: Wrong Page
  • May 05Decision301 → /running-shoes/nike/pegasus-41/
  • May 07Auto-closedSignal cleared for 2 consecutive days.
  • May 18Re-checkedStill clean (11 d) — auto-reopen armed.
Auto-reopens if pattern returns above threshold for ≥ 7d
  1. 01

    Detected

    Nightly scan flags any pair of owned URLs competing on the same SERP. Thresholds tuned to skip noise — a single slider re-tunes them.

  2. 02

    Triaged

    Issue gets a pattern label (Wrong page, Multi-URL, URL flipping), an owner, and a target page. Comment, snooze, link out to your tracker.

  3. 03

    Decided

    Three actions, audit-logged: redirect, de-target one URL, or coexist. The decision becomes data you can filter on later.

  4. 04

    Monitored

    Resolved doesn’t mean ignored. Daily re-check. Auto-reopen if the signal returns above threshold for ≥ 7 days.

How we detect it

Signal, not noise.

We don’t hand you a pile of “possible” cannibalizations and walk away. The daily crawl evaluates every tracked keyword and surfaces only the cases that match one of three named patterns.

  • Wrong Page

    You’re ranking, but Google chose a different URL than the one you declared as the target.

  • Multi-URL

    More than one of your URLs is showing up on the same SERP for the keyword.

  • URL Flipping

    Google keeps switching which of your URLs ranks across days.

Detection signals
CA-138
Wrong Page

7 issues

Multi-URL

4 issues

Flipping

2 issues

Signals fired
  • Same SERP
    US · mobile · location: any
  • Owned URLs in top 20
    2 URLs (#4, #11)
  • Position swap rate ≥ 30%
    42% over last 14d
  • Sustained ≥ 7 days
    12 consecutive d above threshold
Confidence92% / threshold 75%
Rechecked nightly · per-project thresholds on the roadmap

Rechecked nightly on the same daily crawl that powers rankings, movers, and Share of Voice.

What it pairs with

Four neighbors in the product that make the workflow tick.

Cannibalization tracking doesn’t live in a corner; it inherits the data model, the daily cadence, and the click-weighted metrics every other report uses.

01

Built on the URL-centric data model.

Two URLs ranking for the same keyword is impossible to define without the URL-keyword link. The data model is the prerequisite — read the post if you haven’t.

02

Re-checked nightly, automatically.

Cannibalization shifts day to day as the SERP shuffles. Detection runs on the daily crawl — same cadence as the rest of the product, no separate batch job to babysit.

03

Surfaces in Movers when the swap is fresh.

A cannibal pair often shows up as “page A lost / page B gained” in today’s movers. Both views point at the same underlying issue; you triage from either entry point.

04

Quantifies the SoV cost.

Cannibal pairs typically cap each other at a worse CTR position than either could hold alone. Click-weighted SoV makes that cost legible — before and after the decision.

Common questions

The four questions we get on every demo.

Doesn’t ranking on multiple pages mean more SERP real estate?

Occasionally yes, when it’s a real sitelink stack or a featured snippet + organic combo. The far more common case is two pages bouncing between #4 and #11, where neither holds a great click-through position. The workflow handles both: classify as “coexist” if it’s a real stack, “redirect” or “de-target” if it isn’t. The decision is logged either way.

What separates a real cannibalization from noise?

Only issues that match one of three named patterns make the queue. Wrong Page (you rank, but on a URL that isn’t your declared target), Multi-URL (more than one of your URLs appears in the SERP for the keyword), or URL Flipping (Google keeps switching which URL ranks across days). Anything that doesn’t match one of those isn’t a cannibalization in our model — it stays out of the queue.

Do I have to consolidate the pages, or can they coexist?

Both are valid decisions. “Coexist” is a first-class action with the same audit trail as “redirect” or “de-target”, useful when, say, a /blog post is intentionally ranking alongside a /shoes/ category page for branded queries. Filter the queue by decision later to see what you’ve chosen to live with.

How often is the queue re-checked?

Nightly, on the same daily crawl that powers rankings, movers, and SoV. If you mark an issue Resolved and the SERP keeps showing the pattern, the issue is flagged as “still detected” so it doesn’t quietly fall off your queue.

Other questions?See full pricing & FAQ
See your cannibalization queue

See every cannibalization on your site, by tomorrow morning.

Plug in your keywords today. Tomorrow morning, every Wrong Page, Multi-URL, and URL Flipping issue across your keywords is surfaced and ready to triage, assign, and resolve as a workflow.

14-day free trial. No credit card.