Topic clusters for a service business blog: a blueprint
Short answer: A topic cluster is one main "hub" page covering a service or subject broadly, linked to and from a set of narrower supporting posts that each answer one specific question. For a service business, the hub is usually the service page itself or a guide next to it. The point isn't a magic SEO structure; it's that clear internal links and one page per question make your site easier for people and search engines to follow, and stop several posts competing for the same search.
Service business blogs tend to grow one post at a time, in whatever order ideas arrive. After a couple of years there are dozens of loosely related articles, several of them answering the same question, none linked to the service page that pays the bills. Here's a blueprint for reorganizing that into clusters.
The idea in one paragraph
"Topic cluster" and "pillar page" are marketing terms, not Google terminology. What Google's documentation does say is relevant, though. Its guide to links notes that every page you care about should have a link from at least one other page on your site, and that paying attention to the anchor text of internal links helps both people and Google make sense of your site and find other pages. Its guidance on helpful content asks whether a page provides a substantial, complete description of a topic and whether it leaves visitors feeling they've learned enough to achieve their goal. A cluster is a practical way to meet both.
Blueprint: the hub page
The hub is the page you most want to rank and convert. For a plumbing company it might be the water heater service page; for an accountant, a page about bookkeeping for contractors; for a landscaper, a guide to backyard drainage.
What it contains:
- A clear statement of what you do and for whom, near the top.
- An overview of the subject, covering the main questions briefly rather than exhaustively.
- A section for each subtopic, two or three paragraphs each, with a link to the detailed supporting post.
- Proof and specifics: service area, process, what customers can expect, real photos of your work.
- One clear next step: a quote form, booking link or phone number.
What it avoids:
- Repeating every detail of the supporting posts. Summarize and link.
- Generic text that could sit on any competitor's site.
Blueprint: supporting posts
Each supporting post answers one specific question a customer actually asks. For the water heater example (hypothetical):
- How to tell when a water heater needs replacing
- Tank vs tankless for a family of four
- What to do if your water heater is leaking
- How long a water heater installation takes
Each supporting post should:
- Answer its question directly near the top.
- Link back to the hub with descriptive anchor text (for example, "our water heater installation service", not "click here").
- Link sideways to one or two closely related posts where it genuinely helps the reader.
- Stay focused. If a post starts answering a second big question, that question probably deserves its own post.
Blueprint: the link map
Sketch the cluster before writing or rewriting anything:
Hub: Water heater service
├─ Signs you need a replacement (links back to hub)
├─ Tank vs tankless (links to hub + "installation time")
├─ Leaking water heater steps (links to hub + emergency contact)
└─ Installation timeline (links to hub + "tank vs tankless")
Rules of thumb:
- Every supporting post links to the hub.
- The hub links to every supporting post.
- Sideways links only when relevant.
- Navigation or a "related guides" block can reinforce the structure, but in-text links with descriptive anchors carry the clearest meaning.
Google's links guide adds a technical point worth checking: Google can generally only crawl links that are <a> elements with an href attribute. Links built only with JavaScript click handlers may not be followed.
Reorganizing an existing blog
- Export a list of all posts with their titles and URLs.
- Group them by service or subject. Most service businesses end up with three to six natural clusters.
- Find duplicates. Where two or three posts answer the same question, merge them into the strongest one and redirect the others to it.
- Find gaps. List the questions customers ask on the phone or by email that no post answers.
- Choose or create the hub for each cluster. Often an existing service page can be expanded.
- Add the links described above, updating old posts as you go.
- Retire what doesn't fit. Posts unrelated to anything you sell or know about may not be worth keeping; update, merge or remove them.
Measuring whether it helped
- In Search Console, watch impressions and clicks for the hub and its supporting posts over several months.
- Check whether visitors move from supporting posts to the hub and then to your contact page, using your analytics' path or page reports.
- Note fewer cases where two of your pages appear for the same search, which suggests less internal competition.
Expect gradual change rather than a jump; search engines need to recrawl the pages and links.
Mistakes to avoid
- Writing supporting posts for keywords nobody asks about. Start from real customer questions.
- Thin posts created to fill a diagram. A short post is fine if it fully answers the question; a padded one isn't.
- Forgetting the conversion step. The hub should make it easy to get in touch.
- Linking everything to everything. Relevance beats volume.
FAQ
How many supporting posts does a cluster need?
As many as there are distinct questions worth answering. For a small service business, four to eight per cluster is common; quality matters more than count.
Should the hub be a blog post or a service page?
For most service businesses, the service page works best as the hub because it's where visitors convert. A separate guide can work if the service page needs to stay short.
Will topic clusters help my rankings?
They help organization, internal linking and coverage, which support how people and search engines understand your site. Google doesn't promise rankings for any structure.
What about old posts that don't fit any cluster?
Update them if they're still useful, merge them into a related post if they overlap, or remove them if they're outdated and attract no visitors.
Blog full of posts that don't lead anywhere? Send us your post list and we'll sketch the clusters with you.