Writing guide
How to write a pillar page
A pillar page holds a strange position: it is the most-linked, most-visible page in a content strategy, and the least understood. Ask five marketers what one is and you get five answers — an ultimate guide, a long post, a table of contents, a landing page for a keyword. Structurally it is none of those. It is a hub: the page that owns a broad topic at survey depth and routes readers and authority to the narrower pages that go deep.
The two failure modes are opposites. The first is the hollow pillar — 800 words of introduction wrapped around a list of links, which ranks for nothing because it answers nothing. The second is the monolith — 8,000 words that answer every sub-question in full, leaving the cluster pages nothing to rank for and competing against its own children for the same queries. A working pillar sits deliberately between: complete in coverage, shallow on purpose, generous with links.
The reward for building it right is structural, not cosmetic. One pillar plus ten spokes, interlinked in both directions, concentrates internal authority in a way twenty disconnected posts never do — and hands search engines and AI answer engines a machine-readable map of what your site actually knows. The plan below covers the mapping, the writing and the maintenance, in that order, because the mapping is where pillars are won.
What it is
A pillar page is a hub page covering a broad topic at survey depth — typically 2,000 to 4,000 words — that links out to a cluster of 8 to 15 narrower articles and receives a link back from each. The pillar targets the topic’s head term while the cluster pages target its long-tail questions, and the two-way linking concentrates the authority.
When to use it
Build a pillar when a commercially important topic decomposes into at least eight sub-questions you can genuinely cover, and when you can commit to publishing the cluster — a hub with three dead spokes is just a thin page with links. Do not build one for a single question (that is a blog post), for a topic your business has no standing in, or as the first thing on a new blog: pillars organize content that exists or is scheduled, they do not conjure authority from a sitemap.
The structure that works
A definition-anchored opening
The head term must be defined inside the first 100 words, in a self-contained block. That block is what featured snippets and AI answers lift — and it instantly confirms to readers that they found the canonical page.
- Write the definition in 40 to 60 words that survive being quoted alone, with the term itself in the first sentence.
- Follow it with a one-paragraph statement of scope: the sub-topics this page covers and routes to.
- No warm-up above the definition; on a pillar, the definition is the hook.
Chapter H2s that mirror the cluster map
Each H2 is a chapter: one sub-topic, surveyed in 150 to 300 words, then routed to its spoke. The H2 set read alone should form a complete outline of the topic.
- One H2 per cluster page, ordered the way a newcomer needs them.
- Open every chapter with its direct answer, then one proof, then the deeper link.
- A chapter swelling past 300 words is a spoke trying to be born — cut it back and move the depth out.
Cluster links out — and back
The linking is the mechanism, not a garnish. The pillar links to every spoke; every spoke links back with a head-term anchor; that closed loop is what consolidates topical authority.
- Use descriptive anchors (“how to segment an email list”), never “click here” or a bare URL.
- Place the spoke-to-pillar link in the spoke’s first screen, where it also orients lost readers.
- Audit quarterly for orphans: a published spoke with no pillar link is invisible to the structure.
Navigation built for reference readers
Nobody reads a pillar top to bottom. Visitors land from search, jump to one chapter, and leave or go deeper — so the page must work when entered at any H2.
- Put a linked table of contents above the first chapter; make it sticky on long pillars.
- Write each chapter self-contained — no “as we saw above” dependencies.
- Repeat the primary CTA once mid-page and once at the end; a single bottom CTA assumes a reader who reached the bottom.
A visible maintenance block
A pillar is a standing asset competing on freshness against every new page on the topic. Its decay is measurable — and so is the credit for upkeep.
- Show a last-updated date and keep it honest: bump it for real changes, not typo fixes.
- Keep a short changelog of substantive updates; readers and crawlers both read consistency signals.
- Review quarterly — refresh statistics, add chapters for new spokes, prune sections whose queries died.
Step by step
- 01
Map the cluster in a spreadsheet before writing anything
List every sub-question the topic contains, then consolidate to 8 to 15 cluster pages, each with its own primary query and intent. The working spreadsheet has five columns: sub-topic, target query, intent, spoke URL or planned date, and status. This document is the pillar — the page you eventually write is a rendering of it.
Assign the head term to the pillar and check for collisions: no spoke may target the pillar’s query, and no two spokes may target the same one. Most “pillar cannibalization” cases are mapping failures — two rows aimed at one query — caught here in minutes or in the rankings six months later.
- 02
Set the depth contract: survey here, full answer in the spokes
Decide what depth means before drafting: the pillar answers each chapter’s question at the level a smart newcomer needs — the what, the why, the one number to remember — and the spoke carries the how, the edge cases, the walkthrough. Write the contract down; it is the fence that keeps the monolith out.
Enforce it with the 300-word rule: any chapter past 300 words is annexing its spoke’s territory. Cut it back to the survey and move the surplus into the spoke draft — the surplus is usually the spoke’s best material.
- 03
Write the snippet-ready definition block first
Before any chapter, write the 40-to-60-word definition of the head term: the term in the first sentence, no pronouns leaning on earlier text, quotable in isolation. That exact shape is what featured snippets and AI answer engines lift, and on competitive head terms the lifted block is most of the visibility you will get.
Test it by deletion: read the definition with the rest of the page hidden. If it needs anything above or below it to make sense, rewrite until it stands alone.
- 04
Draft chapters that each earn their link
Write every H2 section to a fixed rhythm: the direct answer in the first sentence, one proof — a number, a named example — in the middle, and the routing link at the end with a descriptive anchor: “Full guide: how to segment an email list.” A chapter that is only a link teaches nothing and ranks for nothing; a chapter that teaches everything starves its spoke.
Aim the whole pillar at 2,000 to 4,000 words: ten chapters at 150 to 300 words plus the opening and close lands there naturally. If the total balloons past that, the depth contract is being violated somewhere — find the chapter that grew.
- 05
Wire the links in both directions on publish day
From the pillar, link every live spoke from its chapter. From every spoke, link back to the pillar within the first screen, anchored on the head term — and where it serves the reader, link the adjacent sibling spoke too. The structure only closes when both directions exist; out-links alone leak authority instead of cycling it.
Work through the spreadsheet as a checklist on publish day, then re-audit quarterly. Every content team eventually ships an orphan — a spoke published in a hurry with no pillar edit — and orphaned pages take months longer to rank than connected ones.
- 06
Add the table of contents and design for mid-page landings
Build a linked table of contents from the H2s and place it above the first chapter — sticky on desktop if the page runs long. Searchers arrive at specific chapters through jump links and deep anchors; the TOC is their map, and its anchor text doubles as an on-page summary for crawlers.
Then reread each chapter as if it were the reader’s entry point, because for some slice of traffic it is. Kill every “as mentioned above”; restate the noun instead of pointing at it. Place the primary CTA twice — mid-page and end — so the reader who leaves after one chapter still saw one.
- 07
Publish in the right order, then hold the cadence
Launch with the pillar plus at least 3 to 5 finished spokes, then ship the remainder on a steady schedule — one or two a month sustains the structure. Publishing a hub whose chapters all end in “coming soon” burns the first crawl and the first impression on your emptiest version.
Put the quarterly review on the calendar now: refresh every dated statistic, add chapters for new spokes, prune chapters whose queries died, and bump the visible updated date only for substantive changes. A pillar left alone for 18 months quietly loses to a worse page updated in March — maintenance is where most pillars are actually beaten.
Before and after: what good looks like
Before
Email marketing is one of the most effective digital marketing channels available today, offering incredible ROI for businesses of all sizes. In this ultimate guide, we will cover everything you need to know about email marketing. First, we will discuss what email marketing is and why it matters. Then we will explore how to build your list, the different types of campaigns, best practices for deliverability, and much more. Whether you are a beginner or an expert, this guide has something for you. So let us dive in.
After
Email marketing is the practice of sending commercial messages to a list of people who gave you permission to contact them — used for retention, conversion and repeat revenue, and returning roughly 36 dollars per dollar spent in industry benchmarks. This guide surveys the seven decisions that determine whether it pays: building a list you own, choosing segments, writing campaigns people open, automating the sequences that run without you, staying deliverable, measuring what matters, and picking tools. Each chapter gives the working answer in about 200 words, one benchmark to steer by, and a link to the full guide — start at the chapter you need; each stands alone.
The before spends 86 words promising to cover things; the after spends 107 actually covering them. The rewrite opens with a 39-word definition a snippet could lift whole, replaces “everything you need to know” with a countable scope — seven named decisions that preview the seven chapter H2s — and states the reading contract: survey here, depth one link away. “Ultimate guide” energy is exactly what got cut; a pillar earns the word canonical through structure, not adjectives.
Mistakes that sink a pillar page
| Mistake | The fix |
|---|---|
| The hollow pillar — an introduction wrapped around a list of links | Make every chapter answer its question at survey depth before it routes onward: direct answer, one proof, then the link. A page that only points teaches nothing and ranks for nothing. |
| The monolith that answers every sub-question in full | Enforce the 300-word chapter rule and move surplus depth into the spokes. A pillar that fully answers a sub-question competes with its own cluster page for that query. |
| Pillar and spoke targeting the same query | Keep a one-query-per-URL map in the cluster spreadsheet and check it before any page is drafted. Cannibalization is a mapping error that surfaces six months later as two pages ranking 8th and 9th. |
| Links out with no links back | Add the spoke-to-pillar link, head-term anchored, in every spoke’s first screen. One-way linking leaks authority; the closed loop is the entire mechanism. |
| Launching the hub before the spokes exist | Ship the pillar with 3 to 5 finished cluster pages and a schedule for the rest. Chapters ending in dead ends waste the launch crawl on your weakest version. |
| Publishing once and never returning | Calendar a quarterly review: refresh statistics, add new chapters, prune dead ones, and update the visible date for substantive changes only. Pillars lose to fresher pages far more often than to better ones. |
Pre-publish checklist
- The cluster map exists as a spreadsheet: 8 to 15 spokes, one distinct query each, none colliding with the head term.
- The head term is defined in the first 100 words, in a 40-to-60-word block that reads standalone.
- Each H2 covers exactly one cluster sub-topic, and the H2 list alone outlines the whole topic.
- Every chapter opens with its direct answer and carries at least one number or named example.
- No chapter exceeds 300 words, and the total sits between 2,000 and 4,000.
- Every live spoke is linked from its chapter with a descriptive anchor.
- Every spoke links back to the pillar on a head-term anchor within its first screen.
- A linked table of contents sits above the first chapter.
- No chapter depends on “as mentioned above” — each survives a mid-page landing.
- At least 3 to 5 spokes are live on launch day, with a publish schedule for the rest.
- A quarterly review is on the calendar, and the page shows an honest last-updated date.
Free tools for this work
Check your pillar page before it ships.
Frequently asked questions
- How long should a pillar page be?
- 2,000 to 4,000 words for most topics — enough for 8 to 15 chapters at 150 to 300 words plus the opening. Length is an output of the cluster map, not a target: a pillar past 5,000 words is usually hoarding depth that belongs in its spokes.
- How many cluster pages does a pillar need?
- 8 to 15 at maturity, with 3 to 5 live on launch day. Fewer than 8 sub-questions means the topic is probably a single long article; far more than 15 usually means the topic should split into two pillars.
- What is the difference between a pillar page and a blog post?
- Scope and role. A blog post answers one question completely and can live alone; a pillar surveys a whole topic at 150 to 300 words per sub-question and exists to route readers and authority to 8 to 15 deeper pages. If it has no cluster to route to, it is not a pillar — it is a long post.
- How often should a pillar page be updated?
- Review quarterly and make a substantive update at least every 6 months: refreshed statistics, chapters for new spokes, pruned dead sections. Pillars target head terms where freshness is contested; 18 months of neglect routinely costs positions that a rewrite then takes months to win back.
Free download
The Pre-Publish Checklist
This guide covers one format. The checklist covers every article. 47 checks WriteZu runs before an article ships — as a checklist you can run by hand.
No spam. The checklist, then only what's worth knowing.
Or let WriteZu handle the writing for you
It follows this exact structure — researched, drafted, scored against quality gates, and published to your CMS — while you approve from your inbox.
Start free