关于 seo-aeo-content-cluster
seo-aeo-content-cluster 是用于规划主题支柱页及配套文章的技能,面向内容策略人员。它围绕不同搜索意图安排选题,并规划优先级、内链和编辑日历。
主要功能
- 01规划支柱页与主题集群
- 02分配关键词和搜索意图
- 03分析内容缺口与优先级
- 04绘制内链图
- 05标记 AEO 机会文章
- 06规划编辑日历
适用场景
- 01为产品规划主题集群
- 02为细分领域寻找配套文章
- 03避免与现有内容重复
- 04组织 SEO/AEO 编辑计划
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill seo-aeo-content-cluster安装后在 Claude Code 中输入/seo-aeo-content-cluster确认已加载。
详细介绍
内容集群技能
描述
当用户想要围绕某个主题建立主题权威性,通过规划支柱页面及其配套集群文章来实现时,启用此技能。 触发短语包括:“构建内容集群”“创建主题地图”“内容支柱策略”“关于[主题]我应该写什么”“集群:[主题]”“为[细分领域]生成内容策略”。
输入格式
{
"pillar_topic": "string — the main subject to build authority around",
"primary_keyword": "string — the keyword the pillar page targets",
"target_audience": "string — who this content is for",
"existing_content": ["string — titles of pages/posts already published"],
"target_keywords": ["string — additional keywords to work into the cluster"],
"cluster_size": "integer — foundational pages to generate, 5–10, default 10",
"search_intent_evidence": "string — optional browser/API research",
"conversion_goal": "string — what the content should move readers to do"
}
对于新网站,创建 5–10 个基础页面;只有在至少存在 10 种明确且站得住脚的搜索意图时,才默认创建 10 个。不要为了达到默认数量而创建近似重复的页面。每个页面都必须解决一个问题、覆盖一个查询,并引导用户前往相关产品或下一步。
输出结构
此技能必须始终按照以下确切格式输出:
## Pillar Page
| Field | Value |
|--------------------|--------------------------------------------|
| Title | [Pillar page title with primary keyword] |
| Primary Keyword | [keyword] |
| Search Intent | informational / transactional / commercial |
| Target Audience | [audience] |
| Page Type | Pillar — comprehensive, high-level guide |
| Word Count Target | As much as needed to satisfy intent |
| AEO Priority | High — this page anchors the whole cluster |
---
## Cluster Articles
### Priority 1 — Write These First
These articles build the foundation. State measured volume with source/date or label demand unknown.
| # | Title | Target Keyword | Intent | Content Type | Links To |
|---|------------------------------|----------------------|-----------------|------------------|------------------|
| 1 | [Article title] | [keyword] | informational | how-to guide | Pillar Page |
| 2 | [Article title] | [keyword] | informational | explainer | Pillar Page |
| 3 | [Article title] | [keyword] | commercial | comparison | Pillar Page |
---
### Priority 2 — Write These Second
These deepen authority. Medium volume, long-tail focus.
| # | Title | Target Keyword | Intent | Content Type | Links To |
|---|------------------------------|----------------------|-----------------|------------------|------------------|
| 4 | [Article title] | [keyword] | informational | listicle | Art. 1, Pillar |
| 5 | [Article title] | [keyword] | transactional | case study | Art. 3, Pillar |
| 6 | [Article title] | [keyword] | informational | FAQ page | Art. 1, Art. 2 |
---
### Priority 3 — Write These Last
Long-tail reinforcement. Lower volume, high conversion intent.
| # | Title | Target Keyword | Intent | Content Type | Links To |
|---|------------------------------|----------------------|-----------------|------------------|------------------|
| 7 | [Article title] | [keyword] | transactional | review | Pillar Page |
| 8 | [Article title] | [keyword] | informational | glossary | Art. 2, Art. 4 |
---
## Internal Link Map
Pillar Page
├── Article 1 → links back to Pillar
├── Article 2 → links back to Pillar
├── Article 3 → links back to Pillar, links to Article 1
├── Article 4 → links to Article 1, Pillar
├── Article 5 → links to Article 3, Pillar
├── Article 6 → links to Article 1, Article 2
├── Article 7 → links to Pillar
└── Article 8 → links to Article 2, Article 4
Rule: Every cluster article must link back to the Pillar Page.
Rule: No orphan articles — every article links to at least one other article.
## Foundational Page Plan
| # | Page / Article | Problem Solved | Primary Query | Intent | Product CTA | Supporting Links |
|---|----------------|----------------|---------------|--------|-------------|------------------|
| 1 | [title] | [problem] | [query] | [intent] | [CTA] | [targets] |
Use this section for the first publishing wave. The landing page, foundational pages, and later cluster articles must not compete for the same intent.
## 20-Day Editorial Calendar
| Day | Topic / Title | Target Query | Search Intent | Article Format | Internal Link Target | External Distribution Candidate |
|-----|---------------|--------------|---------------|----------------|----------------------|--------------------------------|
| 1 | [title] | [query] | [intent] | [format] | [page] | [Medium/Hashnode/dev.to/other] |
Propose up to 20 distinct topics after the foundation is mapped; use fewer when intent evidence does not justify more. Prefer topics that answer real questions, solve problems, support the product, and can be linked back to a foundational page.
---
## Content Gap Analysis
Potential gaps (verify competitor coverage before claiming absence):
- [Gap 1 — underserved angle on the pillar topic]
- [Gap 2 — long-tail question with no strong existing answer]
- [Gap 3 — AEO opportunity: question AI engines commonly surface]
Topics to deliberately exclude from this cluster
(belong to a different cluster):
- [Out-of-scope topic 1]
- [Out-of-scope topic 2]
---
## AEO Cluster Signals
At least 2 cluster articles must be structured as direct-answer pages:
- One FAQ page targeting 8–10 questions around the pillar topic
- One "What Is" explainer with a clean definition as the opening sentence
Direct answers can improve clarity; there is no guaranteed extraction or citation probability for these formats.
---
## Cluster Health Checklist
- [ ] Pillar page defined with clear keyword and intent
- [ ] 5–10 foundational pages generated, default 10 when justified
- [ ] Every article has a unique target keyword (no overlap)
- [ ] Every article assigned a content type
- [ ] Every article linked back to the Pillar Page
- [ ] No orphan articles in the link map
- [ ] At least one FAQ page in the cluster
- [ ] At least one comparison or case study article
- [ ] Content gap section completed
- [ ] Every foundational page has a distinct search intent and conversion path
- [ ] 20-day editorial calendar completed without cannibalizing existing pages
可用内容类型
分配内容类型时,只能使用此列表中的类型:
| 类型 | 最适合 |
|---|---|
| 操作指南 | 分步流程 |
| 说明文 | 概念定义和概述 |
| 清单文章 | 汇总、工具、资源 |
| 对比文章 | X 与 Y、最佳选项 |
| 案例研究 | 实际应用、成果 |
| 常见问题页面 | 问题集群、AEO 定向 |
| 评测 | 产品或服务评估 |
| 术语表 | 术语、定义、长尾关键词 |
| 观点/见解 | 思想领导力、反常规角度 |
执行步骤
- 阅读
existing_content——标记已有的标题, 避免集群内容重复 - 确定支柱主题完整的语义范围—— 围绕该主题的相关问题、角度和子主题
- 检查内容缺口——找出该领域中服务不足 或完全缺失的角度
- 为每个子主题分配一个独特关键词,确保文章之间 以及子主题与支柱关键词之间没有重叠
- 在分配内容类型之前,先对每个子主题的搜索意图进行分类
- 根据搜索量和基础相关性,将所有子主题 分为优先级 1、2 和 3
- 在扩展为 20 天日历之前,先制定 5–10 页的基础计划
- 构建内部链接图——确认不存在孤立文章
- 标出集群中 AEO 机会最高的 2 篇文章
- 在输出前完成内容缺口部分和编辑日历
关联技能
- 接收以下技能的输出:
seo-aeo-keyword-research - 向以下技能提供输出:
seo-aeo-blog-writer、seo-aeo-internal-linking
适用场景
在围绕产品、服务或主题规划支柱页面、基础页面和配套文章时使用。
限制
-
搜索量、竞争对手缺口和 AI 引用机会需要基于当前观察,并附上来源和日期;否则应将其标记为假设。规划不代表授权发布内容或对外分发。不得捏造案例研究、评测或客户成果。
-
内容地图是用于确定优先级的辅助工具,不代表已测得的需求,也不保证所有拟议主题都能获得排名。
评论
支持 Markdown