How do topic clusters and pillar pages work in SEO?
Topic clusters work by organizing content the way a buyer researches a subject. A pillar page covers the main question broadly and in depth. Cluster articles each answer one specific sub-question in more detail. Every cluster article links to the pillar, the pillar links to every cluster article, and related cluster articles link to each other. The result is a tightly connected group that signals depth on one subject.
The model is often called hub and spoke. It helps search engines understand which page is your main answer and which pages support it, so the right page ranks for the right query. It helps readers move from a broad question to the specific one they care about. And it helps AI assistants, which expand a single question into several searches and can find more of your pages when they're connected. For how clusters fit into a pipeline-first plan, start with our B2B content strategy hub.
Element | Job | Example for a scheduling startup |
|---|---|---|
Pillar page | Answers the broad question in depth and links to every cluster article | Sales meeting scheduling: the complete guide |
Cluster article | Answers one sub-question in detail and links back to the pillar | How to reduce no-shows for sales demos |
Money page | Where the cluster sends ready buyers | Product page for sales teams, pricing |
Internal links | Connect all three in both directions | Contextual links in the first sections |
What is the difference between a pillar page and a regular article?
A pillar page is broader and more connected than a regular article. It covers every major sub-topic of a subject at summary depth and links out to a detailed article for each one, while a regular article goes deep on one question. A pillar is usually longer, updated more often, and treated as a permanent page rather than a dated post.
Pros
- Gives search engines and assistants one clear main page for the subject
- Collects internal links, which concentrates authority on the page that matters
- Works as a navigation page for readers, guiding them to the detail they want
- Easy to refresh, because new sub-topics become new cluster articles
Cons
- Takes more effort to write and keep current than a single post
- Can overlap with cluster articles if scopes aren't defined clearly
- Fails if cluster articles are never written, leaving a pillar full of dead ends
Some teams make the pillar a product or use-case page rather than a blog post. That can work well for B2B, because the page that ranks for the broad question is then also the page that converts. The trade-off is that a product page has less room for neutral explanation. Our guide to pillar pages in site architecture covers when to make that choice.
How do you plan a topic cluster before writing anything?
Plan a cluster by choosing one subject your buyers research before buying, listing every sub-question they ask, and deciding which page answers each one. The plan should end with a list of URLs, titles and links, not just a list of keywords.
Choose the subject from your sales calls
Pick a problem your product solves that buyers research before they talk to you. One cluster per core problem or use case.
List the sub-questions
Collect questions from sales calls, support tickets, keyword tools and your own AI prompt audits. Group duplicates.
Assign one page per question
Each cluster article answers one distinct question. If two questions have the same answer, they share a page. This prevents pages competing with each other.
Decide the pillar scope
The pillar summarizes every sub-question in a few paragraphs and links to the full answer. Write its outline first.
Map the links
For each page, list the pillar link, two or three related cluster links and the money page link. Put it in the brief.
Set the URLs
Decide the URL pattern before anything is published, so you never have to redirect a live cluster.
Brief and publish in order
Publish the pillar and the most commercially important cluster articles first, then fill in the rest.
How many articles a cluster needs before it earns authority is a common question, and the honest answer depends on the subject; see topical authority for startups. For the brief format, our content brief template includes a links section for exactly this.
What URL structure should topic clusters use?
Use a URL structure that is simple, permanent and doesn't need to change if you reorganize topics. For most marketing sites, a flat blog structure with the topic stored as a CMS field works better than nesting articles under topic folders in the URL.
Pattern | Example | Pros | Cons |
|---|---|---|---|
Flat with topic field | /blog/reduce-demo-no-shows | Never breaks if topics change; simple | Topic isn't visible in the URL |
Topic folder | /blog/scheduling/reduce-demo-no-shows | Topic visible; clear grouping | Moving an article means a redirect |
Pillar as top-level page | /sales-scheduling with articles under /blog | Pillar can double as a money page | Two templates to maintain |
Whichever you pick, add a topic hub page that lists every article in the cluster, and breadcrumbs that show the relationship. Search engines understand the cluster from links and content, not from URL folders, so don't restructure live URLs just to add a folder. If you're migrating platforms anyway, that's the moment to set the structure; the redirect side is covered in our Webflow to Framer migration guide.
How do you set up topic clusters in a CMS?
Set up clusters in a CMS with a topic field on every article, a reference from each article to its pillar, and templates that generate the links automatically. The aim is that publishing a new cluster article updates the pillar's list and the related-posts section without anyone editing other pages by hand.
- Topics collection: one item per cluster, with a name, a description and a reference to the pillar page.
- Article fields: a single reference to its topic, an optional reference to the pillar, and a multi-reference for related articles you choose by hand.
- Pillar template: automatically lists every article whose topic matches, so the pillar never goes stale.
- Article template: a breadcrumb to the topic, an automatic link to the pillar near the top, and a related-posts block filtered by topic.
- Author and updated date: visible on every page. Named authorship helps trust; see author pages and E-E-A-T.
Webflow, Framer and headless CMSs used with Next.js all support collections and references, though the details differ. A headless CMS with Next.js gives the most control over automatic linking and rendering. Check each platform's current documentation for collection and field limits before committing, because those change.
A minimal field setup you can copy
Topics collection: Name (text), Slug (text), Summary (text), Pillar (reference to Articles or Pages), Money page (link).
Articles collection: Title, Slug, Excerpt, Body, Topic (reference to Topics), Is pillar (yes or no), Related articles (multi-reference to Articles), Author (reference to Authors), Updated date.
Template rules: on an article, show a breadcrumb Blog, then Topic, then Title; insert a sentence linking to the topic's pillar in the intro; show three related articles, hand-picked first and then filled by same-topic articles. On a pillar, list every article with the same topic, grouped by sub-theme if you add a sub-theme field. Every article in the topic also gets a link to the topic's money page in its closing section.
How should internal links work inside a topic cluster?
Internal links inside a cluster should go both ways between the pillar and every article, sideways between closely related articles, and out from the cluster to the money page it supports. Use descriptive anchor text that says what the target page answers, and place the most important links early in the content, not only in a footer list.
- Every cluster article links to the pillar in its first two sections.
- The pillar links to every cluster article, in context where the sub-topic is summarized.
- Each article links to two or three closely related articles in the same cluster.
- Each article links to the relevant money page where the reader would naturally consider buying.
- Anchor text describes the target, such as "how to reduce demo no-shows", never "read more".
- Review links quarterly, because new articles need to be added to older ones too.
These links also matter for AI search. Assistants expand one question into several searches, a pattern called query fan-out, and a well-linked cluster gives them more of your pages to find for those sub-questions. Query fan-out explained shows how that works.
How do you keep a topic cluster current?
Keep a cluster current by refreshing the pillar on a schedule, adding new cluster articles when buyers start asking new questions, and updating links whenever something new is published. AirOps found more than 70% of pages cited by AI engines had been updated within the past 12 months, and Ahrefs reported AI-cited content is about 26% fresher than average, so stale clusters lose ground.
Review the pillar at least quarterly, check that every cluster article still answers its question correctly, and add a cluster article whenever a new question shows up repeatedly on sales calls. A good way to strengthen a cluster further is one piece of original data, such as a benchmark or survey, that others will cite; see original data and stats pages. The refresh schedule itself is covered in content freshness for AI search.
