Cannibalisation

Cannibalisation reads your Google Search Console data and finds searches that two or more of your pages share, where Google keeps changing which page it ranks. For each set of pages it shows the searches, each page’s share and position, and a plan: merge the pages, make each one clearly about its own searches, or leave them because both are useful.

It’s free for sites with up to 100 pages that get clicks. Bigger sites cost 1 credit ($1) per 1,000 pages, and the cost shows before you run it. Sign in, connect Search Console (read-only), pick a site and run it.

What you get

• Up to 100 sets of pages, best first, each with its searches, and each page’s share of the impressions, position and clicks from the last 28 days.
• How often Google changed which page ranks best in the last 56 days.
• A plan for each set: which page to keep, and what to do with the other.
• The internal links to point at the page you keep.
• CSV and JSON downloads of every run, and a link an AI agent can work through.

How it works

• It loads the last 56 days of your Search Console data, one day at a time, and keeps it up to date while you use it.
• It groups your searches into needs: the different ways people type one thing they want, found from the search results they share.
• A need counts as split when two or more pages each get at least 10% of its impressions and none gets more than 80%, and the page Google ranks best changed at least twice in 56 days. A page that shows for a need now and then is left alone, and so is a page that simply replaced another.
• It reads every page in each set, following redirects, and your site’s internal links. A page that already redirects to the other, or names it as canonical, is marked “Already fixed”.
• It leaves out searches for your own brand, searches with nothing to act on, and searches Google spreads over many pages of one template, such as the same search on every city page.
• It reads each page, then Jev, an AI model, decides whether the pages meet the same need for those searches.
• Merge when they do: keep the better page, move what only the other page covers into it, then consider a 301 redirect from the other page. A redirect is a high-impact change, so it is advised only when Jev is at least 70% sure and at least 10 clicks are at stake; otherwise the item says to check. It never tells you to delete a page.
• Differentiate when they meet different needs but compete: keep the searches on one page, and point the other page’s title and H1 at the searches it ranks for on its own.
• Leave when they meet different needs and the searches are broad: Google showing either page is fine.
• Link changes come from your real pages: which link to change, or which sentence to link. A link that already points at the right page is left alone.
• Sets with nothing to do are listed under Checked, with one line on why, not as tasks. Each set shows where its numbers come from and when its pages were read.

After you make a change

• Mark an item done when you have changed the pages. Cannibalisation measures the clicks of the page you kept 28 and 56 days later against the same number of days before, and shows the result on your site’s page.
• Dismiss an item you do not want to work on. It stays out of later runs.
• Run it again to see what is new, what is still open and what was resolved since the last run.