← Journal

Guides

Topic clusters and pillar pages: how to plan a blog around them

By Thomas Lovas Lokoy · Published 16 October 2026 · 7 min read

Classical stone columns against a blue sky
Photo: Untitled · CC0

Topic clusters are a way of planning a blog so that related posts are written as a set rather than one at a time. A pillar page gives a broad overview of a subject; cluster posts each cover one part of it in depth; and links run between them in both directions. This guide explains where the idea comes from, what Google's documentation does and does not say that bears on it, and how to plan a cluster for your own blog in a few practical steps.

Topic clusters are a convention, not a Google term

It is worth being straight about this at the start. "Topic cluster" and "pillar page" are terms from content marketing practice. They do not appear as ranking concepts in Google Search Central's documentation, and Google has not published a rule saying that a blog organised this way will rank better. If you read a claim that clusters are "what Google wants", treat it as somebody's interpretation.

What the model does is put several things Google's guidance does recommend into one planning habit:

  • A site with a clear focus. Google's helpful content page asks: "Does your site have a primary purpose or focus?"
  • Content that leaves the reader satisfied. The same page asks: "After reading your content, will someone leave feeling they've learned enough about a topic to help achieve their goal?"
  • Contextual internal links. The link best practices page says: "Every page you care about should have a link from at least one other page on your site."
  • No needless duplication. The SEO starter guide notes that duplicate content is not a spam violation, "but it can be a bad user experience".

Seen that way, a cluster is less a technique for search engines than a discipline for writers: decide the subject, decide the parts, write each part once, and connect them.

What a pillar page is, and what it is not

A pillar page covers a broad subject at the level a newcomer needs. It answers "what is this and what are its parts?" and sends readers to separate posts for each part. A pillar on email newsletters might explain the whole process in a page and link out to posts on choosing a platform, growing a list, writing subject lines and measuring results.

A pillar is not:

  • A very long post that tries to cover everything. Google's helpful content page asks whether you are "writing to a particular word count because you've heard or read that Google has a preferred word count?" and answers its own question: "(No, we don't.)" Length should follow the job, and the pillar's job is orientation.
  • A list of links. It needs enough substance on each part that a reader who never clicks through still understands the subject.
  • A category archive. An archive is generated by date or tag. A pillar is written, and its order follows the logic of the subject.

How to plan a cluster

1. Choose a subject your blog can genuinely cover

Start with something you, or the business you write for, know first-hand. Google's helpful content guidance lists, among its warning signs, writing about things "simply because they seem trending" rather than for an existing audience. A cluster is a commitment to perhaps eight to fifteen posts on one subject. If you cannot imagine writing the fifth one from real knowledge, choose a narrower subject.

2. List the questions a reader asks, in order

Write down what someone new to the subject needs to know, from the first question to the last. Do not start from keyword tools. Start from the questions you hear from customers, in comments and in your own early confusion, then check them against the results page. The guide on keyword research without search volumes explains how to read the results page directly for the phrasing people use.

3. Group the questions into posts

Each cluster post should answer one main question and its close follow-ups. The test is the reader: would someone searching this question be satisfied by the post, or would they need to read two posts to get one answer? If two questions always come together, they belong in one post. If one post would need to answer two quite different questions, split it.

This step is where you prevent the most common cluster failure: several posts competing to answer the same question. The SEO starter guide's advice for duplicate pages is to consider a redirect "from non-preferred URLs to a URL that best represents that information". It is cheaper to avoid writing the duplicate in the first place.

4. Map the funnel position of each post

Some questions come from people learning the basics; others from people comparing options or ready to act. Note which is which. The guide to content funnel stages for blog articles covers how to read a reader's stage from their search. A cluster usually needs mostly early-stage posts, a few comparison posts and a small number of decision posts.

5. Write the pillar outline last

Once you know the cluster posts, the pillar outline almost writes itself: one section per post, in the order a reader would need them, each with a short summary and a link. Writing the pillar first tends to produce a page full of promises the cluster does not yet keep.

6. Decide the URL structure, but do not overthink it

Google's starter guide recommends grouping topically similar pages in directories, and explains that this can help Google learn how often URLs in each directory change. It also says this matters mainly for large sites, of more than a few thousand URLs. For most blogs a flat structure such as /blog/post-name is fine; what matters more is that each URL contains words that describe the page. The starter guide puts that as: "Try to include words in the URL that may be useful for users".

How to link a cluster together

The linking pattern is simple:

  1. The pillar links to every cluster post, in context, in the section that summarises it.
  2. Every cluster post links back to the pillar, usually early, where it mentions the broader subject.
  3. Cluster posts link to each other where the reader would naturally move on. A post on subject lines might link to the post on measuring open rates. Not every post needs to link to every other.

Use descriptive link text. Google's guidance is that good anchor text is "descriptive, reasonably concise, and relevant to the page that it's on and to the page it links to". The guide to internal linking for blogs covers anchor text and a full routine for auditing links.

Building a cluster from posts you already have

You do not need to start from scratch. Most established blogs have the raw material for two or three clusters already.

  1. Export your posts and sort them by subject.
  2. For each subject with five or more posts, list the main question each post answers.
  3. Look for overlaps. Where two posts answer the same question, merge the better material into one, then redirect the other to it. Google's redirects documentation recommends a permanent server-side redirect when you are sure the move will not be reverted.
  4. Look for gaps. The missing questions are your next cluster posts.
  5. Write or rewrite the pillar, then add the links in both directions.

The companion guide on updating old blog posts covers how to rework the existing posts without breaking what already works.

Mistakes to avoid

  • Producing clusters at scale. Google's helpful content page asks: "Are you using extensive automation to produce content on many topics?" Twenty thin cluster posts generated in an afternoon are the opposite of what the model is for. If you use a writing tool for drafts, brief each post separately and check each one; the guide to briefing an AI writing tool covers the brief.
  • Forcing links. A link from a post about subject lines to a post about GDPR consent may be technically in the same cluster and still useless at that point in the text.
  • Treating the cluster as finished. Subjects change. Plan to review the pillar and its posts on a schedule, as the starter guide suggests: "Check in on previously published content and update it as needed, or even delete it if it's not relevant anymore."
  • Expecting quick results. The starter guide says that some changes take effect in a few hours and others take several months, and suggests waiting a few weeks before judging whether a change helped.

A one-page cluster plan

Before writing, you should be able to fill in this outline:

  1. Subject: one line.
  2. Who it is for: one line.
  3. Pillar question: the broad question the pillar answers.
  4. Cluster posts: one main question per post, with its funnel stage.
  5. Links: which cluster posts link to which, beyond the pillar.
  6. Review date: when you will next check the whole set.

If you cannot fill in the first two lines, the cluster is not ready to write.

Sources