blog-cannibalization
Skill0 starsChanged 3 months agoMITView on GitHub
Detect keyword cannibalization across blog posts by extracting primary keywords from titles and headings, clustering semantically similar targets, and flagging posts competing for the same search intent. Supports local-only mode (grep-based) and DataForSEO API mode (Page Intersection endpoint at ~$0.01/call). Outputs severity-scored report with merge or differentiate recommendations. Use when user says "cannibalization", "keyword overlap", "competing pages", "duplicate keywords", "cannibalize".
3 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- gaznilmuzammil12-prog/seo-skills-by-gaznilword for word, first seen Nov 16, 2026
- alpit-patel/seo-aeo-geo-kitedited, first seen Nov 8, 2026
- AgriciDaniel/claude-blogedited, first seen Oct 25, 2026
Other versions3 projects use a version of this.
Word for word · 1
- gaznilmuzammil12-prog/seo-skills-by-gaznil★ 0100% same
Edited · 2
- AgriciDaniel/claude-blog★ 2.7k55% same
- alpit-patel/seo-aeo-geo-kit★ 275% same
Wrote their own version · 0
None found.
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 repository85 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- llms-full.txtllms.txt
- llms.txtllms.txt
- ab-testingSkill
- accessibilitySkill
- ai-seoSkill
- analyticsSkill
- attributionSkill
- blog-analyzeSkill
- blog-audioSkill
- blog-auditSkill
- blog-brandSkill
- blog-briefSkill
- blog-calendarSkill
- blog-chartSkill
- blog-clusterSkill
- blog-discourseSkill
- blog-factcheckSkill
- blog-flowSkill
- blog-geoSkill
- blog-googleSkill
- blog-imageSkill
- blog-locale-auditSkill
- blog-localizeSkill
- blog-multilingualSkill
- blog-notebooklmSkill
- blog-outlineSkill
- blog-personaSkill
- blog-repurposeSkill
- blog-rewriteSkill
- blog-schemaSkill
- blog-seo-checkSkill
- blogSkill
- blog-strategySkill
- blog-taxonomySkill
- blog-translateSkill
- blog-writeSkill
- canonical-tagSkill
- competitorsSkill
- content-optimizationSkill
- content-strategySkill
- copywritingSkill
- core-web-vitalsSkill
- croSkill
- directory-submissionsSkill
- eeat-signalsSkill
- entity-seoSkill
- featured-snippetSkill
- google-search-consoleSkill
- heading-structureSkill
- indexingSkill
- indexnowSkill
- internal-linksSkill
- keyword-researchSkill
- local-seoSkill
- meta-descriptionSkill
- mobile-friendlySkill
- open-graphSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 15 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Use Glob to find all content files in the target directory:
- Distinctive: line 45
Meta description: if present in frontmatter
- Distinctive: line 108
Run Ranked Keywords for each URL to build keyword profiles
- Distinctive: line 109
Run Page Intersection for URL pairs that share keyword clusters
- Distinctive: line 171
When both pages are thin or cover the same intent with similar depth.
- Distinctive: line 177
When pages serve different intents but keyword targeting overlaps.
- Distinctive: line 179
Update the title, H1, and meta description to reflect the new focus
- Distinctive: line 180
Add internal links between the two posts to signal distinct topics
- Distinctive: line 183
When one post is clearly the authority and the other is a lesser duplicate.
- Very specific: line 184
Add rel="canonical" on the weaker page pointing to the authority
- Distinctive: line 185
Consider noindexing the weaker page if it adds no unique value
- Distinctive: line 189
When intent is genuinely different despite surface-level keyword similarity.
- Distinctive: line 190
Document the reasoning for future audits
- Distinctive: line 196
No blog files found: If the directory contains no .md, .mdx, or .html files, report "No blog files found in [directory]" and suggest …
- Distinctive: line 199
WebFetch failures: If a source URL is unreachable, skip it and note "Unable to verify - source unavailable" in the report
- Distinctive: line 200
Single-post directory: If only one blog post exists, report "Cannibalization analysis requires at least 2 posts" and exit gracefully
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Blog Cannibalization - Keyword Overlap Detection
Detect when multiple blog posts compete for the same search keywords. Two modes: local-only analysis (default) and DataForSEO API mode for SERP-level data.
Two Modes
| Mode | Flag | Cost | Data Source |
| Local | (default) | Free | File content analysis via Grep/Read |
| API | --api | ~$0.01/call | DataForSEO Page Intersection + Ranked Keywords |
Local mode works without any API keys. API mode requires DataForSEO credentials
set as environment variables: DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD.
Local Mode Workflow
Step 1: Scan Blog Files
Use Glob to find all content files in the target directory:
- Patterns:
**/*.md,**/*.mdx,**/*.html - Skip files in
node_modules/,.git/,drafts/
Step 2: Extract Primary Keywords
For each file, read and extract keyword signals from:
- Title tag or H1 heading (highest weight)
- H2 headings (medium weight)
- First paragraph (supporting signal)
- Meta description if present in frontmatter
Primary keyword extraction method:
- Tokenize title and H1 into 1-gram, 2-gram, and 3-gram phrases
- Score each phrase by frequency across title + H2s + first paragraph
- Select the top-scoring 2-3 word phrase as the primary keyword
- Record secondary keywords from H2 headings
Step 3: Cluster by Similarity
Group posts into clusters using these matching rules (in priority order):
- Exact match - identical primary keyword across 2+ posts
- Stem match - same root word (e.g., "optimize" vs "optimization")
- Semantic overlap - Claude determines that two keywords target the same search intent (e.g., "best CRM software" vs "top CRM tools 2026")
- Subset match - one keyword contains another (e.g., "email marketing" vs "email marketing for startups")
Step 4: Score and Flag
For each cluster with 2+ posts, assess severity and generate a recommendation.
Step 5: Output Report
Display the results table and per-cluster recommendations.
API Mode Workflow (DataForSEO)
Requires the --api flag. Uses WebFetch to call DataForSEO endpoints.
Endpoints Used
Page Intersection - find keywords where multiple URLs rank:
POST https://api.dataforseo.com/v3/dataforseo_labs/google/page_intersection/live
Authorization: Basic <base64(login:password)>
{
"pages": {
"1": "https://example.com/post-a",
"2": "https://example.com/post-b"
},
"language_code": "en",
"location_code": 2840
}Cost: ~$0.01 per call. Returns overlapping keywords with position, volume, CPC.
Ranked Keywords - get all keywords a single URL ranks for:
POST https://api.dataforseo.com/v3/dataforseo_labs/google/ranked_keywords/live
{
"target": "https://example.com/post-a",
"language_code": "en",
"location_code": 2840
}API Analysis Steps
- Collect all published URLs from the user (or sitemap)
- Run Ranked Keywords for each URL to build keyword profiles
- Run Page Intersection for URL pairs that share keyword clusters
- Calculate severity using the formula below
- Output enriched report with search volume and position data
Severity Scoring
Four severity levels based on overlap signals:
| Level | Criteria | Action Urgency |
| Critical | Same exact keyword, both pages in top 20 | Immediate |
| High | Same keyword cluster, one page outranks the other | This week |
| Medium | Related keywords with partial SERP overlap | This month |
| Low | Semantic similarity but different confirmed intents | Monitor |
Severity Formula (API Mode)
severity_score = overlap_count x avg_search_volume x (1 / position_gap)Where:
overlap_count= number of shared ranking keywordsavg_search_volume= mean monthly volume of shared keywordsposition_gap= absolute difference in average ranking position (min 1)
Higher score = more urgent cannibalization problem.
Severity Heuristic (Local Mode)
Without SERP data, use a simplified scoring:
- Critical: Exact primary keyword match between posts
- High: Stem match on primary keyword, or 3+ shared H2 keywords
- Medium: Semantic overlap on primary keyword
- Low: Subset match only, or shared secondary keywords
Output Format
Summary Table
| Post A | Post B | Shared Keywords | Severity | Recommendation |
|--------|--------|-----------------|----------|----------------|
| /best-crm-tools | /top-crm-software | best crm, crm tools, crm software | Critical | MERGE |
| /email-tips | /email-marketing-guide | email marketing | High | DIFFERENTIATE |
| /seo-basics | /seo-for-beginners | seo basics, beginner seo | Critical | CANONICAL |
| /react-hooks | /react-state-mgmt | react, state | Low | NO ACTION |Per-Cluster Detail
For each flagged cluster, provide:
- Both post titles and URLs
- Full list of overlapping keywords (with volume if API mode)
- Which post is stronger (more comprehensive, better structured)
- Specific recommendation with rationale
Recommendations
Four possible actions for each cannibalization cluster:
MERGE
When both pages are thin or cover the same intent with similar depth.
- Combine the best content from both into one comprehensive post
- 301 redirect the weaker URL to the merged post
- Preserve all internal links pointing to either URL
DIFFERENTIATE
When pages serve different intents but keyword targeting overlaps.
- Shift the primary keyword of the weaker post to a related long-tail
- Update the title, H1, and meta description to reflect the new focus
- Add internal links between the two posts to signal distinct topics
CANONICAL
When one post is clearly the authority and the other is a lesser duplicate.
- Add
rel="canonical"on the weaker page pointing to the authority - Consider noindexing the weaker page if it adds no unique value
- Link from the weaker page to the authority page
NO ACTION
When intent is genuinely different despite surface-level keyword similarity.
- Document the reasoning for future audits
- Monitor rankings quarterly for any position changes
- Re-evaluate if either post drops in rankings
Error Handling
- No blog files found: If the directory contains no .md, .mdx, or .html files, report "No blog files found in [directory]" and suggest checking the path
- DataForSEO credentials missing: In API mode, if credentials are not configured, fall back to local mode automatically and notify the user
- API rate limits: DataForSEO has per-minute rate limits. If a 429 response is received, wait and retry once. If it persists, switch to local mode for remaining URLs
- WebFetch failures: If a source URL is unreachable, skip it and note "Unable to verify - source unavailable" in the report
- Single-post directory: If only one blog post exists, report "Cannibalization analysis requires at least 2 posts" and exit gracefully
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.

