Find and fix keyword cannibalisation between your own pages

By

Use SEO Bot's Cannibalisation check to find pages that split the same Google searches, then merge them, make them distinct, or leave them.

Keyword cannibalisation is when two of your own pages show up for the same Google search. Neither one wins. One week Google ranks the first page, the next week the second, and the clicks get split between them.

You usually notice it by accident. You search for something you wrote about and an older post comes up instead of the new one. Or Search Console shows two URLs for the same query, both stuck on page one but never near the top.

SEO Bot has a Cannibalisation check for this. It reads 90 days of Search Console data, finds the searches where two pages each get a real share of the impressions, and tells you what to do with each pair: merge them, make each one distinct, or leave them alone.

At the end you’ll have a report of competing pages, the fixes made in your site’s source, and a follow-up on SEO Bot’s To Do list that checks whether one page now ranks for each search.

What you need

SEO Bot runs on macOS 14 or later, on Apple silicon and Intel Macs. After purchasing it, download the app zip from your Polar receipt, unzip it, and move SEO Bot.app into Applications. The receipt also has the MIT-licensed source code of the same version.

Cannibalisation needs Google Search Console, connected in the app’s Settings. That part takes a few minutes in the Google Cloud console: turn on the Search Console API, create an OAuth client of type Desktop app, paste its ID and secret into SEO Bot’s Settings, and click Connect with Google. SEO Bot only asks for read access. Search Console itself is free, so this check costs nothing to run.

The commands in this tutorial use seobot, the command line tool that ships inside the app. Install it with SEO Bot → Install Command Line Tool…. It goes into ~/.local/bin, so add that folder to your PATH if your shell can’t find it.

A source folder for the site is optional but worth it. With one, the report names the file to edit for each page, and the agent handoff works in that folder.

Before you start, check that Search Console is connected:

seobot status
Search Console  not set up
DataForSEO      not set up
Plausible       not set up

Set up data sources in the SEO Bot app's Settings. Data: /Users/flavio/Library/Application Support/SEO Bot

That’s a fresh install. The first line should say Search Console is connected before you go on.

The site, pages, searches and numbers in this tutorial are examples. hostingpicker.dev is a fictional hosting comparison site, and its source lives in /Users/flavio/dev/hostingpicker.

Add the site with its Search Console property

SEO Bot doesn’t guess which Search Console property belongs to which site. Each site has a Search Console property setting, like sc-domain:hostingpicker.dev or https://hostingpicker.dev/, and every Search Console tool reads from it. Without the property the check can’t fetch anything. The source folder matters too. It’s how SEO Bot turns /best-cheap-vps/ into src/posts/best-cheap-vps.md, and how the agent knows where to work. Set both once and every later run uses them.

When Search Console is already connected, seobot add picks the matching property for you:

seobot add https://hostingpicker.dev --source ~/dev/hostingpicker
Added hostingpicker.dev.

If the site is already there, change only what’s missing. seobot edit leaves every other setting as it is:

seobot edit hostingpicker.dev --source ~/dev/hostingpicker --search-console sc-domain:hostingpicker.dev
Updated hostingpicker.dev.

In the app, the same fields are in File → Site Settings… (⇧⌘,), under Source folder and Search Console property. New sites come from File → Add Site… (⌘N).

Run the Cannibalisation check

A search only counts as cannibalised when two pages both get a real share of it. A page that shows up once at position 60 isn’t competing with anything. So SEO Bot ignores searches with fewer than 50 impressions in the period, and only pairs pages that each get at least 10% of a search’s impressions. It also fetches the last 4 weeks one at a time to see which page ranked best each week. Each time the best page switches, that’s a “turn”. Turns are the clearest sign that Google can’t decide.

Run it from the terminal:

seobot run cannibalisation --site hostingpicker.dev

While it runs, it prints progress to stderr: first the 90 days of searches, then each of the 4 weeks. Then it saves the report and prints it as Markdown. In the app, click Cannibalisation in the sidebar and then Run.

This check doesn’t crawl or build your site. It only reads Search Console.

A run is also saved, so you can list it later:

seobot reports
ID        SITE               TOOL             DATE              FIXED  SUMMARY
3e1c5312  hostingpicker.dev  cannibalisation  2026-11-15 07:18         3 pairs of pages compete for the same searches. 1 should be merged and 1 made di

The summary is cut at the column width. The first characters of the ID are enough to refer to a report in every other command.

Read the three kinds of advice

The report gives every pair one of three labels, and they decide everything that follows. The rule is short. If one page already gets at least 85% of the clicks on the shared searches and no turns happened, it’s Leave: Google picked a winner. Otherwise, if the two pages share 40% or more of all their searches, it’s Merge, because Google sees them as one topic. Below that it’s Make distinct: each page has a reason to exist, but one of them is poaching the other’s searches.

Print the newest report:

seobot report latest --site hostingpicker.dev --tool cannibalisation

It opens with the period and the totals:

# Cannibalisation for hostingpicker.dev

Aug 14 – Nov 11, 2026 · Run Nov 15, 2026 at 7:18 AM

3 pairs of pages compete for the same searches. 1 should be merged and 1 made distinct.

## Numbers

- Competing pairs: 3
- Merge: 1
- Make distinct: 1
- Leave: 1

The period covers the last 90 days of data, and it ends a few days before the run date. Further down, each pair has a finding with three numbers. Impressions adds up the shared searches. Overlap is the share of all searches either page appears for that both pages appear for. Turns is how many times the best page switched in 4 weeks.

How SEO Bot picks the advice for a pair of pagesA pair is left alone when one page gets at least 85% of the shared clicks and the best page never switched. Otherwise pages sharing 40% or more of their searches get merged, and the rest get made distinct.YesNoYesNoTwo pages each get10%+ of a search'simpressionsOne page has 85%+ ofthe clicks and 0turns?Leave: Googlealready pickedOverlap 40% or more?Merge into the pagewith more clicks,301 the otherMake distinct: onepage owns thesearches, the otherlinks to it

Example 1: merge two pages about the same thing

hostingpicker.dev has /cheap-vps-hosting/ and /best-cheap-vps/, written a year apart. Here’s their finding:

### /cheap-vps-hosting/ and /best-cheap-vps/

https://hostingpicker.dev/cheap-vps-hosting/
Merge · 4 shared searches
Impressions: 18,550 · Overlap: 80% · Turns: 3

- The two pages share 80% of their searches, so Google sees them as the same topic. Google switched which page ranks best 3 times in 4 weeks.
- Move what's unique in /best-cheap-vps/ into /cheap-vps-hosting/, then redirect /best-cheap-vps/ to /cheap-vps-hosting/ with a 301.

  - **cheap vps hosting** (9,500 impressions): /cheap-vps-hosting/ at 4.2 with 210 clicks, /best-cheap-vps/ at 5.8 with 140
  - **cheap vps** (4,800 impressions): /cheap-vps-hosting/ at 6.1 with 90 clicks, /best-cheap-vps/ at 7.4 with 70
  - **best cheap vps** (3,200 impressions): /best-cheap-vps/ at 4.9 with 75 clicks, /cheap-vps-hosting/ at 5.3 with 60
  - **budget vps hosting** (1,050 impressions): /cheap-vps-hosting/ at 8.0 with 20 clicks, /best-cheap-vps/ at 9.2 with 14

Three turns in four weeks, and neither page above position 4. That’s the classic pattern. The page with more clicks overall, /cheap-vps-hosting/, is the one to keep. The next section turns that into three steps.

Merge pages and redirect the old URL

Merging is the destructive fix, so it’s worth slowing down. You delete a page that has links pointing at it and some ranking history. A 301 redirect is what keeps that from being lost: it tells browsers and Google the page moved for good, and sends visitors to the new address. Google treats a permanent redirect as a strong sign that the target should be the page shown in results, as its redirects documentation explains. Skip the redirect and old links land on a 404.

With a source folder set, the report’s Tasks section names the files:

## Tasks

Each heading is a file to edit, relative to /Users/flavio/dev/hostingpicker, with the page it builds. "Find" is the text to look for in it.

### src/posts/cheap-vps-hosting.md

Page: https://hostingpicker.dev/cheap-vps-hosting/

- [ ] Move what's unique in /best-cheap-vps/ into this page, so it covers “cheap vps hosting”, “cheap vps”, “best cheap vps” on its own.

### src/posts/best-cheap-vps.md

Page: https://hostingpicker.dev/best-cheap-vps/

- [ ] Delete this page once its content is in /cheap-vps-hosting/.

### Across the site

- [ ] Redirect /best-cheap-vps/ to /cheap-vps-hosting/ with a 301, and update the links that point to /best-cheap-vps/.

The order matters. Copy the content first, then delete. SEO Bot never deletes or edits files itself. It only writes these instructions, so nothing is gone until you or your agent remove the file. Git is your undo if you change your mind.

SEO Bot matches pages to files by the last part of the URL, by file names, and by slug: or permalink: in Markdown frontmatter. When no file matches, the heading falls back to the page path and you find the file yourself.

Make two pages distinct

Some pairs shouldn’t be merged. A review of Netlify and a comparison of Netlify with Cloudflare Pages are different pages for different readers. They only collide on the comparison searches. Merging them would throw away a page that ranks well for its own searches. The fix is to decide which page owns the shared searches and keep the other off them. SEO Bot picks the owner by how well its URL matches the searches, or, when the URLs fit equally, by which page gets more clicks on them.

Example 2: two pages with different jobs

The same report has this finding:

### /netlify-review/ and /cloudflare-pages-vs-netlify/

https://hostingpicker.dev/netlify-review/
Make distinct · 2 shared searches
Impressions: 6,000 · Overlap: 33% · Turns: 2

- The pages share only 33% of their searches, so each has a reason to exist. Google switched which page ranks best 2 times in 4 weeks.
- /cloudflare-pages-vs-netlify/ should be the page for the searches below, since its URL matches them best. Keep them in its title and H1, and keep the title and H1 of /netlify-review/ on its own angle.
- Link from /netlify-review/ to /cloudflare-pages-vs-netlify/ with the main search as the anchor.

/netlify-review/ gets more clicks overall, from “netlify review” and “netlify pricing”. That’s why it’s listed first. But the comparison URL fits the shared searches, so it owns them. The task touches only the review: keep its title, H1 and intro about reviewing Netlify, and add one link to the comparison with “netlify vs cloudflare pages” as the anchor text. Nothing gets deleted and nothing needs a redirect.

The third pair in the report is labelled Leave:

- One page gets 94% of the clicks for these searches and ranked best every week. Google already picked it, so there's nothing to fix.

Leave pairs have no tasks. If you want more internal links from the weaker page anyway, find orphan and weakly linked pages covers that.

Hand the fixes to a coding agent

You can edit the files by hand from the Tasks list. If you use Cursor or Codex, the report can go to them instead. seobot prompt saves the report as Markdown next to its data and prints the prompt an agent needs. That prompt explains what Merge, Make distinct and Leave mean, so the agent doesn’t have to guess:

seobot prompt latest --site hostingpicker.dev --tool cannibalisation
Use the Cannibalisation report SEO Bot made for hostingpicker.dev (https://hostingpicker.dev/) to improve the site.

3 pairs of pages compete for the same searches. 1 should be merged and 1 made distinct.

Apply the recommendation for each pair of pages. Merge: move what's unique from the weaker page into the stronger one, delete the weaker page and add a permanent redirect to the stronger one. Make distinct: change the title, H1 and intro of one page so each targets a different search, and link between them. Leave: change nothing.

The full report is in /Users/flavio/Library/Application Support/SEO Bot/reports/E0E6051E-7067-4B7B-B9EE-506C6B0DEF1D/3E1C5312-096F-486C-85FF-89D938A1F72E.md. `seobot report 3e1c5312` prints it too, and adding `--json` gives the data.

The rest of the prompt tells the agent to work in /Users/flavio/dev/hostingpicker, to verify, commit and push its changes, and to run seobot fixed with a note when it’s done. If the site has no source folder, it asks for a list of changes to apply by hand instead.

Add --cursor or --codex to open a new agent with the prompt. In the app, the report has Fix with Cursor and Fix with Codex buttons. Either way the prompt waits for you to send it, so you can read it first. Right-click a single finding and choose Fix This with Cursor, Fix This with Codex or Copy Prompt for This to send only that pair. I’d do that for a merge, since it deletes a page, and send the distinct pairs as a batch. The SEO checks from the terminal post shows how the other SEO Bot reports go to agents the same way.

Mark the report fixed and let the follow-up check it

A fix to cannibalisation can’t be judged the next day. Google needs to recrawl both pages, follow the redirect and settle on one URL, and Search Console data arrives with a delay. So marking a report fixed doesn’t just tick a box. It records what you did, which findings you skipped on purpose, and schedules a rerun 4 weeks later. Without the mark, SEO Bot can’t tell you whether the change worked, because it doesn’t know which findings you acted on.

The agent runs this itself. If you made the changes by hand, run it yourself:

seobot fixed 3e1c --skip /static-site-hosting/ --note "Merged /best-cheap-vps/ into /cheap-vps-hosting/ with a 301, retitled /netlify-review/ (a1b2c3d)"
Marked 3e1c5312, Cannibalisation for hostingpicker.dev as fixed on Nov 15, 2026.
Skipped 1 finding:
  https://hostingpicker.dev/static-site-hosting/
Note: Merged /best-cheap-vps/ into /cheap-vps-hosting/ with a 301, retitled /netlify-review/ (a1b2c3d)
Follow-up on Dec 13, 2026: Run Cannibalisation again and check whether one page now ranks for each search, for the 2 fixes from Nov 15.

--skip takes a finding’s path, URL or ID. Skipping the Leave pair keeps the follow-up honest: it counts 2 fixes, not 3. The follow-up shows up in the to-do list:

seobot todo --site hostingpicker.dev
December 2026
  Dec 13  2835327a  hostingpicker.dev  Run Cannibalisation again and check whether one page now ranks for each search, for the 2 fixes from Nov 15.

Running seobot fixed again replaces the earlier mark. If you marked the wrong report, seobot fixed 3e1c --undo clears it and removes the follow-up. In the app, Mark as Fixed and Undo do the same. Until the follow-up is due, Run Again stays unavailable in the app, but an explicit seobot run works at any time. While the app is open, it also reruns Cannibalisation on its own every 4 weeks and adds new pairs to To Do.

When the follow-up runs, the to-do shows how many of the fixed findings the new report no longer flags. Two out of two means each search now has one page.

Example 3: the follow-up fails because Google disconnected

Four weeks later you click Run on the follow-up, and it stops with:

Your Google connection expired or was revoked. In Settings → Google Search Console, click Disconnect, then Connect with Google. Sign in again, then rerun the tool.

This is common with a new OAuth client. If its consent screen is still in Testing, Google expires the refresh token after 7 days for this scope, as its OAuth token expiration rules say. In the app, SEO Bot opens Google sign-in and retries the tool once after you reconnect. From the terminal, do what the message says, then run seobot run cannibalisation --site hostingpicker.dev again. Your saved reports and the fixed mark stay as they were.

If something looks wrong

  • If seobot run cannibalisation stops with “Search Console isn’t connected. Connect it in Settings.”, open SEO Bot’s Settings, paste the OAuth client ID and secret, and click Connect with Google.
  • If it stops with “Pick the Search Console property for hostingpicker.dev in the site’s settings.”, set the property in Site Settings… or with seobot edit hostingpicker.dev --search-console sc-domain:hostingpicker.dev.
  • If the report says “No two pages split the impressions of the same searches.”, there’s nothing to fix in the last 90 days. Searches under 50 impressions don’t count, so a small or new site often gets this.
  • If a page you expected is missing, check that both pages get at least 10% of the search’s impressions. Pages with a handful of impressions for a query aren’t treated as competitors.
  • If a Tasks heading shows a page path instead of a file, SEO Bot couldn’t match the URL to a file in the source folder. Check that Source folder points at the project root, or find the file by hand.
  • If the prompt says the site’s source isn’t on this Mac, set the source folder with seobot edit hostingpicker.dev --source ~/dev/hostingpicker and print the prompt again.
  • If Run Again is greyed out after marking the report fixed, that’s the follow-up waiting for new data. Use seobot run cannibalisation to run it early.
  • If the old URL returns a 404 after a merge, the redirect wasn’t deployed. Add the 301 from the Across the site task and check it in a browser before you mark the report fixed.

Get SEO Bot

Run 16 SEO checks on your websites and turn each report into concrete work for you, Cursor or Codex. Includes a native Mac app, CLI and full MIT source.

See SEO Bot → · Read the docs · $20. See the app page for tax details, with full source code.

More tutorials for my apps →

Want me to talk about your product? You can sponsor this site.