build-hub-and-spoke-content-architectures-and-pillar-pages

Summary

When deciding how to organize content around a competitive keyword or topic cluster, this skill helps the agent choose between hub-and-spoke (navigation-first with multiple spoke pages) and pillar page (comprehensive single-page) architectures, then execute the chosen structure with proper internal linking and content organization.

SKILL.MD

Build Hub-and-Spoke Content Architectures and Pillar Pages

When to Activate

Load this skill when you need to:

  • Plan content architecture for a competitive keyword
  • Design an SEO content strategy for a topic with multiple subtopics
  • Choose between hub-and-spoke or pillar page approaches
  • Structure internal linking for topical authority

Core Knowledge

Hub-and-Spoke Strategy

What it is: A content architecture with a central hub page (table of contents) that links to multiple spoke pages covering subtopics. The hub's purpose is to send visitors to spokes, not retain them.

When to use it:

  • Topic has many obvious subtopics
  • Targeting a single competitive keyword
  • Site lacks strong domain authority (one blog post per keyword won't rank)
  • You need to throw "more firepower" at a competitive term

Why it works:

  • Leverages site structure as technical SEO advantage against competitors who don't execute well
  • Creates multiple ranking opportunities—each spoke can earn organic traffic while building authority toward the hub
  • Hub pages achieve low bounce rates (correlated with better rankings)
  • Internal linking increases dwell time (correlated with better rankings)
  • Simple navigation structure from hub → spokes → hub → other spokes

Examples to reference:

  • Hotjar: "A beginner's guide to usability testing"
  • Vero: "The Ultimate Lifecycle Email Marketing Guide"
  • Amplitude: "Mobile Analytics: A Complete Guide" (variant that links to both owned and external content)

Note: "Cluster" is synonymous with hub-and-spoke in most usage.

Pillar Page Strategy

What it is: A single, comprehensive, long-form page covering a topic in exhaustive depth. All content lives on one page. If you folded a hub and all its spokes into one page, you'd have a pillar.

When to use it:

  • Topic can be comprehensively covered in one location
  • You want to convey authority through depth
  • Readers prefer consolidated content over fragmented articles
  • You're optimizing for backlink acquisition

Why it works:

  • Content >3000 words earns 77.2% more referring domain links than content <1000 words (Brian Dean research)
  • Readers may prefer comprehensive single articles over collections
  • Long-form signals authority and drives higher conversions for SaaS companies
  • Can still build extensive internal links TO the pillar from other content

Structure pattern: Break into sections with table of contents at top for navigation within the page.

Examples to reference:

  • Vestd: "Starting an EMI share options scheme: Everything you need to know"
  • 7Shifts: "The Ultimate Guide to Restaurant Costs"
  • Wistia: "The Wistia Guide to Video Marketing" (hybrid that also links to other owned content)

Constraints / Hard Rules

Hub-and-Spoke

  • Hub MUST link to all spokes
  • Each spoke MUST link back to hub
  • Each spoke SHOULD link to other relevant spokes
  • Hub's primary function is navigation, not content retention

Pillar Pages

  • Must be comprehensive—no gaps in topic coverage
  • Build internal links FROM other content TO pillars
  • Use table of contents for navigation within page

Workflow

1. Choose Your Approach

Select hub-and-spoke if:

  • Topic clearly breaks into 5+ distinct subtopics
  • Each subtopic warrants 1000+ words
  • You're targeting a highly competitive keyword
  • Site authority is low-to-medium

Select pillar page if:

  • Topic is best consumed as unified narrative
  • You want to maximize backlink potential
  • Goal is to establish authoritative resource
  • Content can be structured with clear internal sections

2. Map Content Structure

For hub-and-spoke:

  • Identify the central competitive keyword (hub target)
  • List all subtopics (future spokes)
  • Verify each subtopic has search volume and can stand alone
  • Plan hub as navigational guide, not comprehensive content

For pillar:

  • Outline major sections covering topic exhaustively
  • Ensure logical flow for linear reading
  • Plan table of contents structure
  • Target 3000+ words for backlink optimization

3. Build Internal Linking Architecture

For hub-and-spoke:

  • Create bidirectional links: hub ↔ each spoke
  • Create lateral links: spoke ↔ other relevant spokes
  • Build links FROM other site content TO hub and relevant spokes

For pillar:

  • Identify all existing content that should link TO pillar
  • Build contextual internal links within pillar to related content
  • Ensure pillar is discoverable from high-traffic pages

4. Execute Content Production

For hub-and-spoke:

  • Write hub as concise table of contents with descriptions
  • Produce each spoke as standalone article optimized for its subtopic keyword
  • Implement complete linking structure before publication

For pillar:

  • Write comprehensive long-form content (aim for 3000+ words)
  • Add clear section breaks with descriptive headings
  • Create functional table of contents with jump links
  • Ensure each section is complete but flows into next

Output Contract

When using this skill, you should produce one of:

Hub-and-Spoke Architecture Plan:

  • Hub page keyword target and purpose statement
  • List of spoke topics with keyword targets
  • Internal linking map (hub → spokes, spokes → hub, spokes ↔ spokes)
  • Content brief for hub (navigational focus)
  • Content briefs for each spoke

Pillar Page Plan:

  • Pillar page keyword target and purpose statement
  • Detailed outline with major sections
  • Table of contents structure
  • Target word count (minimum 3000)
  • List of pages that should link TO this pillar
  • List of related content to link FROM pillar

Hybrid Recommendation: When appropriate, note if a hybrid approach (pillar that links to related owned content) better serves the use case.


Source: Hubs vs. Pillars: What's the Difference?