Skip to main content
skill CX Codex

topic-cluster-planning — Claude Code skill for SEO content clusters

Research a content area and turn it into a hub page, supporting articles, and a linking plan. Use it when you need a structured publishing roadmap for a new topic.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a claude-code
Open on GitHub

What topic-cluster-planning does

Give the skill a seed topic or broad keyword. It examines Google results, People Also Ask questions, related searches, and coverage from major publications, then recommends a hub format and specific spoke articles. Each spoke gets a target query, content type, approximate word count, and a role in the cluster.

The plan also covers links between the hub and spokes, external sources for the hub, and a publishing sequence. You can provide a domain so the agent can account for existing pages. It should base spoke ideas on queries found during research, so Google access is needed; it is instructed not to pad the list with invented searches.

What it helps with

  • turn a broad keyword into a hub-and-spoke content plan
  • find specific queries for supporting articles
  • map contextual links between the hub and related pages
  • sequence cluster articles for publication

Example prompts for the agent

  • Plan a topic cluster around email marketing, with a hub page and supporting articles.
  • Research small business accounting and map spoke topics to target queries and internal links.
  • Review the content already published on my domain and suggest missing pages for this cluster.

How to install topic-cluster-planning

1Skills CLI (Vercel)

npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a claude-code

2Manually: put the files in place

~/.claude/skills/topic-cluster-planning/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/topic-cluster-planning/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about topic-cluster-planning

How do I install topic-cluster-planning in Claude Code?

Run npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a claude-code. The skill file is at ~/.claude/skills/topic-cluster-planning/SKILL.md.

What does topic-cluster-planning do?

It researches a broad subject and drafts a cluster structure with a hub page, focused supporting articles, internal links, and a release order.

What does the skill need to work?

Provide a seed subject or broad keyword. A domain is optional for checking existing content, and the research process uses Google.

Source text

SKILL.md · Apache-2.0
---
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.
---

# 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 stuffing

## Next Step

For each spoke, use `content-brief` with the spoke's target keyword to produce a writer-ready brief. Then `write-content` to write the article.

## Bundled references

Load from `references/` only when the step calls for them.

- **`first-link-weight-evidence.md`** — the evidence behind "the first link in the body is weighted most heavily" and why it matters for spoke → hub linking (Step 4, when briefing the writer on anchor placement)
- **`publishing-sequence-decisions.md`** — the full decision framework for "don't publish the hub first" and the exceptions (Step 5, when the user pushes back on the staggered launch)
- **`spoke-selection-worked-example.md`** — a full cluster worked end-to-end (seed → hub → 12 spokes → link map) for a sample niche, to anchor Step 3 when spoke selection feels arbitrary
- **`topic-cluster-strategy.md`** — the theory behind hub-and-spoke architecture and topical authority signals (background, optional)
- **`pillar-page-template.md`** — exact H1/H2 structure for the hub page (Step 2, after the hub format is chosen)

© inhouseseo · Apache-2.0 · inhouseseo/superseo-skills

Similar skills

All skills for SEO and GEO →

From the same set10

write-content Writes complete SEO articles in Markdown using real search results and anti-slop rules without keyword export files. Useful when building blog content that sounds like real practitioner work. CX Codex +1 ★ 370repo stars page-audit Audits an individual URL across seven SEO dimensions and evaluates top 3 Google competitors without requiring analytics access or crawl files. CX Codex +1 ★ 370repo stars linkbuilding This skill assesses a site's authority phase and recommends matching link acquisition tactics. Use it to shape a plan around a domain and its visible signals. CX Codex +1 ★ 370repo stars keyword-deep-dive This skill studies one keyword: reads the Google SERP, inspects the top three competitors and returns a 90-day ranking plan. Useful when you are deciding whether a query is worth chasing. CX Codex +1 ★ 370repo stars improve-content Refreshes underperforming web pages: crawls the existing URL, analyzes top 5 SERP competitors, and rewrites the markdown copy using strict anti-slop rules. CX Codex +1 ★ 370repo stars featured-snippet-optimizer This skill examines Google's current featured snippet and reshapes a matching section of your page to fit its format. Use it when your page already ranks well for the target query. CX Codex +1 ★ 370repo stars expert-interview Runs a short interview with a subject-matter expert and turns the answers into a knowledge document full of specifics AI cannot invent. CX Codex +1 ★ 370repo stars eeat-audit Audits web pages against Google's E-E-A-T criteria, scores four quality signals, and lists actionable fixes. CX Codex +1 ★ 370repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor