How to Write a Pillar Page Outline for a Service Business: A Practical Guide
A pillar page outline for a service business is a plan for one page that covers a core service topic in full, with linked cluster posts covering each subtopic in depth. Done well, it gives your site a structure that readers can navigate and search engines can understand, instead of a pile of disconnected posts competing with each other.
TL;DR / Key Takeaways
- A pillar page covers a broad service topic completely at overview level; cluster posts cover each subtopic in depth and link back to the pillar.
- Start the outline from your core service, not from a keyword list: the pillar should match a service you actually sell.
- Map the reader's journey first, then assign each stage to the pillar or to a cluster post, so nothing is covered twice and nothing is missed.
- Every cluster post links to the pillar, the pillar links to every cluster post, and cluster posts link to each other where genuinely relevant.
- Write the pillar outline before writing any of the posts, because restructuring after publishing is far more work than planning before drafting.
- A pillar page is a living page: review it when you add cluster posts, and refresh it when your services, prices, or processes change.
What a Pillar Page Is, and What It Is Not
A pillar page is a single, substantial page that covers a broad topic comprehensively but at overview level. It answers the main questions about the topic, explains the key concepts, and points readers to more detailed pages for each subtopic. Those detailed pages are the cluster: a set of posts or pages, each focused on one subtopic, each linking back to the pillar, and each linked from the pillar. Together, the pillar and its cluster form a topic cluster, a structure that organises a site around subjects rather than around isolated keywords.
For a service business, the natural pillar topics are your core services. A plumbing business might build a pillar page on bathroom renovation, with cluster posts on costs, timelines, materials, planning permission, and common problems. A wedding photographer might build a pillar on wedding photography, with clusters on pricing, timelines, venues, styles, and what happens in bad weather. The pillar matches a service the business sells, which keeps the whole structure honest: every cluster post exists because a real customer question or a real stage of the buying journey needs it.
A pillar page is not a long blog post with a few links added afterwards, and it is not a sitemap page or a category index. A category index lists posts; a pillar page explains the topic. A reader who lands on a pillar page should leave understanding the topic at overview level and knowing exactly which detailed page to read next for their specific question. If the page only lists links, it is an index. If it only explains without linking onwards, it is a standalone article. The pillar does both jobs: it teaches and it routes.
A pillar page is also not a shortcut to authority. Topical authority is built by covering a topic thoroughly across many pages over time, not by publishing one long page and declaring the topic covered. The pillar is the organising structure for that coverage, and its value grows as the cluster fills in. A pillar with three cluster posts is a start; a pillar with a complete cluster is a resource.
Why the Outline Comes Before the Writing
Writing a pillar page without an outline usually produces one of two failures. Either the pillar tries to cover everything in depth and becomes an unreadable wall of text, or it covers everything shallowly and duplicates the cluster posts it was supposed to organise. The outline prevents both failures by deciding, before any prose exists, what belongs on the pillar and what belongs in each cluster post.
The outline also prevents the most expensive content mistake for a service business: keyword cannibalisation in plain language, where several of your own pages compete to answer the same question and none of them answers it completely. Google's SEO Starter Guide advises organising a site in a logical way so that search engines and users can understand how pages relate to each other, and grouping topically similar pages together. A pillar outline is that advice applied to content planning: it states the relationships between pages before they are written, so each page has a distinct job.
There is a practical benefit too. An outline lets you publish in stages. You can publish the pillar first with its overview sections and a few completed clusters, then add cluster posts over the following weeks, linking each one into the pillar as it goes live. Without an outline, staged publishing produces gaps and dead links; with one, each new post slots into a known place. For a busy service business, that staged approach is often the only realistic way a pillar gets built at all.
How to Build the Outline, Step by Step
Step 1: Pick one pillar topic tied to one core service
Choose a topic that is broad enough to need several subtopics, narrow enough to belong to one service, and commercial enough to matter to your business. A good test: can you name five to ten genuine subtopics without stretching? If you can name only two, the topic is a blog post, not a pillar. If you can name thirty, it may be two pillars, and splitting it will keep each one focused. Write the pillar's promise in one sentence, naming the reader and the outcome: for example, "A homeowner planning a bathroom renovation will understand the process, costs, timeline, and decisions involved, and know which detailed guide to read next." That sentence governs every later decision about what belongs in the outline.
Step 2: List the reader's journey, stage by stage
Before listing subtopics, list the stages your customer passes through. A typical service journey runs from recognising the need, through researching options and costs, comparing providers, preparing for the work, the work itself, and aftercare. Write the questions a customer asks at each stage, drawing on your enquiry inbox and your own experience. This journey list becomes the spine of the outline, because it ensures the pillar serves buyers, not just browsers. It also reveals stages you might otherwise miss: aftercare questions, for example, are frequently asked and rarely covered, which makes them good cluster material.
Step 3: Turn the journey into sections and clusters
Now assign each stage to either the pillar or a cluster post. The pillar gets an overview section for each major stage: enough to answer the stage's main question and to introduce the cluster posts that go deeper. Each cluster post gets one subtopic, defined narrowly enough to answer completely. A bathroom renovation pillar, for instance, might carry overview sections on planning, cost, timeline, materials, and hiring, with cluster posts on each of those in depth, plus clusters on specific problems such as small bathrooms or period properties. Check the assignment for duplication: if two cluster posts would answer the same question, merge them; if a question has no home, add a cluster or fold it into the pillar's FAQ.
Step 4: Write the pillar's section outline
For each pillar section, write a heading, a one-sentence statement of what the section must cover, and the cluster posts it will link to. Keep each section at overview level: two to four short paragraphs, plus the links onwards. If a section grows beyond that, it is probably a cluster post in disguise, and it should be moved. The pillar's introduction should state the topic, the reader, and the outcome, and the pillar should end with a clear next step, such as contacting you, reading a specific cluster post, or checking a service page. The conclusion is also where the commercial purpose of the pillar can be stated plainly: this is a page about a service you sell, and the reader should be able to enquire without hunting for a contact link.
Step 5: Plan the internal links before writing
Internal linking is where many pillar projects fail, because links are added as an afterthought and end up inconsistent. In the outline, specify the links explicitly: every cluster post links to the pillar, the pillar links to every cluster post, and cluster posts link to each other only where the connection genuinely helps the reader. Also link the pillar to the relevant service page, and the service page back to the pillar, so the educational content and the commercial page reinforce each other. Google's SEO Starter Guide notes that links help search engines discover pages and help users navigate, and that good link text tells users and search engines what the linked page contains. Write the link text in the outline too, using descriptive phrases rather than generic wording.
Step 6: Add the supporting elements to the outline
A complete pillar outline also notes the supporting elements each page will need. For the pillar, that includes a descriptive title tag and meta description that state the topic and the outcome, a FAQ section covering the questions that do not fit any cluster, and structured data markup for the FAQ where appropriate, describing content actually visible on the page. For each cluster post, the outline should note its target question, its intended reader, and its place in the journey. These notes are brief, but they prevent the common drift where cluster posts slowly become generic and lose their connection to the pillar.
Step 7: Sequence the writing work
Order the cluster posts by value, not alphabetically. Start with the clusters that answer the questions customers ask most often, and the clusters closest to an enquiry, such as cost and process posts. Publish the pillar first with its overview sections complete, even if only a few clusters exist, and add the remaining clusters over time, updating the pillar's links as each one goes live. Keep a simple tracker: pillar sections, cluster titles, status, and links added. That tracker is what turns a pillar from a plan into a finished structure, because it makes the remaining work visible.
Step 8: Review the outline against the reader test
Before writing begins, read the outline as a stranger with the pillar's stated problem. Can you find the answer to each stage of your journey? Is any section trying to do a cluster post's job? Is any cluster post answering a question nobody asks? Does the pillar end with a clear next step? If the outline fails any of these checks, fix it now. Fixing an outline takes minutes; restructuring published pages takes hours, and it risks breaking links and losing whatever visibility the pages have gained.
Common Mistakes in Pillar Page Outlines
| Mistake | What goes wrong | Fix |
|---|---|---|
| Pillar topic too broad | Outline sprawls across several services | Split into one pillar per core service |
| Pillar covers everything in depth | Unreadable wall of text; cluster posts duplicate it | Pillar stays at overview level; depth lives in clusters |
| No journey mapping | Sections follow keywords, not buyers | Build the outline from the customer's stages |
| Links added afterwards | Inconsistent, missing, or generic links | Specify every link and its text in the outline |
| Cluster posts compete with each other | Several pages answer the same question | Assign each question to exactly one page |
| Pillar published and forgotten | New clusters never linked in; content goes stale | Update the pillar whenever a cluster goes live |
How This Looks on Rankenza
The typical manual way to build a pillar is to write a long post, publish it, and then try to retrofit cluster posts and links around it. That order guarantees rework, because the long post inevitably covers ground the cluster posts need, and the links end up pointing wherever is convenient rather than where the structure requires.
Rankenza's way starts from the outline's logic. Each article begins with research into the top ten results on the search results page for the target topic, so the pillar and its clusters are planned against what readers actually find for the topic. An intent filter checks that each topic matches what searchers are trying to do, which keeps informational clusters and commercial pages from blurring together. Drafts are reviewed by a human before they reach you, and internal links are drawn from your own site's sitemap, so the pillar's links point to pages that actually exist on your site. Your first article is free, then articles cost $3.60 each or $89 for 50, as listed on the Rankenza pricing page.
For a pillar project, the practical approach is to use that workflow post by post: start with the pillar outline you built using this guide, then commission the pillar and its highest-value clusters in sequence, enriching each draft with your own service details, prices, and process notes. The outline is your contribution and your quality control: it tells you whether each draft belongs where it was placed, and whether the cluster is filling in or drifting.
Long enough to cover the topic at overview level and route readers onwards, and no longer. That usually means substantially longer than a standard blog post, because the pillar must introduce every major stage of the topic, but each section stays brief precisely because the depth lives in the cluster posts. If your pillar draft keeps growing, check whether sections are doing cluster posts' jobs and move that depth out. Length follows the outline; the outline follows the reader's journey.
Enough to cover the topic's genuine subtopics, which for a service business is usually somewhere between a handful and a dozen. Start with the clusters that answer your most-asked customer questions and the questions closest to an enquiry, and add the rest over time. A pillar with a few strong clusters and a plan for the rest is better than a pillar with many thin clusters written to hit a number. See our guide to topical authority cluster plans for one niche for how to size a cluster.
It can be either, but it should be one or the other, clearly. Many service businesses publish the pillar as a comprehensive guide in their blog or resources section, and link it prominently from the relevant service page. What matters is that the pillar is easy to find, clearly about the topic, and ends with a path to enquiry. If the pillar lives in the blog, link to it from the service page; if it lives on the service page itself, keep the page's commercial purpose visible alongside the educational content.
Check three things over time. First, whether readers move between the pillar and the clusters, which your analytics can show. Second, whether the pillar and its clusters appear in search results for the topic and its subtopics, which Google Search Console can show, as explained in our guide on how to measure blog SEO results in Google Search Console. Third, whether enquirers mention the guides, which is the commercial test that matters most. A pillar that earns traffic but never an enquiry may need a clearer next step; a pillar that earns enquiries but little traffic may need more clusters covering the questions searchers actually ask.
Sources
- Google Search Central, "SEO Starter Guide: The Basics" — organising a site logically, grouping topically similar pages, and using descriptive link text: https://developers.google.com/search/docs/fundamentals/seo-starter-guide
- Google Search Central, "Creating Helpful, Reliable, People-First Content" — providing a substantial, complete description of a topic and satisfying the reader's goal: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- Google Search Central, "In-Depth Guide to How Google Search Works" — how pages are discovered through links and sitemaps, and how indexing and serving work: https://developers.google.com/search/docs/fundamentals/how-search-works
- Sitemaps.org, "Sitemaps XML format" — the sitemap protocol that lists the URLs search engines can discover on a site: https://www.sitemaps.org/protocol.html
Related reading on Rankenza: pillar pages and topic clusters explained, blog post outline template that ranks, and the SEO keyword generator for testing pillar and cluster topics.