seo-cannibalization-detector

SKILL.md

---
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.
risk: safe
source: community
date_added: '2026-02-27'
---

## 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.
- Use the examples below; no separate implementation playbook is bundled.

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. Describe observed similarity and its method; do not invent a measured 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.

## Evidence and change boundaries

Topic or keyword overlap is a candidate for investigation, not proof of harmful cannibalization. Require supplied Search Console/analytics evidence, query intent and relevant observation windows before claiming ranking loss. Preserve pages that serve different intents. Canonical tags are hints for duplicate or substantially similar content, not a generic fix for every shared keyword. Propose the exact consolidation/redirect target, preserve useful content and existing links, and verify backups/rollback before an authorized site change. No publishing or redirect mutation is performed by this audit alone.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.