What is a Topic Cluster?

A topic cluster is one pillar page linking to and from a bunch of narrower subtopic pages. The internal links tell search engines you have depth on this subject. HubSpot popularized the name around 2017, but grouping related content is older than that. Google's move toward entity understanding—BERT in 2019, MUM in 2021—made clusters work better because engines now look at topical coverage across your whole site, not just individual keyword matches. A typical cluster is one pillar page hitting a high-volume head term, 8–25 subtopic pages on long-tail variations, and bidirectional links between them. We've shipped this on 50+ projects. It beats flat blog structures for organic traffic growth in 3–6 months.

How it works

Three pieces:

Pillar page — Long-form (1,500–4,000 words) covering the broad topic. Links out to every subtopic in the cluster.
Subtopic pages — Individual pages (800–2,000 words) targeting specific long-tail keywords. Each links back to the pillar and optionally to sibling subtopics.
Internal linking mesh — The bidirectional links distribute PageRank, establish semantic relationships, and help crawlers understand hierarchy.

Simplified sitemap:

/seo-guide (pillar)
  ├── /seo-guide/keyword-research (subtopic)
  ├── /seo-guide/on-page-seo (subtopic)
  ├── /seo-guide/technical-seo (subtopic)
  ├── /seo-guide/link-building (subtopic)
  └── /seo-guide/content-optimization (subtopic)

In Astro and Next.js projects, we use a content collection (Astro) or MDX directory (Next.js) with a shared cluster frontmatter field. A build-time script generates the pillar's link list and injects rel attributes automatically. This removes the manual linking work that causes clusters to rot.

The key technical detail: internal anchor text matters. Each pillar → subtopic link should use descriptive, keyword-relevant anchor text. Not "click here" or "read more." Google uses anchor text as a ranking signal for the destination page.

When to use it

Clusters aren't universal. They work in specific scenarios.

Use a topic cluster when:

You're targeting a broad topic with 10+ related long-tail queries (check Ahrefs or Semrush for keyword groupings)
You've got scattered content on a topic that needs consolidation
You're building a new content vertical from scratch and want a clear editorial roadmap
You're doing programmatic SEO and need a structural parent for generated pages

Skip the cluster when:

The topic is too narrow to support more than 3–4 subtopics—you'll create thin pages just to fill slots
You're a single-product SaaS with 5 total pages; focus on those pages
You don't have the editorial capacity to maintain the cluster—outdated subtopic pages hurt more than they help
The topic doesn't map to search intent (internal company updates, for example)

Biggest mistake we see: forcing every piece of content into a cluster. Not all content needs a parent. Some pages stand alone.

Topic Cluster vs alternatives

Approach	Structure	Best for	Weakness
Topic Cluster	Pillar + subtopics with internal links	Mid-to-high volume informational topics	Requires ongoing maintenance
Flat Blog	Chronological posts, minimal linking	News, personal blogs	No topical signal to engines
Hub & Spoke	Nearly identical to topic cluster	Often used interchangeably	Same trade-offs
Programmatic SEO	Template-driven pages at scale	Data-rich, high-variation queries (city pages, product comparisons)	Risk of thin content without cluster context
Content Silo	Strict hierarchical folders, no cross-linking	Large enterprise sites with distinct verticals	Too rigid; cross-links between silos can actually help

"Hub & spoke" and "topic cluster" describe the same pattern. Content silos are a stricter, older version we rarely recommend because the no-cross-linking rule leaves ranking potential on the table.

Real-world example

We built a cluster for a B2B SaaS client targeting "workflow automation." Pillar page was ~3,000 words covering the concept broadly. We created 14 subtopic pages: "workflow automation for HR," "Zapier vs Make comparison," "workflow automation ROI calculator." Each subtopic linked back to the pillar with keyword-rich anchor text. We cross-linked related subtopics (ROI calculator → comparison page). Within 4 months, the pillar ranked on page 1 for "workflow automation" (monthly search volume ~8,100 in Ahrefs US). The cluster collectively drove 12,000+ organic sessions/month. The critical factor wasn't word count—it was the linking structure and the fact that every subtopic genuinely answered a distinct user question.

Frequently asked questions about Topic Cluster

Is a topic cluster the same as a content silo?

They're related but not identical. A content silo is an older architectural pattern that uses strict folder hierarchy and deliberately avoids cross-linking between silos. A topic cluster is more flexible: subtopic pages link back to their pillar, but you're encouraged to cross-link between related subtopics and even between clusters when it makes sense. The silo model came from Bruce Clay's work in the mid-2000s. Topic clusters evolved from that thinking but dropped the rigid isolation rules. In 2026, the cluster approach is more practical because Google's entity understanding rewards topical connections across your site, not just within one folder.

When did topic clusters become a standard SEO practice?

HubSpot's research team formalized and popularized the term "topic cluster" in 2017 with their pillar page strategy. But the underlying concept—grouping related content with internal links to build authority—has been an SEO tactic since the early 2010s. Google's BERT update (October 2019) and later MUM (May 2021) made the pattern more effective because these models evaluate topical depth across multiple pages. By 2020, most enterprise SEO teams had adopted some version of the cluster model. Today it's considered a baseline content architecture pattern, not an advanced tactic.

What's the alternative to a topic cluster?

The main alternatives are a flat blog structure (chronological posts with minimal internal linking), programmatic SEO (template-generated pages targeting keyword variations at scale), or standalone long-form guides that try to rank for both head terms and long-tail queries on a single URL. Flat blogs work for news sites but leave topical authority on the table. Programmatic SEO is powerful for data-driven queries but needs a parent structure—often a pillar page—to avoid thin content penalties. Single mega-guides can rank, but they max out at some point; you can't realistically cover 20 subtopics in depth on one page without hurting UX.

How many subtopic pages should a topic cluster have?

There's no magic number, but 8–25 subtopic pages is a practical range for most clusters. Fewer than 5 and you probably don't have enough topical depth to justify the architecture—just write a thorough single page. More than 30 and maintenance becomes a real burden; pages go stale, internal links break, and editorial quality drops. The right count comes from keyword research: group related long-tail queries using tools like Ahrefs keyword clustering or Semrush's topic research, and each distinct intent group becomes a subtopic page. Don't create pages just to hit a number. Every subtopic should answer a genuinely different question.

What is Topic Cluster?