Find keyword cannibalization with AI

1. Find the split queries. The agent calls search_insights with the cannibalization recipe. It returns queries where at least two pages each hold 10% or more of the impressions (with at least 10 impressions in total), plus each page's position, impressions and clicks. One data pull.
2. Profile each competing page. For the top queries, the agent calls search_analytics with dimensions query,page, filtered to each competing page. The full query list shows whether a page is a broad overview, a how-to or a comparison, which is what decides the winner. One data pull per page; for one pair that is two.
3. Pick a winner and an action. The agent weighs intent first (which page should answer this search), then clicks and position as evidence, and proposes keep, merge and redirect, or de-optimize and link.

A run with one or two competing pairs costs about 2 to 6 data pulls. On a large site with many pairs, ask for the top 3 queries only to keep it inside the free plan's 15 pulls a day.

This is a real run on mcpsearchconsole.com, for 2 September to 30 September 2026. The recipe found one cannibalized query:

Total: 31 impressions, 0 clicks, split across two pages. The per-page search_analytics calls added context. Over the same window the homepage ranked for product queries such as "mcp search console claude" (position 5.6, 2 clicks) and "google search console mcp" (position 54.0, 136 impressions). The round-up post ranks for comparison wording.

The agent's verdict: the query says "best ... servers", which is comparison intent, so the round-up post should win. The homepage should not be merged or redirected (it is the product page and earns the site's clicks); instead it should avoid "best servers" phrasing and link to the round-up for readers who want a comparison. The agent also flagged that both pages sit far below page one, so fixing the split alone will not bring clicks; the winning page also needs ranking work.

That last point is honest and worth keeping in mind: cannibalization is one cause of weak rankings, not the only one.

For each query in the table, apply the rule that fits.

• Same intent, one page clearly stronger. Merge the useful parts of the weaker page into the stronger one, then 301 redirect the weaker URL to it. This is the cleanest fix when both pages answer the same question.
• Same intent, both pages earn clicks for other queries. Keep both. Remove or rewrite the competing wording on the loser (title, H1, the section that targets the query), and add a link from the loser to the winner with anchor text that matches the query.
• Different intents. If one page is a product page and the other a comparison or a how-to (as in the example), the split may be temporary while Google works out which one fits. Make the difference obvious in titles and headings, link between them, and re-check in a month.
• A homepage or category page is one of the two. Almost never redirect it. De-optimize it for the specific query and link out to the detailed page.
• Tiny numbers. Under about 20 impressions in 28 days, the split can be noise. Note it and re-run later before merging anything.

Pick the action, make the change, and re-run the prompt in four weeks to see whether the impressions have consolidated on the winner. This page is about fixing pages that already compete. To stop new pages from competing before you publish them, see how to plan a content calendar without cannibalization.

• It cannot see why Google split the query. Search Console shows the split, not the reason. Read both pages before merging; sometimes the fix is a clearer title, not a redirect.
• Sharing is not always harmful. Two of your pages in the top five for one query is a good result. The recipe flags shares above 10% each, so check positions before treating every row as a problem.
• Page-level data is per URL. Parameters, trailing slashes or http and https versions can show as separate pages. That is a canonical issue, not content cannibalization; an index coverage audit is the better tool for it.
• No backlink data. The page with more links pointing to it may be the better one to keep even if it ranks lower today. Search Console MCP does not report links, so check that elsewhere before redirecting.
• Anonymized queries are hidden. Rare queries are withheld by Google, so some overlap between pages may not show up at all.

Comparing tools that can do this? Our list of the best SEO MCP servers covers the options. To connect your data first, follow the guide to use Search Console in ChatGPT.