seo-aeo-content-cluster – Writing & Content skill for AI agents
Builds a topical authority map from business goals, search intent, existing content, and gaps, then prioritises foundational and supporting pages.
Install the seo-aeo-content-cluster skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/seo-aeo-content-cluster-85ab7.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /seo-aeo-content-cluster – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/seo-aeo-content-cluster-85ab7.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $seo-aeo-content-cluster – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/seo-aeo-content-cluster-85ab7.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /seo-aeo-content-cluster – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/seo-aeo-content-cluster-85ab7.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /seo-aeo-content-cluster – then describe the task you want done.
SKILL.md content
Content Cluster Skill
Description
Activate this skill when the user wants to build topical authority around
a subject by mapping out a pillar page and its supporting cluster articles.
Trigger phrases include: "build a content cluster", "create a topic map",
"content pillar strategy", "what should I write about for [topic]",
"cluster: [topic]", "generate a content strategy for [niche]".
---
Input Format
{
"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"
}For a new website, produce 5–10 foundational pages, defaulting to 10 only when there are at least 10 distinct, defensible search intents. Do not create near-duplicate pages to hit the default. Every page must solve a problem, own a query, and lead to a relevant product or next step.
---
Output Structure
The skill must always produce output in this exact format:
## 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---
Content Types Available
When assigning content types, use only from this list:
| Type | Best For |
|----------------|-------------------------------------------------|
| how-to guide | step-by-step processes |
| explainer | concept definitions and overviews |
| listicle | roundups, tools, resources |
| comparison | X vs Y, best options |
| case study | real-world application, results |
| FAQ page | question clusters, AEO targeting |
| review | product or service evaluation |
| glossary | terminology, definitions, long-tail keywords |
| opinion/take | thought leadership, contrarian angles |
---
Execution Steps
1. Read existing_content — mark any titles that already exist
so the cluster doesn't duplicate them
2. Identify the pillar topic's full semantic territory —
what questions, angles, and sub-topics surround it
3. Run a content gap pass — what angles are underserved
or missing entirely in this space
4. Assign each subtopic a unique keyword with no overlap
between articles or with the pillar keyword
5. Classify each subtopic's search intent before assigning content type
6. Sort all subtopics into Priority 1, 2, and 3 tiers
based on search volume and foundational relevance
7. Build the 5–10-page foundational plan before expanding to the 20-day calendar
8. Build the internal link map — verify no orphan articles exist
9. Flag the 2 highest AEO-opportunity articles in the cluster
10. Complete the content gap section and editorial calendar before outputting
---
Connected Skills
- Receives output from:
seo-aeo-keyword-research - Feeds output to:
seo-aeo-blog-writer,seo-aeo-internal-linking
When to Use
Use when planning a pillar page, foundational
… (full content is in the download package)
Related skills
- seo-content – Content quality and E-E-A-T analysis with AI citation readiness assessment. Use when…
- seo-content-auditor – Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores…
- seo-content-checker – SEO Content Checker. Use when working with content and target query or reader task.
- seo-content-planner – Creates comprehensive content outlines and topic clusters for SEO. Plans content…
- seo-content-refresher – Identifies outdated elements in provided content and suggests updates to maintain…
- seo-content-writer – Writes SEO-optimized content based on provided keywords and topic briefs. Creates…
- skill-porter – Preview conservative tool-name translations and copy complete local skill bundles for…
- skill-writer – Create and improve agent skills following the Agent Skills specification. Use when asked…