构建内容集群指南：使用支柱-辐条模型提升网站主题权威与SEO排名

build-clusters by calm-north/seojuice-skills

1,100 周安装量

3 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/calm-north/seojuice-skills --skill build-clusters

数据分析营销 SEO

🇨🇳中文介绍

构建内容集群

使用支柱-辐条结构、覆盖率评分和内部链接规划，从种子关键词构建主题权威集群。

什么是主题集群？

主题集群是一组相互链接的页面，共同覆盖一个主题领域。Google 在集群层面评估主题权威性——如果网站没有围绕该主题的支持性内容，单个页面就更难获得排名。

结构：

支柱页面 — 对广泛主题的全面概述（针对核心词）
辐条页面 — 专注于子主题的文章（针对主体词/长尾词）
内部链接 — 每个辐条页面都链接到支柱页面，支柱页面链接到所有辐条页面，辐条页面之间相互交叉链接

开始之前

收集以下背景信息（如果未提供，请询问）：

种子主题。 要围绕其建立权威的广泛主题领域。
现有内容。 网站是否已有关于此主题的页面？请列出它们。
业务相关性。 此主题如何与产品或服务相关联？
内容产能。 团队每月可以产出多少篇文章？

步骤 1：子主题发现

从种子主题出发，使用以下方法生成子主题：

搜索衍生：

种子关键词的"用户还问了"问题
搜索结果页面底部的相关搜索
自动补全建议（种子 + a, b, c...）
竞争对手内容分析 — 排名靠前的网站覆盖了哪些子主题？

意图衍生：

认知阶段："什么是 [主题]"，"为什么 [主题] 很重要"
考虑阶段："最佳 [主题] 工具"，"[主题] 与 [替代方案] 对比"
实施阶段："如何 [主题]"，"[主题] 教程"
故障排除："[主题] 不工作"，"常见 [主题] 错误"

受众衍生：

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

步骤 2：集群地图

将子主题组织成一个结构化的集群：

Pillar: [Broad Topic] (head term)
│
├── Spoke: [Subtopic 1] (body term)
│   └── Intent: informational
│
├── Spoke: [Subtopic 2] (body term)
│   └── Intent: commercial investigation
│
├── Spoke: [Subtopic 3] (long-tail)
│   └── Intent: transactional
│
├── Spoke: [Subtopic 4] (long-tail)
│   └── Intent: informational
│
└── ... (8-15 more spokes)

步骤 3：覆盖率评分

评估现有网站在集群覆盖方面的表现：

子主题	现有页面？	质量 (1-5)	流量	差距？
[subtopic 1]	/blog/topic-1	4	500/mo	No
[subtopic 2]	—	—	—	Yes
[subtopic 3]	/blog/old-post	2	50/mo	Partial (needs refresh)

完全空白 — 没有现有页面，需要创建
部分空白 — 页面存在但内容单薄、过时或意图不符
已覆盖 — 现有页面质量高，可能只需要添加内部链接

步骤 4：支柱页面设计

在概述层面全面覆盖主题（2,000-4,000 字）
链接到每个辐条页面以进行深入探讨
构建为整个集群的目录
针对集群中搜索量最高的关键词
包含每个子主题的摘要（2-3 段）并链接到完整的辐条页面

支柱页面不是试图深入涵盖所有内容的巨型文章。它是一个中心枢纽，用于分发权威性并将读者引导至正确的辐条页面。

步骤 5：内部链接规划

规划内部链接：

来源页面	目标页面	锚文本	上下文
Pillar	Spoke 1	"[subtopic 1] guide"	在子主题 1 概述部分
Spoke 1	Pillar	"[broad topic]"	在引言或结论部分
Spoke 1	Spoke 2	"[subtopic 2]"	在上下文提及子主题 2 的地方
Spoke 3	Spoke 1	"[subtopic 1]"	在相关比较出现的地方

每个辐条页面都链接到支柱页面（强制）
支柱页面链接到每个辐条页面（强制）
辐条页面交叉链接到 2-4 个同级页面（在上下文自然的情况下）
使用多样化的锚文本（不总是完全匹配关键词）

步骤 6：集群健康度指标

评估集群参与竞争的成熟度：

Coverage Score  = (Covered spokes / Total spokes) x 100
Link Health     = (Spokes with bidirectional pillar link / Total spokes) x 100
Content Quality = (Spokes scoring 3+ quality / Total spokes) x 100

指标	得分	阈值
Coverage	[x]%	> 70% 以开始竞争支柱关键词排名
Link Health	[x]%	100% 是目标 — 每个辐条页面必须链接到支柱页面并返回
Content Quality	[x]%	> 80% — 包含薄弱辐条页面的集群会稀释权威性

按健康度等级的预期结果

集群状态	覆盖率	链接健康度	内容质量	预期结果
Incomplete	<50%	<70%	Any	支柱页面不太可能进入第 1 页；辐条页面最多只能单独排名
Developing	50-70%	70-90%	50-80%	支柱页面可能出现在第 2-3 页；部分辐条页面在长尾词上排名
Competitive	70-90%	100%	80-90%	支柱页面竞争第 1 页；大多数辐条页面在其目标词上排名
Dominant	>90%	100%	>90%	支柱页面在第 1 页表现强劲；集群捕获该主题下的大部分查询

每个集群的内部链接标准

链接类型	最小数量	方向
Pillar → each spoke	1 per spoke	向下 — 从支柱页面的相关部分链接
Each spoke → pillar	1 per spoke	向上 — "我们的完整 [主题] 指南"
Spoke ↔ sibling spokes	2-4 per spoke	横向 — 在上下文自然的地方
Cross-cluster bridges	0-2 per cluster	集群间 — 仅在具有真正的主题相关性时

集群准备就绪参与竞争： 覆盖率 > 70%，链接健康度 = 100%，内容质量 > 80%。低于这些阈值时，在期望支柱页面获得排名之前，应优先填补空白。

步骤 7：生产顺序

为获得最大影响，按以下顺序安排内容生产：

先创建支柱页面 — 即使是草稿，也能建立中心枢纽
其次是机会最高的辐条页面 — 针对空白且机会评分最佳的页面
更新现有辐条页面 — 更新并重新链接任何部分空白的页面
剩余辐条页面 — 随时间推移完善集群
更新支柱页面 — 随着每个新辐条页面的发布，添加链接

主题集群：[seed topic]

支柱关键词：[keyword] (volume: [x], difficulty: [y])
辐条总数：[count]
现有覆盖率：[x]% ([n] 个页面存在，[n] 个需要创建)
集群总搜索量：[sum of all keyword volumes]

集群地图 [来自步骤 2 的可视化结构]

覆盖率评分卡 [来自步骤 3 的表格]

支柱页面规格

目标关键词：[keyword]
推荐标题：[title]
结构：[包含辐条链接的标题大纲]

内部链接规划 [来自步骤 5 的表格]

生产路线图 [来自步骤 6 的有序列表，包含预计时间线]

专业提示： 使用免费的 Blog Keyword Generator 来发现集群的子主题。SEOKuice MCP 用户可获得自动集群映射 — 运行 /seojuice:content-strategy 查看带有覆盖率指标的现有集群，或使用 list_clusters 和 get_cluster_detail 来检查集群健康度并识别空白。

🇺🇸English

Build Clusters

Build a topical authority cluster from a seed keyword using pillar-spoke structure, coverage scoring, and interlinking plans.

What is a Topic Cluster?

A topic cluster is a group of interlinked pages that collectively cover a subject area. Google evaluates topical authority at the cluster level — ranking a single page is harder if the site has no supporting content around the topic.

Structure:

Pillar page — comprehensive overview of the broad topic (targets head term)
Spoke pages — focused articles covering subtopics (target body/long-tail terms)
Internal links — every spoke links to the pillar, pillar links to all spokes, spokes cross-link to siblings

Before You Start

Gather this context (ask if not provided):

Seed topic. The broad subject area to build authority around.
Existing content. Does the site already have pages on this topic? List them.
Business relevance. How does this topic connect to the product or service?
Content capacity. How many pieces can the team produce per month?

Step 1: Subtopic Discovery

From the seed topic, generate subtopics using these methods:

Search-derived:

People Also Ask questions for the seed keyword
Related searches at the bottom of SERPs
Autocomplete suggestions (seed + a, b, c...)
Competitor content analysis — what subtopics do top-ranking sites cover?

Intent-derived:

Awareness: "what is [topic]", "why [topic] matters"
Consideration: "best [topic] tools", "[topic] vs [alternative]"
Implementation: "how to [topic]", "[topic] tutorial"
Troubleshooting: "[topic] not working", "common [topic] mistakes"

Audience-derived:

Beginner questions about the topic
Advanced practitioner concerns
Decision-maker evaluation criteria

Aim for 8-20 subtopics per cluster.

Step 2: Cluster Map

Organize subtopics into a structured cluster:

Pillar: [Broad Topic] (head term)
│
├── Spoke: [Subtopic 1] (body term)
│   └── Intent: informational
│
├── Spoke: [Subtopic 2] (body term)
│   └── Intent: commercial investigation
│
├── Spoke: [Subtopic 3] (long-tail)
│   └── Intent: transactional
│
├── Spoke: [Subtopic 4] (long-tail)
│   └── Intent: informational
│
└── ... (8-15 more spokes)

Step 3: Coverage Scoring

Score how well the existing site covers the cluster:

Subtopic	Existing Page?	Quality (1-5)	Traffic	Gap?
[subtopic 1]	/blog/topic-1	4	500/mo	No
[subtopic 2]	—	—	—	Yes
[subtopic 3]	/blog/old-post	2	50/mo	Partial (needs refresh)

Full gap — no existing page, needs creation
Partial gap — page exists but is thin, outdated, or off-intent
Covered — strong existing page, may just need internal linking

Step 4: Pillar Page Design

The pillar page should:

Cover the topic comprehensively at an overview level (2,000-4,000 words)
Link to every spoke page for deeper dives
Be structured as a table of contents for the entire cluster
Target the highest-volume keyword in the cluster
Include a summary of each subtopic (2-3 paragraphs) with a link to the full spoke

Pillar page is NOT a mega-article that tries to cover everything in depth. It is a hub that distributes authority and directs readers to the right spoke.

Step 5: Interlinking Plan

Map the internal links:

From Page	To Page	Anchor Text	Context
Pillar	Spoke 1	"[subtopic 1] guide"	In the subtopic 1 overview section
Spoke 1	Pillar	"[broad topic]"	In the introduction or conclusion
Spoke 1	Spoke 2	"[subtopic 2]"	Where subtopic 2 is mentioned contextually
Spoke 3	Spoke 1	"[subtopic 1]"	Where comparison is relevant

Rules:

Every spoke links to the pillar (mandatory)
Pillar links to every spoke (mandatory)
Spokes cross-link to 2-4 siblings (where contextually natural)
Use varied anchor text (not always the exact keyword)

Step 6: Cluster Health Metrics

Score the cluster's readiness to compete:

Coverage Score  = (Covered spokes / Total spokes) x 100
Link Health     = (Spokes with bidirectional pillar link / Total spokes) x 100
Content Quality = (Spokes scoring 3+ quality / Total spokes) x 100

Metric	Score	Threshold
Coverage	[x]%	> 70% to start ranking for pillar keyword
Link Health	[x]%	100% is the target — every spoke must link to pillar and back
Content Quality	[x]%	> 80% — clusters with thin spokes dilute authority

Expected Outcomes by Health Level

Cluster State	Coverage	Link Health	Content Quality	Expected Result
Incomplete	<50%	<70%	Any	Pillar unlikely to rank page 1; spokes rank individually at best
Developing	50-70%	70-90%	50-80%	Pillar may appear page 2-3; some spokes rank for long-tail
Competitive	70-90%	100%	80-90%	Pillar competes for page 1; most spokes rank for their targets
Dominant	>90%	100%	>90%	Pillar strong on page 1; cluster captures most queries in the topic

Internal Link Standards per Cluster

Link Type	Minimum Count	Direction
Pillar → each spoke	1 per spoke	Downward — link from the relevant section of the pillar
Each spoke → pillar	1 per spoke	Upward — "our complete [topic] guide"
Spoke ↔ sibling spokes	2-4 per spoke	Lateral — where contextually natural
Cross-cluster bridges	0-2 per cluster	Between hubs — only with genuine topical relevance

Cluster ready to compete: Coverage > 70%, Link Health = 100%, Content Quality > 80%. Below these thresholds, prioritize filling gaps before expecting the pillar to rank.

Step 7: Production Sequence

Order the content production for maximum impact:

Pillar page first — even as a draft, it establishes the hub
Highest-opportunity spokes next — pages targeting gaps with the best opportunity scores
Refresh existing spokes — update and relink any partial-gap pages
Remaining spokes — fill out the cluster over time
Update pillar — add links to each new spoke as it's published

Output Format

Topic Cluster: [seed topic]

Cluster Summary

Pillar keyword: [keyword] (volume: [x], difficulty: [y])
Total spokes: [count]
Existing coverage: [x]% ([n] pages exist, [n] need creation)
Total cluster volume: [sum of all keyword volumes]

Cluster Map [Visual structure from Step 2]

Coverage Scorecard [Table from Step 3]

Pillar Page Spec

Target keyword: [keyword]
Recommended title: [title]
Structure: [heading outline with spoke links]

Interlinking Plan [Table from Step 5]

Production Roadmap [Ordered list from Step 6 with estimated timelines]

Pro Tip: Use the free Blog Keyword Generator to discover subtopics for your cluster. SEOJuice MCP users get automatic cluster mapping — run /seojuice:content-strategy to see existing clusters with coverage metrics, or use list_clusters and get_cluster_detail to check cluster health and identify gaps.

Weekly Installs

1.0K

Repository

calm-north/seoj…e-skills

GitHub Stars

First Seen

11 days ago

Security Audits

Gen Agent Trust HubPass SocketPass SnykWarn

Installed on

claude-code155

codex125

antigravity117

opencode55

gemini-cli53

cline52