A topic cluster is a set of pages on one subject: a pillar page that answers the broad question, and spoke pages that each answer one narrower question, joined by internal links. Search engines and AI answer engines use those links and answers to find your pages and pick a passage to quote.

This guide is part of the B2B creator-operator playbook, and its worked example is the cluster plan behind this site's own guides.

Key points

• A cluster has three parts: one pillar, 8 to 12 spokes, and fixed internal links between them.

• Google says no special files, markup or schema are needed for AI Overviews or AI Mode.

• Plan from target questions, not keywords. Each spoke answers one question a buyer asks.

• Every spoke links the pillar in its first 150 words, links two siblings, and bridges once to another cluster.

• Measure each spoke by whether it ranks and gets quoted for its own target question.

What is a topic cluster?

A topic cluster covers one subject from several angles, with a pillar page at the center. Semrush's topic cluster guide defines it as "a group of interconnected, thematically related pages on a website."

HubSpot's topic cluster guide describes the same shape: a broad pillar page linked to focused cluster pages, "with internal links from each cluster page back to its pillar and sometimes to the others." The model traces back to a 2015 research project called "Topics Over Keywords" by former HubSpotters Anum Hussain and Cambria Davies, which HubSpot says "became the foundation of the topic cluster model."

The three parts:

• Pillar. Answers the head question in full and links to every spoke.

• Spokes. Each answers one specific question and links back to the pillar.

• Internal links. Descriptive links that let readers and crawlers move through the whole subject.

CoSchedule's topic cluster guide puts it more simply: "A topic cluster is a group of interlinked web pages." The interlinking is what turns a set of posts into a cluster.

Why do topic clusters help both Google and AI answer engines?

Both lean on the same signals: pages that answer a question well, and links that show how those pages relate. A cluster builds both on purpose.

What Google says about links and structure

Google's guide to crawlable links says "Google uses links as a signal when determining the relevancy of pages and to find new pages to crawl." It also says "Every page you care about should have a link from at least one other page on your site."

A cluster makes that rule automatic: the pillar links to every spoke, so none is an orphan.

What Google says about AI Overviews and AI Mode

Google's page on AI features and your website is direct: "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary." It also says you do not need "new machine readable files, AI text files, or markup" to appear.

Its first listed best practice is "Making your content easily findable through internal links on your website." The page also describes "query fan-out," where these features issue "multiple related searches across subtopics and data sources." A cluster that covers the subtopics of one subject gives those searches more of your pages to find.

What Google says about helpful content

Google's helpful content guidance asks whether content shows "first-hand expertise and a depth of knowledge," and lists "producing lots of content on many different topics in hopes that some of it might perform well" as a warning sign. A cluster goes deep on a few subjects you know instead.

Before you map spokes, check which content motion the cluster serves. Not every motion fits every budget, audience and stage.

How do you pick a pillar and spokes from target questions?

Start with the business line the content supports, list the questions its buyers ask, and promote the broadest one to pillar. The rest become spokes.

The steps:

1. Pick one subject you can prove. Match it to something you sell or do, so the pages show first-hand expertise.

2. List 20 to 30 questions buyers ask. Pull them from sales calls, DMs, community threads and "People also ask."

3. Choose the pillar question. The broadest question every other one sits under.

4. Cut the list to 8 to 12 spokes. Merge questions that share an answer, or both pages will compete for the same query.

5. Give each spoke a link role. Definition, comparison, how-to, linkable asset or bridge.

6. Write the spokes first, then the pillar. The pillar can only link to pages that exist.

What are the internal link rules for a cluster?

Each page type has a fixed job, and the links follow from it. Write the rules down once so every new page follows them.

Anchor text

Google's link guidance says "Good anchor text is descriptive, reasonably concise, and relevant to the page that it's on," and suggests reading the anchor out of context to check that it still makes sense.

Never use "click here," and vary anchors to the same page by mixing the guide title and plain phrases.

Cross-cluster bridges

A bridge is one link from a spoke into a neighboring cluster. On this site, Content guides bridge to a Consulting or Career guide where the topics meet. Bridges show readers where the next subject starts.

What should each page in the cluster look like?

Use the same answer engine optimization (AEO) template on every page, so answer engines can lift a clean answer. Every guide on this site follows it.

1. The target question as the H1, in the words people type or ask.

2. An answer block of 40 to 60 words directly under the H1, with no lead-in. This is the passage most likely to be quoted.

3. A key points list of 3 to 5 bullets that each make sense alone.

4. Follow-up questions as H2s, each opening with a one or two sentence answer.

5. One structured element: a table, numbered steps or a checklist.

6. Citations to primary sources for every figure.

7. A FAQ section with 4 to 6 short questions.

8. A byline with a "Last updated" date and one call to action.

A note on FAQ markup. Google's FAQ structured data documentation says the FAQ rich result "will no longer appear in Google Search starting May 7, 2026." Keep the FAQ section for readers and answer engines, but do not expect a rich result.

The guide on getting cited by ChatGPT and Perplexity covers the citation side in more depth.

What does a real cluster plan look like?

Here is the Consulting cluster on this site. The business line is installing AI operating systems for B2B teams, so the pillar answers that head question.

The pillar is what an AI operating system for a B2B team is and how to install one. Its spokes each take one buyer question:

Two spokes show the link rules at work. The L1 to L4 AI automation maturity ladder is the linkable asset, so guest posts point at it instead of the homepage. The manual-work leak audit guide sits closest to the offer, so siblings link to it where readers ask "where do I start?"

Every cluster on this site follows the same plan, each with its own pillar and spokes.

How do you build a planning table for your own cluster?

Use one row per page and fill every column before anyone writes. An empty column means the page is not ready.

Keep slugs flat, such as /guides/{slug}, rather than nested under the cluster name. A page can then move clusters later without breaking its URL or its backlinks.

I run my own content from a planning table like this one, and I build the revenue side of the same idea for SaaS teams: lead routing, CRM cleanup and pipeline reporting, set up inside a 90-day AI RevOps Sprint for Series A and B companies. Contact me to get yours scoped.

How do you measure whether a cluster is working?

Measure each spoke against its own target question, in classic search and in AI answers.

What to track:

• Search Console queries per page. Check that each page's top queries match its target question. If not, fix the H1 or answer block.

• Impressions before clicks. A spoke with impressions and no clicks needs a better title.

• AI answer checks every 90 days. Ask each target question in ChatGPT, Perplexity and Google's AI features, and rewrite the answer block of any spoke that is not cited.

• Internal link coverage. Crawl each quarter and fix any orphan.

• Assisted conversions. Track which spokes readers view before they book a call.

Refresh every page each quarter: update figures, add new FAQs and change the "Last updated" date.

What are the most common topic cluster mistakes?

The most common mistake is planning from keywords and ending up with five pages that answer the same question. Most others come from skipping the link rules.

1. Overlapping spokes. Two pages that share an answer compete with each other. Merge them.

2. Writing the pillar first. It ships with nothing to link to, and nobody adds the links later.

3. Orphan spokes. A spoke the pillar does not link to goes against Google's guidance that every page you care about needs a link from another page.

4. Generic anchors. "Click here" tells neither readers nor crawlers what the page covers.

5. Covering topics you cannot prove. Google's helpful content guidance warns against entering a niche "without any real expertise."

6. Chasing special AI files or schema. Google says none are needed for its AI features.

7. Never refreshing. Out-of-date figures make the answer block wrong.

For guest posts that point back at your spokes, the relationship-first guest posting playbook covers pitching. When the cluster needs more pages than one person can write, the guide on scaling a content team with AI covers production.

Topic cluster checklist

Run this before a cluster goes live:

• One subject tied to a business line you can prove

• 8 to 12 spokes, each with one target question and no overlap

• Planning table filled for every page

• Each spoke links the pillar in its first 150 words, plus two siblings and one bridge

• Pillar links every live spoke

• Every page follows the AEO template

• Target questions logged for the 90-day AI answer check

FAQ

What is the difference between a pillar page and a spoke?
A pillar answers the broad head question and links to every spoke. A spoke answers one narrower question and links back to the pillar in its first 150 words.

How many spokes should a topic cluster have?
Semrush and CoSchedule do not set a fixed number. The plan on this site uses 8 to 12 spokes per pillar, which covers a subject without forcing overlap.

Do topic clusters still matter with AI search?
Yes. Google lists internal links among its best practices for AI Overviews and AI Mode, and those features search across subtopics.

Do I need special files or schema for AI answers?
No. Google says there are no special optimizations, AI text files or schema needed to appear in AI Overviews or AI Mode.

Should I still add a FAQ section?
Yes, for readers and answer engines. Google stopped showing the FAQ rich result from May 7, 2026.

Should topic cluster URLs be nested under the cluster name?
Flat slugs are safer. A page at /guides/{slug} can move to another cluster later without a redirect.

Want a second set of hands on your cluster plan?

I work with a small number of B2B teams as a fractional GTM and AI engineer, building content systems like this one, from the cluster plan to the drafting and refresh workflow. If that would help, see how I work or book a short intro call. Brands with sponsored content enquiries can use the same contact page.

Running revenue at a Series A or B SaaS company? Ask about the 90-day AI RevOps Sprint. I take two clients at a time.

About the author: Kevin Payne is an AI engineer and GTM operator who installs AI workflows for B2B teams. He has 10+ years in B2B SaaS demand generation and RevOps across Techstars, a16z and YC portfolio companies, and his writing has appeared in HubSpot, GetResponse, Outbrain and more.