Find query and page overlap from GSC data and recommend consolidation, differentiation, or internal-link fixes. Use when Codex needs to identify and resolve keyword cannibalization issues.
Scanned 9/20/2026
Install to Claude Code
npx -y skills add unempyd/revenueos --skill cannibalization-check --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cannibalization Check?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/unempyd-cannibalization-check)More formats (shields.io, HTML) on the badges page.
---
name: cannibalization-check
description: Find query and page overlap from GSC data and recommend consolidation, differentiation, or internal-link fixes. Use when Codex needs to identify and resolve keyword cannibalization issues.
---
# Cannibalization Check
## Overview
Analyze GSC query and page data to find situations where multiple pages compete for the same or closely related queries, diluting ranking potential. Recommend consolidation, 301 redirects, or differentiation strategies.
## Inputs
- GSC query + page export or live data
- Optional: site content inventory or sitemap
## Workflow
1. Load GSC data and group queries by semantic similarity.
2. For each query group, identify pages that appear for the same query.
3. Score cannibalization severity:
- Multiple pages in top 20 for the same query
- Pages splitting clicks/impressions across similar queries
- High-authority page being cannibalized by a lower-authority page
4. For each cannibalization instance, recommend:
- Consolidation: 301 to the best page
- Differentiation: adjust targets so pages cover distinct subtopics
- Internal link fix: adjust anchor text and link structure
5. Estimate the traffic recovery from resolving each instance.
## Output
Cannibalization report with competing page pairs, query overlap, severity score, and fix recommendation.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!