Topic Clusters and Internal Linking: How to Build One

Topic Clusters and Internal Linking: How to Build One

Part of a guideThis post is one piece of AI Search Visibility: The Complete Guide to SEO, GEO, and AEO. This one covers the content organization layer: how a set of pages should be structured and linked, which is how this whole guide is built.

Most business blogs are a pile. Twenty posts, published whenever someone had an idea, each one linking to nothing and linked from nowhere except the blog index. Every post is a lone island, and none of them adds up to a claim that your site knows this subject.

A topic cluster is the fix. It's a deliberate set of pages that cover one subject from several angles and link to one another in a clear pattern. It helps visitors find what they need, it helps crawlers discover and understand your pages, and it gives you a repeatable way to decide what to write next.

The pillar-and-spoke model

A cluster has two kinds of page:

The pillar answers "what is the big picture?" and the spokes answer "how do I do this one part?" A reader can enter at either level and move in both directions.

Why it works

Let's be careful here, because "topical authority" is a term SEOs use heavily and Google doesn't formally document. What we can say plainly is this:

  1. Crawlers follow links. Pages linked from other pages on your site are discovered faster and revisited more reliably. A page with no internal links (an "orphan") may not be found at all.
  2. Anchor text gives context. A link labeled "how AI crawlers read robots.txt" tells a machine what the target page is about, in your own words.
  3. Coverage signals substance. A site with a dozen coherent pages on a subject looks more like a real source on it than a site with one page.
  4. It matches how people research. Someone with a broad question wants the overview, then wants to drill into their specific problem. A cluster serves both.

The best evidence we have is first-hand. In the HVAC/R AI Pro case study, a brand-new domain with no authority was built as a hub-and-spoke cluster: pillar pages for each product workflow, plus a blog of specific technician questions that link back into them. Each page was mapped to a specific query group before it was written, and the pages were linked so they reinforced each other rather than competing. Within five months the site was appearing for 75 queries and was named first in Google's AI Overview for its head term. One case isn't proof of a rule, but the approach is sound and the numbers are from Search Console.

How to build a cluster, step by step

1. Choose a topic you can genuinely own

Pick a subject that's central to your business and broad enough to have five to fifteen distinct subquestions. "Roofing" is too broad; "residential roof replacement in Phoenix" is probably right. "Our company news" isn't a topic at all.

2. List the real questions

Collect what people actually ask. Good sources:

  • Your sales calls, emails, and support tickets. This is the best source, because it's the language of real customers.
  • Google's "People also ask" boxes and related searches for your core term.
  • Search Console queries you already show up for.
  • Prompts you'd type into ChatGPT or Perplexity as a customer.

3. Group the questions by intent

Sort your list. Questions that a single page could answer well belong together. Questions with different goals (learning, comparing, buying, fixing) deserve separate pages. Each page should have one job. If two pages would answer essentially the same query, merge them. Otherwise they compete with each other, which is called keyword cannibalization.

4. Write the pillar

Build the overview first, or at least outline it. It should define the topic, lay out the main components, and offer a short answer to each subquestion, with a link to the full answer. Give it a table of contents if it's long.

5. Write the spokes

Each spoke goes deep on one question and follows the content principles in How to Write Content AI Search Engines Cite. Publish them over time. You don't need every spoke live on day one, but don't link to pages that don't exist yet.

6. Link deliberately

This is the step people skip. See the rules below.

7. Maintain it

When you publish a new spoke, go back and add links to it from the pillar and from two or three related spokes. Clusters decay when new pages are added but the old ones never learn about them.

Internal linking rules that hold up

  1. The pillar links to every spoke. It's the map.
  2. Every spoke links back to the pillar. Ideally near the top, so readers who land mid-topic can get oriented.
  3. Spokes link to each other where it's useful. Link when a reader would naturally want the related page next, not to hit a quota.
  4. Use descriptive anchor text. "Read our guide to AI crawlers and robots.txt" beats "click here" and beats "learn more."
  5. Put links in the body copy. Contextual links inside the content carry more meaning than a wall of links in a footer or sidebar.
  6. Vary the wording naturally. Don't use the identical exact-match phrase every time. Write like a person.
  7. Aim for a handful per page. There's no magic number. A few relevant contextual links per post, plus a related-reading block, is plenty. Too many links dilute each one.
  8. Make sure nothing is orphaned. Every page you want found should be reachable through at least one link from another page, and be listed in your sitemap.

A worked example: the map of this guide

PageRoleLinks to
AI Search Visibility guidePillarAll spokes, plus the HVAC/R case study and older related posts
AI crawlers and robots.txtSpoke: accessPillar, llms.txt, schema, tracking
llms.txt explainedSpoke: myth-checkPillar, crawlers, content, schema, tracking
Schema markupSpoke: understandingPillar, entity SEO, crawlers, local SEO
Entity SEOSpoke: authorityPillar, schema, local SEO, content, tracking
Writing citable contentSpoke: contentPillar, clusters, entity SEO, tracking
Local SEO and AI searchSpoke: localPillar, entity SEO, schema, tracking
Tracking AI visibilitySpoke: measurementPillar, crawlers, content, entity SEO

Notice what's happening: no page is a dead end, every spoke has a clear reason to exist, and the reader can move up to the big picture or across to the next step at any point.

How to audit the linking you already have

  • Crawl your site with a tool like Screaming Frog (free up to 500 URLs) or a similar crawler, and look at "inlinks" per page. Any important page with zero or one internal inlink needs attention.
  • Compare against your sitemap. URLs in the sitemap that the crawl never reached are orphans.
  • Check Search Console for "Discovered, currently not indexed" and "Crawled, currently not indexed" pages. Weak internal linking is a common culprit, though not the only one.
  • Review your top pages. Add links from pages that already get traffic to newer or weaker pages that deserve more.

Common mistakes

  • Publishing spokes with no pillar. You have a pile again, just a better-written one.
  • Two pages targeting the same question. Pick one and consolidate, redirecting the other.
  • Linking everything to everything. If every page links to every other page, the structure means nothing.
  • Vague anchors. "Here" and "this post" waste the signal.
  • Abandoning the cluster. A cluster is a living structure. New spokes and refreshed pillars keep it accurate.

If your business has a blog with a backlog of unconnected posts, that's a quick win: pick your best subject, choose a pillar (or write one), and start connecting. For more on why a blog is worth investing in at all, see 7 Reasons to Add a Blog Section to Your Website. And to see the whole picture this cluster supports, go back to the AI Search Visibility guide.

Want this done for your site?

Crawled SEO runs a Visibility Audit that checks the things in this guide against your actual site: crawler access, structure, entity signals, content, and how you show up in AI answers today.

Request your free audit