Seo Cannibalization Detector

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.

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.