In shortThere's no fixed number of pages in a content cluster — the right size depends on the topic, how competitive it is, and how many genuine questions clients ask within it. A narrow subject might need a pillar and a handful of supporting pages; a broad, competitive practice area might warrant many more.
The mistake is treating it as a number to hit: too few pages and the cluster lacks the depth to build authority, too many and it fills up with thin, padded content that hurts. The right size is a planning decision, not a guess.
Why the page count is the wrong question
Asking how many pages a cluster needs is natural, but answering with a fixed number misunderstands how clusters work. A cluster exists to cover a topic thoroughly enough to build authority — and how much coverage that takes depends entirely on the topic, not on a target figure.
Chasing a page count leads to bad outcomes in both directions: padding a simple topic with unnecessary pages, or under-serving a big one with too few. The number should be an outcome of covering the subject well, not a goal in itself.
What actually determines the right size
A cluster's proper size comes from a few real factors: how broad the topic is, how competitive it is, and how many genuine, distinct questions clients ask within it. A tightly defined area with a handful of key questions needs a modest cluster; a broad, contested practice area with dozens of real client questions warrants a much larger one.
Working that out means understanding the topic and the market — which is planning, not counting. The right cluster is the one that covers what genuinely needs covering, no more and no less.
Why guessing wastes effort
Guess too small and the cluster never reaches the depth needed to build authority, so the effort underperforms. Guess too large and you pad it with thin pages that add nothing and can actively drag the site down. Either way, effort is wasted — which is expensive in time and money.
This is why cluster size is worth planning properly rather than guessing. Our Content Cluster Build service maps the right scope for a topic before building — so the cluster is the size it needs to be to work, not an arbitrary number that misses.