seo-cannibalization-detector
Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.
Best use case
seo-cannibalization-detector is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.
Teams using seo-cannibalization-detector should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/seo-cannibalization-detector/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How seo-cannibalization-detector Compares
| Feature / Agent | seo-cannibalization-detector | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## 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.
Related Skills
azure-ai-anomalydetector-java
Build anomaly detection applications with Azure AI Anomaly Detector SDK for Java. Use when implementing univariate/multivariate anomaly detection, time-series analysis, or AI-powered monitoring.
antipattern-detector
Detect common technical and organizational anti-patterns in proposals, architectures, and plans. Use when strategic-cto-mentor needs to identify red flags before they become problems.
agent-detector
CRITICAL: MUST run for EVERY message. Detects agent, complexity, AND model automatically. Always runs FIRST.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
backend-patterns
Backend patterns for ORPC routers, Drizzle schemas, and server-side code. Use when creating API endpoints, database tables, or services.
backend-passport-js
Authentication middleware for Express.js and Node.js applications. Use when building Express APIs that need JWT authentication, OAuth, or custom auth strategies. Provides 500+ authentication strategies. Choose Passport.js over Auth.js for Express backends, pure API servers, or when you need maximum control over auth flow.
backend-nodejs
Node.js/TypeScript backend expert. Handles Express/Fastify API routes, TypeScript strict mode, Prisma ORM, Zod validation, error handling, configuration management. Use when project is Node.js backend (package.json + TypeScript server).
Backend Node.js Expert
专注于 Node.js 后端开发模式与最佳实践。
Backend Migrations
Create and manage database schema migrations with reversible operations, zero-downtime deployments, and safe rollback strategies. Use this skill when writing database migrations for PostgreSQL, MySQL, SQLite, MongoDB, or any database system; when using ORMs like Prisma, Sequelize, TypeORM, ActiveRecord, Django ORM, or similar migration tools; when implementing schema changes (adding tables, columns, indexes, constraints); when performing data migrations or transformations; when creating indexes on large tables with concurrent options to avoid locks; when separating schema changes from data migrations for safer rollbacks; when implementing zero-downtime deployment strategies for high-availability systems; when versioning database schemas and managing migration order; or when working with database change management in production environments.
backend
Skill para diseñar y construir backends y APIs **modulares**, **auditables**, **resilientes** y **multi-tenant**, con seguridad fuerte, modelado correcto (incl. ledger cuando aplique), datos y jobs/colas operables.
backend-guidelines
Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.
backend-guide
Complete backend development guide covering Node.js, Python, Go, Java, PHP, databases, APIs, authentication, and server architecture. Use when building server applications, APIs, or backend systems.