Claude Marketplaces
SkillsMCP serversMarketplacesDigestTools
Submit

This week in Claude

Every Monday: Claude Code, Agent SDK, MCP, and the Anthropic platform moves worth your time.

Skills by category
Frontend DevelopmentBackend & APIsTesting & QASecurityDevOps & CI/CDGit & Pull RequestsDocumentationCode Review & QualityAI & Agent BuildingSkill Development
MCP servers by category
Sales & MarketingWeb & Browser AutomationDatabasesAI & LLM ToolsCloud & InfrastructureCommunication & MessagingDeveloper ToolsDesign & CreativeDocuments & KnowledgeSearch & Web Crawling
Marketplaces by category
AI Agents & OrchestrationLLM IntegrationDevelopment ToolsFrontend & UIBackend & APIsDatabasesTesting & Code QualityDevOps & CloudSecurity & ComplianceGit & Version Control
Claude Marketplaces

An independent directory of skills, plugins and MCP servers for Claude Code. Not affiliated with Anthropic.

Browse

  • Skills
  • MCP servers
  • Marketplaces
  • Weekly digest
  • Skill index
  • MCP index
  • Marketplace index

Site

  • About
  • Tools
  • Submit
  • Feedback
  • Privacy
  • llms.txt
  • Plugins reference

Maker

  • Snug
  • Agent Caffeine
  • knobs
  • Wax
  • Vectoys
  • mertduzgun.com
Crafted at
Skills/DevOps & CI/CD
calm-north avatar

Build Clusters

calm-north/seojuice-skills

This walks you through building a proper topic cluster from a seed keyword: pillar page targeting the head term, 8-20 spoke pages covering subtopics, and the bidirectional linking structure Google actually rewards. It scores your existing coverage, helps you prioritize which gaps to fill first, and gives you health metrics (coverage, link health, content quality) so you know when the cluster is actually ready to compete. The output is a production roadmap with an interlinking plan, not just a list of article ideas. Use it when you're trying to rank for a competitive keyword and need the supporting content architecture, not when you just need one blog post.

installs
2.1K
GitHub stars
21
last updated
Aug 21, 2026
View on GitHubSave

Install

$ npx -y skills add calm-north/seojuice-skills --skill build-clusters --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub

Sponsors

SnugThe clipboard manager you and your agent can use, safelyAgent CaffeineClose your lid, come back to finished workWaxBlock anything with supervision, without erasing your iPhoneOpen StepsSponsoredFree and open-source skills that make AI coding agents easier to understand, verify, and control.

Details

Repository
github.com/calm-north/seojuice-skills
Categories
DevOps & CI/CD, Documentation, Code Review & Quality, Marketing & SEO

More from calm-north/seojuice-skills

All 14
  • Recover Content2.1K
  • Fix Linking2K
  • Target Serp2K
  • Find Keywords7K
  • Optimize For Ai6.6K
  • Build Links6.5K
  • Brief6.4K
  • Audit6.4K
  • Rank Local2.5K
  • Audit Speed2.4K
  • Diagnose Seo2.1K
  • Migrate Site2.1K
  • Beat Competitors2.1K

Recommended

More DevOps & CI/CD
1anthropics avatarbuild-zoom-botanthropics/knowledge-work-pluginsBuild a Zoom meeting bot, recorder, or real-time media workflow. Use when joining meetings programmatically, processing live media or transcripts, or combining 2.1Kinstalls
2anthropics avatarbuild-zoom-team-chat-appanthropics/knowledge-work-pluginsReference skill for Zoom Team Chat. Use after routing to a chat workflow when building user-scoped messaging integrations, chatbot experiences, rich cards, butt2.1Kinstalls
3anthropics avatarbuild-zoom-video-sdk-appanthropics/knowledge-work-pluginsReference skill for Zoom Video SDK. Use after routing to a custom-session workflow when the user needs full control over the video experience rather than an act2.1Kinstalls
4anthropics avatarbuild-zoom-meeting-appanthropics/knowledge-work-pluginsBuild or embed a Zoom meeting flow. Use when implementing Meeting SDK joins, web or mobile meeting embeds, meeting lifecycle flows, or when deciding between Mee2.1Kinstalls
5anthropics avatarbuild-zoom-virtual-agentanthropics/knowledge-work-pluginsReference skill for Zoom Virtual Agent. Use after routing to a virtual-agent workflow when implementing web embeds, Android or iOS wrapper integrations, knowled2.1Kinstalls
6anthropics avatarbuild-zoom-contact-center-appanthropics/knowledge-work-pluginsReference skill for Zoom Contact Center. Use after routing to a contact-center workflow when implementing app, web, or native integrations; engagement context a2.1Kinstalls