Content Cannibalization

Stop competing with yourself.

When two of your pages target one query, Google has to pick, and your ranking power splits while it decides. Search Console already shows the overlap. Murkuz hands those rows to Claude or ChatGPT so your agent can name the pair.

The friction

Two pages, same keyword, neither ranks well.

What content cannibalization is

Two or more pages on your site target the same keyword. Instead of one strong page, Google sees competing signals and ranks neither well. You are bidding against yourself for one position.

Why it is hard to spot

Each page looks fine on its own. The overlap only appears when you line the query up against every URL it triggered, which is a join Search Console will not do for you. Our keyword clustering tool groups overlapping queries so you can see the shape of it.

The signal is not hidden, it is just spread across rows. One query, several URLs, impressions split between them and none of them in the top five. Finding that by hand means exporting the query dimension, exporting the page dimension, and joining the two in a spreadsheet. Murkuz hands your agent the join.

In practice

Four questions, and no exports.

1

Find the overlapping queries

One call returns the queries where two or more of your own pages are competing, taken from your property rather than a crawl or an estimate.

Live_Cannibalization
2

Read the rows behind each one

Clicks, impressions, CTR and position for each competing URL, over any window your property holds. Your agent can slice it by country or device from there.

Search_Analytics
3

Work out which page should win

Google's own index status for a URL: crawled, indexed, and which URL Google picked as canonical. Often that answers the question on its own.

Inspect_URL
4

Make the change where the content lives

Merge, redirect or differentiate. Murkuz does not edit or publish your pages. It gives your agent the numbers to argue from, then you ask again next month against the same window.

The four shapes it usually takes.

Blog post against blog post

Two articles covering the same topic. Common when a content team publishes without checking what already exists.

Blog post against product page

Informational content competing with the transactional page. The post takes the clicks from the page that converts.

Category against subcategory

Ecommerce sites where a parent and a child category page end up targeting overlapping queries.

Old against new

A new article lands on the same keywords as an established one, with no internal linking or redirect to settle it.

Stop splitting your ranking power.

Connect Search Console once. Then ask Claude or ChatGPT which of your own pages are competing, and which one the rows say should win.

Free on one site, no card. Reading your own data is never metered.