build-clusters
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseBuild 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
主题集群是一组相互链接的页面集合,共同覆盖某一主题领域。Google会在集群层面评估主题权威度——如果站点在该主题下没有支撑内容,单个页面的排名难度会高很多。
结构:
- 支柱页(Pillar page):对宽泛主题的全面概述(定位头部关键词)
- 辐条页(Spoke pages):聚焦子主题的专项文章(定位中端/长尾关键词)
- 内部链接:所有辐条页都链向支柱页,支柱页链向所有辐条页,辐条页之间也互相交叉链接
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
步骤1:子主题挖掘
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.
从种子主题出发,通过以下方法生成子主题:
搜索来源:
- 种子关键词对应的People Also Ask问题
- SERP底部的相关搜索
- 自动补全建议(种子 + a、b、c…)
- 竞品内容分析:排名靠前的站点都覆盖了哪些子主题?
意图来源:
- 认知阶段:"什么是[主题]"、"为什么[主题]很重要"
- 考量阶段:"最好的[主题]工具"、"[主题] vs [替代方案]"
- 落地阶段:"如何使用[主题]"、"[主题]教程"
- 故障排查:"[主题]无法运行"、"[主题]常见错误"
受众来源:
- 受众关于该主题的入门级问题
- 高级从业者的关切点
- 决策者的评估标准
每个集群建议设置8-20个子主题。
Step 2: Cluster Map
步骤2:集群地图
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)将子主题整理为结构化的集群:
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
步骤3:覆盖度评分
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
评估现有站点对集群的覆盖程度:
| 子主题 | 是否有现有页面? | 质量(1-5分) | 流量 | 是否存在缺口? |
|---|---|---|---|---|
| [子主题 1] | /blog/topic-1 | 4 | 500/月 | 否 |
| [子主题 2] | — | — | — | 是 |
| [子主题 3] | /blog/old-post | 2 | 50/月 | 部分缺口(需要更新) |
- 完全缺口:无现有页面,需要新建
- 部分缺口:页面存在,但内容单薄、过时或不符合用户意图
- 已覆盖:现有页面质量较高,可能仅需补充内部链接
Step 4: Pillar Page Design
步骤4:支柱页设计
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.
支柱页应当满足以下要求:
- 在概述层面全面覆盖主题(字数2000-4000字)
- 链向所有辐条页,供用户深入阅读
- 作为整个集群的目录结构存在
- 定位集群中搜索量最高的关键词
- 包含每个子主题的摘要(2-3段),并链向完整的辐条页
支柱页不是试图深度覆盖所有内容的超级文章,它是分发权威度、引导用户访问对应辐条页的枢纽。
Step 5: Interlinking Plan
步骤5:内链规划
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)
规划内部链接映射:
| 来源页面 | 目标页面 | 锚文本 | 上下文位置 |
|---|---|---|---|
| 支柱页 | 辐条页1 | "[子主题1]指南" | 在子主题1的概述部分 |
| 辐条页1 | 支柱页 | "[宽泛主题]" | 在引言或结论部分 |
| 辐条页1 | 辐条页2 | "[子主题2]" | 上下文提到子主题2的位置 |
| 辐条页3 | 辐条页1 | "[子主题1]" | 适合做对比的位置 |
规则:
- 所有辐条页必须链向支柱页(强制要求)
- 支柱页必须链向所有辐条页(强制要求)
- 辐条页可向2-4个同级辐条页添加交叉链接(上下文自然的前提下)
- 使用多样化的锚文本(不要一直使用完全匹配的关键词)
Step 6: Cluster Health Metrics
步骤6:集群健康度指标
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 |
评估集群的排名竞争力:
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| 指标 | 得分 | 阈值 |
|---|---|---|
| 覆盖度 | [x]% | 超过70%可开始冲击支柱页关键词排名 |
| 链接健康度 | [x]% | 目标为100%——所有辐条页都必须和支柱页互链 |
| 内容质量 | [x]% | 超过80%——辐条页内容单薄会稀释集群权威度 |
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 |
| 集群状态 | 覆盖度 | 链接健康度 | 内容质量 | 预期结果 |
|---|---|---|---|---|
| 未完成 | <50% | <70% | 任意 | 支柱页几乎不可能排在首页;最多仅辐条页可单独获得排名 |
| 发展中 | 50-70% | 70-90% | 50-80% | 支柱页可能出现在第2-3页;部分辐条页可获得长尾词排名 |
| 有竞争力 | 70-90% | 100% | 80-90% | 支柱页可冲击首页排名;多数辐条页可获得对应目标关键词排名 |
| 主导级 | >90% | 100% | >90% | 支柱页稳居首页前列;集群可捕获该主题下绝大多数搜索请求 |
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.
| 链接类型 | 最低数量 | 方向 |
|---|---|---|
| 支柱页 → 每个辐条页 | 每个辐条页1条 | 向下——从支柱页对应子主题的部分链出 |
| 每个辐条页 → 支柱页 | 每个辐条页1条 | 向上——锚文本类似"我们的完整[主题]指南" |
| 辐条页 ↔ 同级辐条页 | 每个辐条页2-4条 | 横向——上下文自然的前提下 |
| 跨集群桥接链接 | 每个集群0-2条 | 枢纽间——仅当存在真实主题相关性时添加 |
具备排名竞争力的集群标准: 覆盖度>70%、链接健康度=100%、内容质量>80%。低于这些阈值时,请优先填补缺口,再期待支柱页获得排名。
Step 7: Production Sequence
步骤7:产出顺序
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 — runto see existing clusters with coverage metrics, or use/seojuice:content-strategyandlist_clustersto check cluster health and identify gaps.get_cluster_detail
集群摘要
- 支柱关键词:[关键词](搜索量:[x],难度:[y])
- 总辐条页数量:[数量]
- 现有覆盖度:[x]%(已有[n]个页面,需要新建[n]个页面)
- 集群总搜索量:[所有关键词搜索量之和]
集群地图
[步骤2中的可视化结构]
覆盖度评分卡
[步骤3中的表格]
支柱页规范
- 目标关键词:[关键词]
- 建议标题:[标题]
- 结构:[带辐条页链接的标题大纲]
内链规划
[步骤5中的表格]
生产路线图
[步骤6中的排序列表,附预估时间线]
专业提示: 使用免费的博客关键词生成器挖掘集群的子主题。SEOJuice MCP用户可自动生成集群映射——运行即可查看带有覆盖度指标的现有集群,也可使用/seojuice:content-strategy和list_clusters检查集群健康度、识别内容缺口。get_cluster_detail