blog-cannibalization

Detect keyword cannibalization across blog posts and generate severity-scored remediation recommendations.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/captaindevv/blogs --skill blog-cannibalization-captaindevv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog-cannibalization
Source: https://github.com/captaindevv/blogs/tree/main/skills/blog-cannibalization
Command: npx skills add https://github.com/captaindevv/blogs --skill blog-cannibalization-captaindevv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify when multiple blog posts compete for the same search intent and surface actionable remediation so content teams can stop internal ranking conflicts and consolidate authority.

Core Features & Use Cases

  • Local and API analysis: Runs a zero-cost grep-based scan of markdown/html content or enriches results with DataForSEO Page Intersection and Ranked Keywords when the --api flag and credentials are provided.
  • Keyword extraction and clustering: Extracts primary keywords from titles, H1/H2 headings and first paragraphs, then groups posts by exact match, stem match, semantic overlap, or subset match.
  • Severity scoring and recommendations: Produces per-cluster severity levels (Critical/High/Medium/Low) and prescriptive actions (MERGE, DIFFERENTIATE, CANONICAL, NO ACTION) with rationale.
  • Use case: Run this on a content repository to find competing posts after a site migration or before a large reoptimize to decide which pages to merge, differentiate, or canonicalize.

Quick Start

Use the blog-cannibalization skill to scan the content directory for keyword overlap and produce a severity-scored remediation report.

Frequently Asked Questions about blog-cannibalization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect keyword cannibalization across my blog posts?

You detect keyword cannibalization by extracting primary keywords from titles, H1/H2 headings, and first paragraphs, then clustering semantically similar targets to score severity. This produces actionable MERGE, DIFFERENTIATE, or CANONICAL recommendations to resolve internal ranking conflicts and consolidate authority.

What is the best way to run a content audit for keyword overlap without API costs?

Running a zero-cost grep-based scan of your local markdown or HTML content directory performs a content audit for keyword overlap without API costs. This extracts primary keywords, clusters similar targets, and generates a severity-scored remediation report offline.

Can I use DataForSEO to enrich keyword cannibalization analysis for published URLs?

DataForSEO integration enriches keyword cannibalization analysis for published URLs using Page Intersection and Ranked Keywords endpoints for SERP-aware insights. You provide API credentials with the --api flag to supplement local grep extraction with live search ranking data.

How do I decide whether to merge, differentiate, or canonicalize competing blog posts?

Decisions to merge, differentiate, or canonicalize competing blog posts are driven by per-cluster severity scoring and prescriptive rationale. The analysis evaluates Critical, High, Medium, or Low overlap levels between clustered posts to recommend the optimal remediation action.

Do I need DataForSEO API credentials to find keyword conflicts in local markdown files?

DataForSEO API credentials are not required to find keyword conflicts in local markdown files. A zero-cost grep-based scan extracts primary keywords and clusters semantically similar targets directly from your local content directory without external dependencies.