topic-cluster-planning
Use when planning a topic cluster (hub + spokes) for a new content area.
Skill by inhouseseo
Chalk Labs
Need help deploying topic-cluster-planning?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/inhouseseo-topic-cluster-planning
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: writing, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/topic-cluster-planning
What's inside
- Skill name
topic-cluster-planning- Description
- Use when planning a topic cluster (hub + spokes) for a new content area. The agent researches the space, identifies the hub topic, maps the spokes, and produces a specific content plan with internal linking strategy.
- License
- Apache-2.0
- Instructions
- 134 lines in SKILL.md · view on GitHub
Files (6)
- SKILL.md
- first-link-weight-evidence.md · references/
- pillar-page-template.md · references/
- publishing-sequence-decisions.md · references/
- spoke-selection-worked-example.md · references/
- topic-cluster-strategy.md · references/
SKILL.md (first lines)
# Topic Cluster Planning
Builds a hub-and-spoke architecture for a new content area. Hub = a broad pillar page that owns the topic. Spokes = specific articles that target long-tail keywords and link up to the hub. Done right, this signals topical authority to Google and concentrates link equity on the pages that matter.
## Input
**Seed topic or broad keyword** (required). Example: "email marketing", "keto diet", "small business accounting".
Optionally: your domain, so the agent can check what you've already published in this space.
## Role
You are a senior SEO content strategist specializing in topical authority architecture. You think in clusters, not individual articles.
## Step 1: Research the Topic Space
Google the seed topic. Read:
- The top 10 results for the broad keyword
- The People Also Ask questions
- The "Searches related to" at the bottom of the SERP
- 2-3 major publications in the space to see how they structure their content
Note:
- Who dominates the broad keyword? (This tells you the difficulty level.)
- What sub-topics emerge from PAA and related searches?
- What specific questions do people ask?
Use only PAA questions and related searches you actually saw — don't pad the spoke list with invented queries. If the SERP shows few, say so and lean harder on competitor coverage.
## Step 2: Identify the Hub
The hub is the one page that deserves to own the broad topic. It should:
- Target the broad/seed keyword directly
- Cover the topic comprehensively at a high level (don't go deep on every sub-topic)
- Link out to all the spoke articles
**Hub content type options:**
- **Ultimate guide** ("The Complete Guide to X") — best for broad informational topics
- **Pillar + chapters** (pillar page with a TOC linking to deep-dive chapters) — best for very broad topics with clear sub-chapters
- **Category page with curated featured content** — best for product/service topics
State your recommended hub format with reasoning.
## Step 3: Map the Spokes
From the PAA questions, related searches, and competitor coverage, identify 8-15 specific spoke topics. Each spoke should:
- Target a long-tail keyword or specific question
- Go deeper on one narrow sub-topic than the hub can
- Link back to the hub (primary)
- Link to 2-3 related spokes
For each spoke, specify:
- Target keyword / question it answers
- Content type (how-to / definition / comparison / case study / listicle)
- Approximate word count
- Why it matters for the cluster (what sub-topic does it own?)
**Rule of thumb:** a spoke should answer a question the hub can only summarize.
## Step 4: Map the Internal Linking
Draw the link graph:
- Every spoke links to the hub with a keyword-rich anchor
- Hub links to every spoke (usually in a "In this guide" TOC or a "Related deep dives" section)
- Related spokes link to each other (but sparingly — don't over-link)
- External links from the hub to 3-5 authoritative sources in the space
**Critical:** the first link from any spoke TO the hub is what Google's algorithm weights most heavily. Make sure it's contextual (within the article body), with a descriptive anchor text.
## Step 5: Publishing Order
Don't publish the hub first. Publish 3-4 high-quality spokes first, then the hub with links to them. Then publish the remaining spokes, each linking back to the now-established hub.
This prevents the hub from launching as a link-less orphan that has nothing to point to.
## Step 6: Output
### Cluster Overview
- Seed topic | Estimated difficulty (Easy / Moderate / Hard) based on SERP competition
- Realistic timeline to build out (how many articles, how many months)
### Hub
- Recommended format (Ultimate guide / Pillar + chapters / Category)
- Target keyword (the broad seed)
- Main H2 sections (roughly 5-10)
- Approximate word count
- What the hub should NOT cover in depth (save that for spokes)
### Spoke List
| # | Spoke Topic | Target Keyword | Content Type | Words | Hub Anchor Text |
|---|---|---|---|---|---|
8-15 rows. Sorted by priority: highest-impact/easiest-to-rank first.
### Publishing Sequence
1. **Month 1**: 3-4 spokes (pick from rows 1-4)
2. **Month 2**: Publish the hub, link it to the published spokes
3. **Month 3-4**: Remaining spokes, each linking back to the hub
### Internal Link Map
A simple list showing which spokes link to which other spokes. Not every spoke needs to link to every other — just the naturally related ones.
### External Linking Strategy
3-5 authoritative external sources the hub should cite. (Not competitors — actual authoritative sources: research papers, industry standards, government/university resources, or the primary creators of the concepts you're discussing.)
### Success Metrics
- **Month 3**: Hub should rank somewhere in top 50 for the seed keyword
- **Month 6**: At least 2-3 spokes ranking in top 20 for their long-tail keywords
- **Month 9**: Hub ranking top 20, cluster driving consistent organic traffic
- **Month 12**: Cluster becomes a topical authority signal for the whole domain
## What to Ignore
- **Publishing everything at once** — Google needs time to see the cluster form. Spread it over 3-4 months.
- **Over-linking between spokes** — if it doesn't feel natural in the article, skip it
- **Keyword density in the hub** — the hub is about breadth, not keyword stuffingFrom inhouseseo/superseo-skills, Apache-2.0.
More from inhouseseo/superseo-skills
- 0.761score
content-brief
inhouseseo
Use when planning a new article.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
eeat-audit
inhouseseo
Use when auditing a page for E-E-A-T signals.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
expert-interview
inhouseseo
Use when extracting first-party expertise from a subject-matter expert before writing content.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
featured-snippet-optimizer
inhouseseo
Use when you want to win a featured snippet for a keyword you already rank for.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
improve-content
inhouseseo
Use when rewriting or refreshing an existing page that's underperforming.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
keyword-deep-dive
inhouseseo
Use when planning to rank for a specific keyword.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
linkbuilding
inhouseseo
Use when planning link acquisition.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
page-audit
inhouseseo
Use when auditing a specific page's SEO performance, content quality, and competitive position.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
semantic-gap-analysis
inhouseseo
Use when a page ranks for a keyword but isn't in the top 3 and you want to know exactly what's missing.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
write-content
inhouseseo
Use when writing a complete SEO article.
SkillBFreshness: B★ 366Claude Code +9
Signals
- Stars
- 366
- Forks
- 45
- Open issues
- 1
- Last commit (this folder)
- Sep 3, 2026 (1 month ago)
- Last release
- Sep 3, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/inhouseseo/superseo-skills
- Website
- inhouseseo.ai
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from inhouseseo
- 0.761score
content-brief
inhouseseo
Use when planning a new article.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
eeat-audit
inhouseseo
Use when auditing a page for E-E-A-T signals.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
expert-interview
inhouseseo
Use when extracting first-party expertise from a subject-matter expert before writing content.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
featured-snippet-optimizer
inhouseseo
Use when you want to win a featured snippet for a keyword you already rank for.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
improve-content
inhouseseo
Use when rewriting or refreshing an existing page that's underperforming.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
keyword-deep-dive
inhouseseo
Use when planning to rank for a specific keyword.
SkillBFreshness: B★ 366Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get topic-cluster-planning running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
topic-cluster-planning skill. Agent Mart. https://agentmart.dev/skills/inhouseseo-topic-cluster-planning (last updated 2026-10-24)