Content and On-Page SEO skill 12 of 13

Keyword Cannibalisation SKILL.md

The Keyword Cannibalisation skill makes Claude, Codex or another AI agent find pages on your own site that compete for the same searches and fix them. It reads Search Console query and page data to spot rankings that swap between URLs, separates real cannibalisation from healthy double listings, then merges, redirects, re-targets, canonicalises or re-links so each intent has one clear page.

keyword-cannibalisation/SKILL.md, version 1.0.0, 1,130 words.

Cannibalisation happens when two or more pages on one site serve the same intent, so search engines keep switching between them or rank neither as well as one strong page would. It is common on blogs that published similar posts over the years, on sites with overlapping category and guide pages, and after migrations.

Not every overlap is a problem. Two of your pages ranking together at the top is a good outcome. This skill tells the difference and fixes the cases that cost traffic.

Operating principles

  1. Intent, not words. Pages compete when they answer the same need, not because they share a keyword.
  2. Evidence from Search Console. Look for queries where several URLs take impressions and the ranking URL keeps changing.
  3. Healthy overlap is fine. A guide and a product page both ranking for a mixed-intent query can be ideal.
  4. One intent, one page. Fixes aim for a clear owner per intent.
  5. Keep the value. Merges keep the best content, the stronger URL and the links of both pages.

When to use, and when not to

Use it when rankings swap between URLs, when the wrong page ranks, after content audits find duplicate topics, and before publishing a page on a topic you may already cover.

Don't use it for technical duplicates such as parameter or protocol variants (use the Technical SEO canonicalization skill) or for a page that simply underperforms on its own (on-page-seo).

Inputs to ask for, in one message

  1. Search Console data by query and page for 3 to 16 months.
  2. A crawl with titles, H1s, canonicals, word counts and inlinks.
  3. Backlinks by URL and conversions by landing page.
  4. Any queries or topics already suspected.

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as keyword-cannibalisation/SKILL.md.

---
name: keyword-cannibalisation
description: "Find and fix pages on the same site that compete for the same searches: detect overlap from Search Console page and query data, separate real cannibalisation from healthy double listings, then merge, redirect, re-target, canonicalise or re-link so each intent has one clear page. Use whenever someone mentions keyword cannibalisation or cannibalization, pages competing with each other, rankings swapping between URLs, two posts on the same topic, the wrong page ranking, or unstable positions."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/content-seo/keyword-cannibalisation/
  category: marketing
  subcategory: content-seo
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Keyword Cannibalisation

Cannibalisation happens when two or more pages on one site serve the same intent, so search engines keep switching between them or rank neither as well as one strong page would. It is common on blogs that published similar posts over the years, on sites with overlapping category and guide pages, and after migrations.

Not every overlap is a problem. Two of your pages ranking together at the top is a good outcome. This skill tells the difference and fixes the cases that cost traffic.

## Operating principles
1. **Intent, not words.** Pages compete when they answer the same need, not because they share a keyword.
2. **Evidence from Search Console.** Look for queries where several URLs take impressions and the ranking URL keeps changing.
3. **Healthy overlap is fine.** A guide and a product page both ranking for a mixed-intent query can be ideal.
4. **One intent, one page.** Fixes aim for a clear owner per intent.
5. **Keep the value.** Merges keep the best content, the stronger URL and the links of both pages.

## When to use, and when not to
Use it when rankings swap between URLs, when the wrong page ranks, after content audits find duplicate topics, and before publishing a page on a topic you may already cover.

Don't use it for technical duplicates such as parameter or protocol variants (use the Technical SEO canonicalization skill) or for a page that simply underperforms on its own (`on-page-seo`).

## Inputs to ask for, in one message
1. Search Console data by query and page for 3 to 16 months.
2. A crawl with titles, H1s, canonicals, word counts and inlinks.
3. Backlinks by URL and conversions by landing page.
4. Any queries or topics already suspected.

## Workflow

### Step 1. Find candidates
From Search Console, list queries where two or more of your URLs each have a meaningful share of impressions. Add pages with very similar titles or H1s from the crawl.

### Step 2. Check the pattern
For each query, chart which URL ranked by day or week. Frequent switching, both pages stuck lower than expected, or the less relevant page ranking all point to cannibalisation. Two pages steady near the top is usually fine.

### Step 3. Check intent
Read the live results and both pages. Do they serve the same need in the same format? If one is a guide and one is a product page, and results show both types, they may coexist with clearer targeting.

### Step 4. Choose a fix
| Situation | Fix |
|---|---|
| Same intent, both pages useful | Merge into the stronger URL, 301 the other |
| Same intent, one page weak and unlinked | Redirect the weak page, or remove it if it has no value |
| Different intents, unclear targeting | Re-target: rewrite titles, H1s and content so each page owns its intent; link between them |
| Both pages needed for users (for example print or region versions) | Canonical from the variant to the main page |
| Internal links point at the wrong page | Change anchors and links so the owner page gets them |

### Step 5. Pick the surviving URL
Choose the URL with the most links, traffic and conversions, and the cleaner address. Move the best content from the other page into it.

### Step 6. Implement
Merge content, set 301 redirects, update internal links, sitemaps and navigation, and remove the retired URL from any templates.

### Step 7. Measure
Watch the query set for 6 to 12 weeks: one URL should settle and position should improve or hold with higher clicks.

## Preventing it
- Check the site for existing pages before briefing new content.
- Keep a topic register mapping each intent to one URL.
- Use the topical map to give every page a distinct job.
- Link to the owner page with consistent, descriptive anchors.

## Worked example
A travel insurance site had three posts on "travel insurance for pre-existing conditions", written in 2021, 2023 and 2025. Search Console showed all three taking impressions for the main query, with the ranking URL changing every few days and positions between 9 and 15. The 2023 post had most backlinks; the 2025 post had the most current information. The 2025 content was merged into the 2023 URL, the other two were redirected to it, and internal links were updated. Within eight weeks one URL ranked steadily in position 4, and clicks for the query group roughly doubled.

## Output format
```
# Cannibalisation review: <site>, <date>
## Summary (query groups affected, pages involved, expected gain)
## Findings
| Query group | URLs competing | Impression split | Ranking pattern | Same intent? | Fix | Surviving URL |
## Implementation steps (content to move, redirects, links to update)
## Measurement plan
```

## Merge playbook
1. Choose the surviving URL (most links, traffic and conversions; cleaner address).
2. Outline the merged page: keep every section that ranks or earns links from both pages.
3. Rewrite into one coherent page; remove repetition.
4. Keep the surviving URL; 301 the retired URL to it.
5. Update internal links, navigation, sitemaps and any canonical tags.
6. Request indexing for the surviving URL.
7. Watch the query group for six to twelve weeks.

## Diagnosing from Search Console
1. Export the Performance report by query and page for 3 to 16 months.
2. Filter to queries with two or more ranking URLs.
3. For each, chart which URL ranked each week and its position.
4. Flag queries where the ranking URL changes often, or where the less relevant URL ranks.
5. Check impressions split: if both URLs share impressions and neither holds a top position, overlap is likely hurting.
6. Read both pages and the live results before deciding to merge, differentiate or leave them.

## Differentiating instead of merging
When both pages deserve to exist, give each a distinct intent: one for buying (category or product), one for learning (guide). Update titles, H1s and introductions to match, and link between them with descriptive anchors so search engines and readers see their different jobs.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Category page and blog post compete | Give the category page buying intent and the post learning intent; link between them |
| Location pages compete across cities | Make each page clearly local, or consolidate if content is identical |
| Old and new versions of an annual guide | Keep one evergreen URL and update it each year |
| Product variants on separate URLs | Consolidate to one page with options, or canonicalise variants |
| Two pages both steady in the top three | Leave them; it's a strength |

## Handoffs to related skills
- Redirect rules and tests: the Technical SEO `redirects-status-codes` skill
- Link updates: the Technical SEO `internal-linking` skill
- Rewriting merged content: `seo-content-writing`
- Preventing new overlap: `topical-map`, `content-brief`
- Finding overlap across the site: `content-seo-audit`

## Quality bar: what an excellent review includes
- Evidence of competition from Search Console, not just similar titles.
- An intent judgement for each pair.
- A surviving URL chosen on links, traffic and conversions.
- Redirects, link updates and a measurement plan.

## Common mistakes
- Merging pages that serve different intents.
- Choosing the newer URL by default and losing older links.
- Using noindex instead of merging, which wastes the weaker page's signals.
- Forgetting to update internal links after a merge.
- Treating every shared query as a problem.

## Questions to ask before you recommend changes
- Which page converts better, and which has the stronger links?
- Is there a business reason to keep both pages?
- Who can redirect URLs and update links?

## Self-check before you answer
- Is each case backed by Search Console query and page data?
- Did I confirm the intents match before merging?
- Does the surviving URL keep the best content and links?
- Are redirects and internal links part of the plan?

## Official documentation
- Consolidate duplicate URLs: https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls
- Redirects and Google Search: https://developers.google.com/search/docs/crawling-indexing/301-redirects
- Search Console Performance report: https://support.google.com/webmasters/answer/7576553

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/content-seo/keyword-cannibalisation/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Find candidates

From Search Console, list queries where two or more of your URLs each have a meaningful share of impressions. Add pages with very similar titles or H1s from the crawl.

Step 2. Check the pattern

For each query, chart which URL ranked by day or week. Frequent switching, both pages stuck lower than expected, or the less relevant page ranking all point to cannibalisation. Two pages steady near the top is usually fine.

Step 3. Check intent

Read the live results and both pages. Do they serve the same need in the same format? If one is a guide and one is a product page, and results show both types, they may coexist with clearer targeting.

Step 4. Choose a fix

SituationFix
Same intent, both pages usefulMerge into the stronger URL, 301 the other
Same intent, one page weak and unlinkedRedirect the weak page, or remove it if it has no value
Different intents, unclear targetingRe-target: rewrite titles, H1s and content so each page owns its intent; link between them
Both pages needed for users (for example print or region versions)Canonical from the variant to the main page
Internal links point at the wrong pageChange anchors and links so the owner page gets them

Step 5. Pick the surviving URL

Choose the URL with the most links, traffic and conversions, and the cleaner address. Move the best content from the other page into it.

Step 6. Implement

Merge content, set 301 redirects, update internal links, sitemaps and navigation, and remove the retired URL from any templates.

Step 7. Measure

Watch the query set for 6 to 12 weeks: one URL should settle and position should improve or hold with higher clicks.

Preventing it

  • Check the site for existing pages before briefing new content.
  • Keep a topic register mapping each intent to one URL.
  • Use the topical map to give every page a distinct job.
  • Link to the owner page with consistent, descriptive anchors.

Worked example

A travel insurance site had three posts on "travel insurance for pre-existing conditions", written in 2021, 2023 and 2025. Search Console showed all three taking impressions for the main query, with the ranking URL changing every few days and positions between 9 and 15. The 2023 post had most backlinks; the 2025 post had the most current information. The 2025 content was merged into the 2023 URL, the other two were redirected to it, and internal links were updated. Within eight weeks one URL ranked steadily in position 4, and clicks for the query group roughly doubled.

Output format

# Cannibalisation review: <site>, <date>
## Summary (query groups affected, pages involved, expected gain)
## Findings
| Query group | URLs competing | Impression split | Ranking pattern | Same intent? | Fix | Surviving URL |
## Implementation steps (content to move, redirects, links to update)
## Measurement plan

Merge playbook

  1. Choose the surviving URL (most links, traffic and conversions; cleaner address).
  2. Outline the merged page: keep every section that ranks or earns links from both pages.
  3. Rewrite into one coherent page; remove repetition.
  4. Keep the surviving URL; 301 the retired URL to it.
  5. Update internal links, navigation, sitemaps and any canonical tags.
  6. Request indexing for the surviving URL.
  7. Watch the query group for six to twelve weeks.

Diagnosing from Search Console

  1. Export the Performance report by query and page for 3 to 16 months.
  2. Filter to queries with two or more ranking URLs.
  3. For each, chart which URL ranked each week and its position.
  4. Flag queries where the ranking URL changes often, or where the less relevant URL ranks.
  5. Check impressions split: if both URLs share impressions and neither holds a top position, overlap is likely hurting.
  6. Read both pages and the live results before deciding to merge, differentiate or leave them.

Differentiating instead of merging

When both pages deserve to exist, give each a distinct intent: one for buying (category or product), one for learning (guide). Update titles, H1s and introductions to match, and link between them with descriptive anchors so search engines and readers see their different jobs.

Edge cases and judgement calls

SituationWhat to do
Category page and blog post competeGive the category page buying intent and the post learning intent; link between them
Location pages compete across citiesMake each page clearly local, or consolidate if content is identical
Old and new versions of an annual guideKeep one evergreen URL and update it each year
Product variants on separate URLsConsolidate to one page with options, or canonicalise variants
Two pages both steady in the top threeLeave them; it's a strength
  • Redirect rules and tests: the Technical SEO redirects-status-codes skill
  • Link updates: the Technical SEO internal-linking skill
  • Rewriting merged content: seo-content-writing
  • Preventing new overlap: topical-map, content-brief
  • Finding overlap across the site: content-seo-audit

Quality bar: what an excellent review includes

  • Evidence of competition from Search Console, not just similar titles.
  • An intent judgement for each pair.
  • A surviving URL chosen on links, traffic and conversions.
  • Redirects, link updates and a measurement plan.

Common mistakes

  • Merging pages that serve different intents.
  • Choosing the newer URL by default and losing older links.
  • Using noindex instead of merging, which wastes the weaker page's signals.
  • Forgetting to update internal links after a merge.
  • Treating every shared query as a problem.

Questions to ask before you recommend changes

  • Which page converts better, and which has the stronger links?
  • Is there a business reason to keep both pages?
  • Who can redirect URLs and update links?

Self-check before you answer

  • Is each case backed by Search Console query and page data?
  • Did I confirm the intents match before merging?
  • Does the surviving URL keep the best content and links?
  • Are redirects and internal links part of the plan?

Official documentation

When to use this skill, and when not to

Use it when rankings keep switching between two of your URLs, when the wrong page ranks for an important query, when an audit finds several posts on the same topic, after a migration, and before publishing a page on a topic you may already cover.

Don’t use it for technical duplicates such as parameter, protocol or trailing-slash variants (use Canonicalization) or for a single page that underperforms on its own (use On-Page SEO Optimisation).

Example prompts

  • “Find queries where two of our URLs compete and tell me which to merge.”
  • “We have three posts on travel insurance for pre-existing conditions. What should we do?”
  • “Our category page and our buying guide swap rankings every week. Is that a problem?”
  • “Check whether this new article would compete with anything we already have.”
  • “Plan the redirects and link changes for these five merges.”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# Cannibalisation review: example.com, 10 October 2026

## Findings (extract)
| Query group | URLs | Impression split | Pattern | Same intent? | Fix | Survivor |
| pre-existing conditions travel insurance | 3 | 41/33/26% | URL switches every few days, pos 9-15 | Yes | Merge, 301 two | 2023 post (most links) |
| best running shoes | 2 | 60/40% | Both steady in top 5 | No (guide vs category) | Keep both, clarify titles | n/a |

Two of your pages ranking together near the top is treated as a good outcome, not a problem; only harmful overlap is fixed.

What the agent needs from you

The skill asks for Search Console data by query and page for three to sixteen months, a crawl with titles, H1s, canonicals, word counts and inlinks, backlinks by URL, conversions by landing page, and any queries or topics you already suspect.

How this skill hands off to related skills

Fixing overlap involves several skills. Redirect rules and testing come from Redirects and HTTP Status Codes, link updates from Internal Linking and Site Architecture, and merged content is rewritten with SEO Content Writing. To stop it happening again, every new page is checked against the topical map before a brief is written.

How to run the Keyword Cannibalisation skill step by step

  1. Install the skill as keyword-cannibalisation/SKILL.md.
  2. Export Search Console data by query and page for three to sixteen months.
  3. Add a crawl with titles, H1s, canonicals, word counts and inlinks.
  4. Add backlinks and conversions by URL, so the surviving page keeps the most value.
  5. Review each query group: impression split, ranking pattern, intent verdict and fix.
  6. Merge, redirect and update links, then watch the query group for six to twelve weeks.

Situations this skill handles

Overlap isn’t always a problem. The skill tells the difference in these situations:

SituationWhat the skill does
Three posts on the same topic from different yearsMerges into the URL with the most links and redirects the others
Category page and buying guide swap rankingsGives each a distinct intent and links between them
Two pages steady in the top threeLeaves them alone; that is a strength
Annual guides on new URLs each yearMoves to one evergreen URL updated yearly
Location pages competingMakes each clearly local or consolidates identical ones
Checking a new article before publishingSearches the site and Search Console for existing pages on the topic

What makes this skill different

Most cannibalisation checks flag any two pages sharing a keyword. This skill looks for evidence of harm in Search Console (rankings swapping between URLs, both pages stuck lower than expected, the less relevant page ranking) and confirms the intents match before recommending a merge.

When it does merge, it protects value: the surviving URL is chosen on links, traffic and conversions, the best content from both pages is kept, and redirects and internal links are part of the plan.

Practical tips from real projects

  • Intent, not words. Pages compete when they answer the same need.
  • Don’t use noindex to fix overlap; it throws away the weaker page’s signals.
  • Update internal links after every merge.
  • Keep a topic register mapping each intent to one URL.

A worked example: a travel insurance site had three posts on cover for pre-existing conditions, written in 2021, 2023 and 2025. Search Console showed all three taking impressions, with the ranking URL changing every few days between positions 9 and 15. The 2023 post had the most backlinks; the 2025 post had the newest information. The newer content moved into the 2023 URL, the other two were redirected and internal links were updated. Within eight weeks one URL ranked steadily at position four and clicks for the query group roughly doubled.

Overlap also confuses AI answers. When two of your pages say different things about the same topic, engines may cite the outdated one. Consolidating to one clear, current page helps classic rankings and AI accuracy at the same time.

Prevention is cheaper than repair: check the topic register before every brief, so new pages get a distinct job from the start.

The merge itself follows a set order: choose the surviving URL, outline the merged page keeping every section that ranks or earns links, rewrite it as one coherent page, redirect the retired URL, update links, sitemaps and canonicals, request indexing and then measure the query group. Skipping a step, especially the link updates, is the most common reason merges underperform.

Report the result as a query group, not a single keyword, because merged pages usually gain across many related searches at once.

Frequently asked questions

Two or more pages on the same site serving the same intent, so search engines switch between them or rank neither as well as one strong page would.

No. If both pages are steady near the top and serve different needs, such as a guide and a category page, that can be ideal. The skill fixes only harmful overlap.

Usually neither. If the pages serve the same intent, merge them and redirect the weaker URL so its links and signals carry over. Canonicals suit variants users still need.

Normally the one with the most backlinks, traffic and conversions and the cleaner URL. The best content from the other page is moved into it.

Often a few weeks once Google processes the redirects. The skill measures the query group for six to twelve weeks.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.