跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

seo-cluster

SERP-based semantic topic clustering for content architecture planning. Groups keywords by actual Google SERP overlap (not text similarity), designs hub-and-spoke content clusters with internal link matrices, and generates interactive visualizations. Optionally executes content creation if claude-blog is installed. Use when user says "topic cluster", "content cluster", "semantic clustering", "pillar page", "hub and spoke", "content architecture", "keyword grouping", or "cluster plan".

AgriciDaniel · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add AgriciDaniel/claude-seo --skill seo-cluster

技能说明


name: seo-cluster description: > SERP-based semantic topic clustering for content architecture planning. Groups keywords by actual Google SERP overlap (not text similarity), designs hub-and-spoke content clusters with internal link matrices, and generates interactive visualizations. Optionally executes content creation if claude-blog is installed. Use when user says "topic cluster", "content cluster", "semantic clustering", "pillar page", "hub and spoke", "content architecture", "keyword grouping", or "cluster plan". user-invocable: true argument-hint: "" license: MIT metadata: author: AgriciDaniel original_author: "Lutfiya Miller (Pro Hub Challenge Winner)" version: "2.2.5" category: seo

Semantic Topic Clustering

SERP-overlap-driven keyword clustering for content architecture. Groups keywords by how Google actually ranks them (shared top-10 results), not by text similarity. Designs hub-and-spoke content clusters with internal link matrices and generates interactive cluster map visualizations.

Scripts: Located at the plugin root scripts/ directory.


Quick Reference

CommandWhat it does
/seo cluster plan <seed-keyword>Full planning workflow: expand, cluster, architect, visualize
/seo cluster plan --from strategyImport from existing /seo plan output
/seo cluster executeExecute plan: create content via claude-blog or output briefs
/seo cluster mapRegenerate the interactive cluster visualization

Planning Workflow

Step 1: Seed Keyword Expansion

Expand the seed keyword into 30-50 variants using WebSearch:

  1. Related searches: Search the seed, extract "related searches" and "people also search for"
  2. People Also Ask (PAA): Extract all PAA questions from SERP results
  3. Long-tail modifiers: Append common modifiers: "best", "how to", "vs", "for beginners", "tools", "examples", "guide", "template", "mistakes", "checklist"
  4. Question mining: Generate who/what/when/where/why/how variants
  5. Intent modifiers: Add commercial modifiers: "pricing", "review", "alternative", "comparison", "free", "top"

Deduplication: Normalize variants (lowercase, strip articles), remove exact duplicates. Target: 30-50 unique keyword variants. If under 30, run a second expansion pass with the top PAA questions as seeds.

Step 2: SERP Overlap Clustering

This is the core differentiator. Load references/serp-overlap-methodology.md for the full algorithm.

Process:

  1. Group keywords by initial intent guess (reduces pairwise comparisons)
  2. For each candidate pair within a group, WebSearch both keywords
  3. Count shared URLs in the top 10 organic results (ignore ads, featured snippets, PAA)
  4. Apply thresholds:
Shared ResultsRelationshipAction
7-10Same postMerge into single target page
4-6Same clusterGroup under same spoke cluster
2-3InterlinkPlace in adjacent clusters, add cross-links
0-1SeparateAssign to different clusters or exclude

Optimization: With 40 keywords, full pairwise = 780 comparisons. Instead:

  • Pre-group by intent (4 groups of ~10 = 4 x 45 = 180 comparisons)
  • Only cross-check group boundary keywords
  • Skip pairs where both are long-tail variants of the same head term (assume same cluster)

DataForSEO integration: If DataForSEO MCP is available, use serp_organic_live_advanced instead of WebSearch for SERP data. Run claude-seo run dataforseo_costs.py check serp_organic_live_advanced --count N before each batch. If "status": "needs_approval", show cost estimate and ask user. If "status": "blocked", fall back to WebSearch.

Step 3: Intent Classification

Classify each keyword into one of four intent categories:

IntentSignalsInclude in Clusters?
Informationalhow, what, why, guide, tutorial, learnYes
Commercialbest, top, review, comparison, vs, alternativeYes
Transactionalbuy, price, discount, coupon, order, sign upYes
Navigationalbrand names, specific product names, loginNo (exclude)

Remove navigational keywords from clustering. Flag borderline cases for manual review. Keywords can have mixed intent (e.g., "best CRM software" is both commercial and informational) -- classify by dominant intent.

Step 4: Hub-and-Spoke Architecture

Load references/hub-spoke-architecture.md for full specifications.

Design the cluster structure:

  1. Select the pillar keyword: Highest volume, broadest intent, most SERP overlap with other keywords
  2. Group spokes into clusters: Each cluster is a subtopic area (2-5 clusters per pillar)
  3. Assign posts to clusters: Each cluster gets 2-4 spoke posts
  4. Select templates per post: Based on intent classification:
Intent PatternTemplate Options
Informational (broad)ultimate-guide
Informational (how)how-to
Informational (list)listicle
Informational (concept)explainer
Commercial (compare)comparison
Commercial (evaluate)review
Commercial (rank)best-of
Transactionallanding-page
  1. Set word count targets:

    • Pillar page: 2500-4000 words
    • Spoke posts: 1200-1800 words
  2. Cannibalization check: No two posts share the same primary keyword. If SERP overlap is 7+, merge those keywords into a single post targeting both.

Step 5: Internal Link Matrix

Design the bidirectional linking structure:

Link TypeDirectionRequirement
Spoke to pillarspoke -> pillarMandatory (every spoke)
Pillar to spokepillar -> spokeMandatory (every spoke)
Spoke to spoke (within cluster)spoke <-> spoke2-3 links per post
Cross-clusterspoke -> spoke (other cluster)0-1 links per post

Rules:

  • Every p
阅读完整来源 ↗