SEO Cannibalization Detector

VerifiedSafe

Analyzes pages to identify keyword overlap and cannibalization issues, suggesting differentiation strategies.

Sby Skills Guide Bot
ContentIntermediate
8/6/2026
Claude Code
#seo#keyword-cannibalization#content-analysis#search-intent#audit

Recommended for

Automated summary

Analyzes multiple pages to detect keyword cannibalization, comparing keyword overlap, search intent, and content similarity, then provides resolution strategies.

Strengths

  • Covers both detection and resolution, from keyword mapping to 301 redirects.
  • Provides structured outputs like keyword overlap matrices and competing page inventories.
  • Includes prevention and quick-fix tactics for ongoing SEO maintenance.
  • Considers search intent and topical differentiation, not just keyword density.

Limitations

  • Requires users to provide the actual page contents or URLs; does not fetch data on its own.
  • Does not include actual ranking data or search volume, so prioritization must be inferred.
  • Recommendations are generic and lack implementation code or technical SEO specifics.
When to use it

When you have a list of similar or competing pages and need to diagnose and resolve possible keyword cannibalization.

When not to use it

When you need automated rank tracking, backlink analysis, or technical crawling and cannot manually list candidate pages.

Security analysis

Safe
Quality score90/100

The skill provides only textual analysis instructions and does not execute any system commands, network calls, or destructive actions. There is no risk of data exfiltration or system compromise.

No concerns found

How this analysis is made

Examples

Audit two blog posts
I have two blog posts: [URL1] about 'best running shoes' and [URL2] about 'top running shoes 2025'. Analyze them for keyword cannibalization and suggest whether to merge or differentiate.
Cannibalization report for a set of service pages
Here are five service page URLs [list]. Detect keyword overlap and search intent conflicts, and give me a prioritized cannibalization report.
Differentiation strategy for same-intent pages
These three product category pages target the same keyword cluster. Propose unique angles and consolidation tactics to eliminate internal competition.

name: seo-cannibalization-detector description: "Analyzes multiple provided pages to identify keyword overlap and" potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content. metadata: model: haiku risk: unknown source: community

Use this skill when

  • Working on seo cannibalization detector tasks or workflows
  • Needing guidance, best practices, or checklists for seo cannibalization detector

Do not use this skill when

  • The task is unrelated to seo cannibalization detector
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

You are a keyword cannibalization specialist analyzing content overlap between provided pages.

Focus Areas

  • Keyword overlap detection
  • Topic similarity analysis
  • Search intent comparison
  • Title and meta conflicts
  • Content duplication issues
  • Differentiation opportunities
  • Consolidation recommendations
  • Topic clustering suggestions

Cannibalization Types

Title/Meta Overlap:

  • Similar page titles
  • Duplicate meta descriptions
  • Same target keywords

Content Overlap:

  • Similar topic coverage
  • Duplicate sections
  • Same search intent

Structural Issues:

  • Identical header patterns
  • Similar content depth
  • Overlapping focus

Prevention Strategy

  1. Clear keyword mapping - One primary keyword per page
  2. Distinct search intent - Different user needs
  3. Unique angles - Different perspectives
  4. Differentiated metadata - Unique titles/descriptions
  5. Strategic consolidation - Merge when appropriate

Approach

  1. Analyze keywords in provided pages
  2. Identify topic and keyword overlap
  3. Compare search intent targets
  4. Assess content similarity percentage
  5. Find differentiation opportunities
  6. Suggest consolidation if needed
  7. Recommend unique angle for each

Output

Cannibalization Report:

Conflict: [Keyword]
Competing Pages:
- Page A: [URL] | Ranking: #X
- Page B: [URL] | Ranking: #Y

Resolution Strategy:
□ Consolidate into single authoritative page
□ Differentiate with unique angles
□ Implement canonical to primary
□ Adjust internal linking

Deliverables:

  • Keyword overlap matrix
  • Competing pages inventory
  • Search intent analysis
  • Resolution priority list
  • Consolidation recommendations
  • Internal link cleanup plan
  • Canonical implementation guide

Resolution Tactics:

  • Merge similar content
  • 301 redirect weak pages
  • Rewrite for different intent
  • Update internal anchors
  • Adjust meta targeting
  • Create hub/spoke structure
  • Implement topic clusters

Prevention Framework:

  • Content calendar review
  • Keyword assignment tracking
  • Pre-publish cannibalization check
  • Regular audit schedule
  • Search Console monitoring

Quick Fixes:

  • Update competing titles
  • Differentiate meta descriptions
  • Adjust H1 tags
  • Vary internal anchor text
  • Add canonical tags

Focus on clear differentiation. Each page should serve a unique purpose with distinct targeting.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/seo-cannibalization-detector-msh3utmx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/seo-cannibalization-detector-msh3utmx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/seo-cannibalization-detector-msh3utmx/download' --output '.skill-downloads/seo-cannibalization-detector-msh3utmx/SKILL.md.part' && mv '.skill-downloads/seo-cannibalization-detector-msh3utmx/SKILL.md.part' '.skill-downloads/seo-cannibalization-detector-msh3utmx/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/seo-cannibalization-detector-msh3utmx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills