When a Topic Deserves a Pillar Page, Not a Post

Not every topic earns a pillar page. Most don't. A pillar is expensive to produce and expensive to maintain, and building one for the wrong topic ties up hours you could have spent covering three or four smaller questions your buyers actually type. The mistake I see most often isn't publishing too few pillars — it's promoting an ordinary topic to pillar status because it felt important, then watching it sit there, too broad to rank and too generic to convert.

This piece gives you a way to decide before you commit. The goal is to sort each topic into one of two buckets — pillar or post — using signals you can check in an afternoon.

What actually makes a topic a pillar

A pillar page is the hub for a subject wide enough that it splits into multiple genuine sub-questions, each strong enough to hold its own page. The pillar covers the subject at the overview level and links out to those sub-pages, which link back. That structure only makes sense when the subject has real depth underneath it.

Three things separate a pillar topic from a post topic:

• Breadth. The topic naturally breaks into five or more distinct sub-topics that people search for separately. If you can only think of two, it's a post.
• Search demand across the cluster. There's steady, recurring demand for the head term and its variations — not one spike, but a pattern.
• Commercial relevance. The subject connects to something you sell. A pillar on a topic your buyers don't pay for is a library you're funding for strangers.

A topic needs all three. Breadth without demand gives you a sprawling page nobody finds. Demand without commercial relevance gives you traffic that never becomes revenue. Commercial relevance without breadth gives you a topic that should stay a single, focused post.

A scoring test you can run in an afternoon

Score the topic 0-2 on each of five factors. Add them up. The total tells you what to build.

The five factors

Reading the score

• 8-10: Build the pillar. It has the breadth and the demand to justify the cost.
• 5-7: Start with a strong post. If it earns traffic and you find yourself needing to explain sub-topics in depth, expand it into a pillar later.
• 0-4: Post, and probably a short one. Don't overbuild.

The last factor — competitor depth — is the one people skip and shouldn't. If the pages currently ranking for your head term are all 3,000-word resources with sub-sections and internal links, a 900-word post won't compete no matter how good it is. The market has already decided what depth this topic requires.

A worked example

Suppose a commercial HVAC company wants to cover the topic "rooftop unit maintenance." Run the test.

1. Sub-topics: filter schedules, coil cleaning, belt inspection, refrigerant checks, seasonal shutdown, common failure signs, maintenance contract vs in-house. That's seven distinct searches. 2 points.
2. Recurring demand: building managers search this year-round, with predictable bumps before summer and winter. 2 points.
3. Link to what you sell: the company sells maintenance contracts. Direct. 2 points.
4. Buyer decision weight: a manager weighing whether to outsource maintenance is close to a purchase. 2 points.
5. Competitor depth: the top results are detailed guides with sections. 2 points.

Total: 10. This is a pillar. The page covers rooftop unit maintenance end to end at the overview level, then links to separate posts on "how often to change commercial HVAC filters," "signs your rooftop unit is failing," and "maintenance contract vs in-house team." Each of those is a post that ranks for its own query and feeds the pillar.

Now compare a topic like "what SEER rating means." It's one definition. Maybe two sub-questions. It informs a choice but doesn't split into a cluster. Score it and you land around 4. That's a clean, useful 800-word post — and turning it into a pillar would pad it with filler and dilute the answer people came for.

Should I write the pillar first or the cluster posts first?

Write the pillar first as a complete overview, then publish cluster posts around it over the following weeks. The pillar establishes the structure and gives you a place to link each new post as it goes live. If you write the cluster posts first with no hub, they float — related in your head but not connected on the site, which is the part search engines and AI answer systems actually read. That said, the pillar doesn't need every cluster post to exist on day one. Publish it with links to the two or three sub-pages you've written, and add links as the rest ship. A pillar that grows its internal links over a quarter looks exactly like a resource that's being actively maintained, which is the signal you want.

How long should a pillar page be compared to a post?

A pillar typically runs 2,000-4,000 words because it has to cover a broad subject at the overview level and hand off to sub-pages, while a normal post lands at 800-1,500 words because it answers one question completely and stops. But length is an output of scope, not a target you set. Don't decide "this will be a 3,000-word pillar" and then stretch a thin topic to fit. Decide the scope first using the scoring test, write until the subject is genuinely covered, and let the word count fall where it falls. A padded pillar reads worse than a tight post and performs worse too, because readers bounce off the filler and the page's core answer gets buried.

Common ways this goes wrong

A few patterns to watch for:

• The vanity pillar. A topic that matters to the founder's identity but not to buyers. Score it honestly on commercial relevance and buyer decision weight before committing.
• The premature pillar. Building the hub before you can support it with even two cluster posts. Ship the pillar plus a couple of sub-pages together, not the pillar alone.
• The orphaned cluster. Writing five related posts with no pillar tying them together. They compete with each other and none of them signals authority.
• The frozen pillar. Publishing once and never adding links or updating. A pillar is a living page; it should gain internal links and refreshes as your coverage grows.

If you're running a structured program where question mapping and interlinking are handled for you — the kind of setup ClearPath Content builds — the pillar-versus-post decision gets made against the whole map rather than one topic at a time, which is where it belongs.

The takeaway

Before you write anything, list the sub-topics and run the five-factor score. Eight or above, build the pillar and plan the cluster. Five to seven, write the best single post you can and let it prove demand before you expand. Four or below, write the post and move on. The discipline isn't in building more pillars — it's in refusing to build them for topics that only need a good, honest answer and a link home.