calm-north/seojuice-skills

build-clusters

Build a topical authority cluster from a seed keyword or topic.

Vedi sorgente
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Build 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

Before You Start

Gather this context (ask if not provided):

  1. Seed topic. The broad subject area to build authority around.
  2. Existing content. Does the site already have pages on this topic? List them.
  3. Business relevance. How does this topic connect to the product or service?
  4. Content capacity. How many pieces can the team produce per month?

Step 1: Subtopic Discovery

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.

Step 2: Cluster Map

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)

Step 3: Coverage Scoring

Score how well the existing site covers the cluster:

SubtopicExisting Page?Quality (1-5)TrafficGap?
[subtopic 1]/blog/topic-14500/moNo
[subtopic 2]Yes
[subtopic 3]/blog/old-post250/moPartial (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

Step 4: Pillar Page Design

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.

Step 5: Interlinking Plan

Map the internal links:

From PageTo PageAnchor TextContext
PillarSpoke 1"[subtopic 1] guide"In the subtopic 1 overview section
Spoke 1Pillar"[broad topic]"In the introduction or conclusion
Spoke 1Spoke 2"[subtopic 2]"Where subtopic 2 is mentioned contextually
Spoke 3Spoke 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)

Step 6: Cluster Health Metrics

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
MetricScoreThreshold
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

Expected Outcomes by Health Level

Cluster StateCoverageLink HealthContent QualityExpected Result
Incomplete<50%<70%AnyPillar unlikely to rank page 1; spokes rank individually at best
Developing50-70%70-90%50-80%Pillar may appear page 2-3; some spokes rank for long-tail
Competitive70-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

Internal Link Standards per Cluster

Link TypeMinimum CountDirection
Pillar → each spoke1 per spokeDownward — link from the relevant section of the pillar
Each spoke → pillar1 per spokeUpward — "our complete [topic] guide"
Spoke ↔ sibling spokes2-4 per spokeLateral — where contextually natural
Cross-cluster bridges0-2 per clusterBetween 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.

Step 7: Production Sequence

Order the content production for maximum impact:

  1. Pillar page first — even as a draft, it establishes the hub
  2. Highest-opportunity spokes next — pages targeting gaps with the best opportunity scores
  3. Refresh existing spokes — update and relink any partial-gap pages
  4. Remaining spokes — fill out the cluster over time
  5. 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 — run /seojuice:content-strategy to see existing clusters with coverage metrics, or use list_clusters and get_cluster_detail to check cluster health and identify gaps.
dallo stesso repository

Altri Skills

Tutti gli Skills
calm-north
Community

audit-speed

Deep Core Web Vitals and page speed audit. Use when the user asks about page speed, Core Web Vitals, LCP, CLS, INP, FCP, TTFB, Lighthouse scores, why a page is slow, performance optimization, or resource size analysis. For broader technical SEO issues, see diagnose-seo.

installazioni
1
GitHub Stars
21
Aggiornato
27 feb
calm-north
Community

brief

Produce an editor-ready content brief for a target keyword or topic. Use when the user asks for a content brief, writing guidelines, article outline, SEO brief, what to include in a blog post, or how to structure content for a keyword. For choosing which topics to write about, see find-keywords. For a full site-wide SEO audit, see audit.

installazioni
1
GitHub Stars
21
Aggiornato
27 feb
calm-north
Community

find-keywords

Build a prioritized keyword list for a website, topic, or campaign. Use when the user asks about keyword research, finding keywords to target, building a keyword list, search demand, keyword difficulty, intent mapping, or which keywords to prioritize. For writing content around keywords, see brief. For grouping keywords into clusters, see build-clusters.

installazioni
1
GitHub Stars
21
Aggiornato
27 feb
calm-north
Community

migrate-site

Guide a website migration without losing rankings — domain moves, CMS switches, URL restructures, HTTP to HTTPS, or redesigns. Use when the user asks about site migration, domain change, CMS migration, URL restructure, redesign SEO impact, redirect mapping, or how to move a site safely.

installazioni
1
GitHub Stars
21
Aggiornato
27 feb