Once you’ve built a pillar page and started grouping supporting posts around it, a practical question comes up almost immediately: when is a cluster actually finished? Add too few posts and the topic looks thin next to a competitor with real depth. Add too many and you risk the exact overlap problem covered in the previous post in this series, where posts start competing against each other instead of reinforcing a shared pillar.
There’s no single correct number that applies to every topic, but there is a useful range and a set of signals that tell you when a cluster has grown past the point of being helpful.
A Reasonable Starting Range
For most solo bloggers, a healthy cluster tends to land somewhere between five and twelve supporting posts underneath a single pillar page. Below five, the topic usually doesn’t have enough distinct sub-questions to justify its own dedicated pillar in the first place, and is often better treated as a section within a broader pillar rather than a standalone cluster. Above twelve, it becomes increasingly likely that some of those posts are answering nearly the same question from slightly different angles, which edges back toward the content duplication problem discussed earlier in this series rather than genuine topical breadth.
This range is a starting heuristic, not a rule to force onto every topic. Some genuinely broad subjects support twenty or more distinct, non-overlapping supporting posts without any duplication at all, and some narrow subjects are legitimately finished at four or five. The number matters less than the reasoning behind it.
The Real Test: Distinct Reader Questions
The more reliable way to judge cluster size is to list every distinct question a reader interested in the topic would reasonably want answered, then check whether each supporting post maps to exactly one of those questions. If you can list fifteen genuinely distinct questions, a fifteen-post cluster is entirely reasonable. If you’re struggling to name an eighth distinct question and the seventh post already covers most of what an eighth would say, that’s a sign you’ve reached the natural end of the cluster, at least for now.
This is also a useful check in the other direction. If a pillar page’s cluster only has three posts underneath it, but a quick brainstorm turns up eight or nine distinct sub-questions readers would want answered, that gap is a content roadmap rather than a problem — it tells you exactly what to write next, informed by what the topic actually needs rather than by guesswork.
Signs a Cluster Has Grown Too Large
A few patterns tend to show up once a cluster has genuinely outgrown a single pillar. Search Console data for several posts in the cluster starts showing overlapping queries, with rankings for those posts trading places month to month rather than each post clearly owning its own set of search terms. Readers browsing the pillar page’s list of supporting posts start seeing titles that look nearly interchangeable at a glance, unable to tell which post actually answers their specific question without clicking through several of them. And when you try to write the “distinct question” list described above, you find yourself splitting hairs to justify why two posts are different, rather than the difference being obvious.
When these signs show up, the fix usually isn’t deleting content, it’s splitting the cluster. A single pillar that’s accumulated twenty genuinely useful but loosely related posts is often really two or three narrower pillar topics that got treated as one for too long. Splitting means choosing a second (or third) pillar candidate from within the existing posts, regrouping the supporting content underneath whichever pillar it more precisely serves, and adjusting internal links accordingly.
Signs a Cluster Is Too Thin
The opposite problem is quieter and easier to miss, since a thin cluster doesn’t cause the same kind of visible competition a bloated one does. A pillar page with only two or three supporting posts often just sits there looking reasonably fine, without any obvious signal that it’s underperforming its potential.The clearest sign of a thin cluster is a pillar page that ranks decently for its broad core term but fails to show up at all for the more specific long-tail variations a fuller cluster would naturally capture. If your pillar on home coffee brewing ranks fine for “how to brew coffee at home” but never appears for any of the dozen more specific questions a real reader would search around that topic, that’s a sign the supporting posts needed to capture those specific queries simply don’t exist yet.
Balancing Cluster Size Against Available Time
For a solo blogger, the honest constraint is rarely “how many posts should this topic ideally have” and more often “how many posts can I realistically produce and maintain.” A cluster of six well-written, well-linked, periodically updated posts will outperform a cluster of fifteen posts that were rushed out and then never revisited, since content decay eventually catches up with any post that isn’t maintained, regardless of how many total posts sit around it.
A reasonable approach is to treat the five-to-twelve range as a target for a mature cluster, but build toward it gradually, prioritizing the two or three highest-value missing sub-questions rather than trying to fill every gap at once. A cluster that grows to its natural size over six months, with every post genuinely earning its place, will hold up better over time than one assembled in a single sprint to hit a number.
Reassessing Clusters Over Time
Cluster size isn’t a decision made once and left alone. Topics evolve, reader questions shift, and a cluster that was appropriately sized two years ago may need pruning, splitting, or expanding today. The same kind of audit process covered earlier in this series — grouping posts, checking for overlap, checking for gaps against a fresh list of reader questions — is worth revisiting periodically for any cluster that’s core to your site, not just when something is obviously broken.
The next post in this series zooms out from individual clusters to the overall shape of a blog’s structure, covering site architecture fundamentals and how multiple clusters fit together into a coherent whole.