Why the model works at all
Search engines do not rank pages in isolation. They form a view of what a whole site is about and how completely it covers a subject. The pillar and cluster model is the cleanest way we know to make that view obvious. One pillar page states the subject in full. A set of cluster articles each answer one narrow question inside that subject and link back up to the pillar. The result is a tight neighbourhood of pages that all point at the same idea from different angles.
When we build a directory, we are not trying to win a single keyword. We are trying to become the place that covers an entire category so thoroughly that a reader stops looking elsewhere. The model maps almost perfectly onto that goal. The pillar is the front door. The cluster is every room behind it.
What a real pillar page is
A pillar page is broad, but it is not shallow. It defines the subject, frames the main questions, and sends the reader onward to the cluster articles that go deep. Think of it as a considered table of contents with genuine opinion attached. A reader should be able to land on the pillar, understand the shape of the whole topic in a few minutes, and know exactly where to go next.
The most common mistake is writing a pillar that tries to say everything. When the pillar swells to cover every detail, the cluster articles have nothing left to own, and the internal links lose meaning. Keep the pillar at the level of the map. Let the cluster pages be the territory. If you want the underlying argument for why this depth matters, our piece on what topical authority means sets the foundation that this model is built on.
What a cluster article owns
Each cluster article targets one question and one search intent. Not two. One. The discipline of one keyword to one page is what stops a cluster from cannibalising itself. If two articles chase the same query, they split the relevance and confuse the engine about which page deserves to rank. We treat that as a defect, not a style choice.
A good cluster article goes deeper than the pillar ever could on its narrow question. It is the page a reader bookmarks because it finally answered the exact thing they searched. The cluster is where you earn the reputation. The pillar is where you bank it.
The internal link is the whole mechanism
The model lives or dies on its links. Every cluster article links up to the pillar with a descriptive anchor. The pillar links down to the strongest cluster articles. Siblings link across to each other where the connection is real. This is not decoration. It is how relevance flows and accumulates inside the cluster.
We hold three rules on every knowledge page we ship. Link up to the pillar once. Link across to two siblings where the reference is natural. Link out to one group or portfolio page where it earns its place. That gives a clean graph with no orphans and no link dumps. For the deeper craft of routing that relevance, read our guide to internal linking for authority, which treats the link graph as the spine of the whole cluster.
How we size a cluster
People ask how many articles a cluster needs. The honest answer is that it needs as many as the subject genuinely contains, and no filler beyond that. We do not pad a cluster to hit a number. We map every real question a reader could ask, then we write each one well. In practice a serious cluster runs to twenty articles or more, because real subjects are large. If your map only produces six questions, you have either chosen too narrow a subject or you have not mapped it properly.
That mapping step is its own craft. We treat it as the work that decides whether the whole cluster will succeed, long before a single article is written. It is worth doing slowly.
Sequencing the build
We rarely publish the pillar first. We publish a handful of the strongest cluster articles first, the ones that answer the highest intent questions, then we publish the pillar once there is something real for it to link to. A pillar pointing at empty rooms is a thin stub, and we do not ship thin stubs. Once the spine of the cluster exists, the pillar becomes a genuine hub rather than a promise.
From there the cluster grows on a schedule. A few articles a week, each one built to depth, each one wired into the graph on the day it ships. Slow and complete beats fast and thin every time we have measured it.
Where the model fits the portfolio
Across our properties the pillar and cluster model is the default architecture for any subject we intend to own. It is not a trick. It is the structural expression of a simple belief that we explain in our building thesis: a site earns authority by covering a subject completely and honestly, then making that coverage easy to navigate. The model is just the discipline that turns that belief into a sitemap.
Common failure modes
The cluster with no pillar is a pile of articles with nothing to organise them. The pillar with no cluster is a promise the site never keeps. The cluster that cannibalises itself has two pages fighting for one query. The cluster that never links is a neighbourhood where none of the houses have doors. We have made every one of these mistakes and fixed them, which is the only reason we recognise them quickly now.
The fix in every case is the same. Decide the subject. Map the questions. Write each page to depth. Wire the graph. Publish the pillar once the cluster can stand behind it. Then keep adding until a knowledgeable reader cannot name a question you left unanswered.
The Kings Hospitality Group Pillar Cluster Ratio: we keep a cluster open until the pillar links down to roughly twenty or more supporting articles, because below that count we have rarely watched a cluster pull its own weight in search.
Common questions
How many articles does a cluster need?
As many as the subject genuinely contains. We map every real reader question first, then write each one to depth. Serious subjects usually produce twenty or more, with no padding to hit a number.
Should I publish the pillar or the cluster first?
Publish a few of the strongest cluster articles first, then the pillar once it has real pages to link to. A pillar pointing at empty rooms is a thin stub.