cannibalization-check
Skill7 starsChanged 5 months agoMITView on GitHub
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.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- FlorianBruniaux/google-search-console-mcptheir own version, first seen Oct 15, 2026
- UXMagicai/seosorted-skillstheir own version, first seen Oct 4, 2026
- AminForou/mcp-gsctheir own version, first seen Apr 10, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- AminForou/mcp-gsc★ 2.1ksame name
- FlorianBruniaux/google-search-console-mcp★ 22same name
- UXMagicai/seosorted-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- authority-mark-keyword-difficultySkill
- client-report-writerSkill
- competitor-serp-monitorSkill
- content-decay-monitor-setupSkill
- content-moat-plannerSkill
- content-refresh-briefSkill
- exceed-quality-thresholdSkill
- internal-link-builderSkill
- keyword-opportunity-finderSkill
- keyword-plannerSkill
- live-search-console-dataSkill
- proposal-builderSkill
- refresh-vs-new-contentSkill
- schema-fix-writerSkill
- seo-content-briefSkill
- seo-growth-loopSkill
- seo-offer-architectSkill
- seo-priority-scoreSkill
- seo-strategySkill
- technical-seo-triageSkill
- title-meta-rewriterSkill
- traffic-decay-detectorSkill
The file
Files
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
- Load GSC data and group queries by semantic similarity.
- For each query group, identify pages that appear for the same query.
- 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
- 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
- Estimate the traffic recovery from resolving each instance.
Output
Cannibalization report with competing page pairs, query overlap, severity score, and fix recommendation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.