seo-cannibalization-detector
Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.
What this skill does
## 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. ## 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.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".