Topic Clusters and Pillar Pages: Plan, Write and Link a Content Hub

Most small sites grow one page at a time. A post gets written because someone asked a question, another because a competitor published something similar, and a year later nobody can say which page is the main answer on a subject. Visitors land on a narrow article with no path to the broader picture.

Topic clusters and pillar pages are a way to plan that growth. A pillar page gives the broad overview of a subject. A set of supporting pages each answer one narrower question in full, and the pages link to each other in a way a reader would find useful. This guide is for site owners, writers and small marketing teams who want a content plan they can finish. By the end you will have a one-page cluster map, a pillar outline, a linking plan and a short list of checks for keeping the cluster honest.

Short answer: A topic cluster is one broad pillar page plus several supporting pages that each answer one narrower question, all linked in context. Google's documentation does not define or require the term. The structure helps readers move between related answers and helps crawlers find pages through links. It does not promise any ranking result.

Before you begin

You need a list of the pages you already have (a sitemap or a spreadsheet export will do), access to Google Search Console for your site, and a spreadsheet. If Search Console is not set up yet, start with Set Up Google Search Console: Complete Website Owner Checklist. Plan on two to three hours for the map, and more for the writing.

The main risk is changing live URLs. If your plan involves merging or renaming existing pages, redirect the old address to the new one and update your internal links before you remove anything. Keep a copy of the old page text until the redirect is tested.

What is a topic cluster, and what is a pillar page?

Both phrases come from the SEO industry, not from Google. Google's documentation does not define a "topic cluster" or require one, so treat the idea as a planning method. It works when it makes your site easier to use, and it is pointless when it only adds pages.

	Pillar page	Supporting page
Question it answers	The broad one: "How do I do X?" or "What is X?"	One specific question inside X
Depth	Covers each part briefly and sends readers on	Answers the narrow question completely
Typical length	As long as the overview needs, no more	As long as the answer needs, no more
Links out	To every supporting page, near the sentence it relates to	Back to the pillar and to one or two closely related siblings
How many	One per topic	Only as many as there are real, separate questions

Google gives no ideal number of supporting pages, and four honest pages beat twenty padded ones.

Do topic clusters help SEO?

They can help in ways Google does describe, but nothing here is a promise. Google's SEO starter guide says links are how it finds most new pages, and that link text tells users and Google something about the page being linked to. A cluster gives every page a natural reason to be linked from another page. The same guide advises grouping topically similar pages in directories, which mainly matters for crawling on large sites with more than a few thousand URLs. Google's helpful content guidance asks whether a page offers a substantial, complete treatment of a topic and more value than other pages in the results.

What a cluster does not do: it does not make a weak page strong, it does not replace original information, and it does not create demand for a topic nobody is searching for. Google also says it does not guarantee that any page will be crawled, indexed or shown.

Step-by-step instructions

Step 1: Choose a topic you can cover with real knowledge

Pick a subject where your business has something to add: first-hand experience, your own data, customer questions you answer every week. Google's helpful content questions warn against entering a niche only for search traffic and against summarising what others say without adding anything. Test the topic: do customers ask about it, and can you answer from direct experience?

Our worked example is a bicycle repair shop on example.com that chooses "bike maintenance for commuters".

What success looks like: One topic name and a one-sentence statement of who the cluster is for.

Step 2: Collect the real questions

List every question people ask about the topic. Good sources are your own support emails, questions customers ask in the shop or on calls, and the queries already bringing impressions to your site in Search Console (see Read the Search Console Performance Report: Clicks, CTR and Position). Write each question in the words the person used. Google notes that people phrase the same idea differently, so you do not need a page for every variation.

What success looks like: A raw list of 15 to 40 questions, each in a plain sentence.

Step 3: Group questions by intent and pick the page for each

Sort the questions into groups where one page would satisfy the same person. "How often should I oil a chain?" and "How do I know my chain is worn?" are different jobs, so they belong on different pages. "How often to lube a chain" and "chain lubrication schedule" are one job, so they share a page. Search Intent: How to Match Each Page to What Searchers Want explains how to tell the difference. Check your existing pages first; the best supporting page may already exist.

What success looks like: Each group has one named target page, marked as existing or new.

Step 4: Draw the cluster map

Put the plan in a table with one row per page. Here is the example:

Page	Role	URL	Question it answers	Status
Bike maintenance for commuters	Pillar	`/guides/commuter-bike-maintenance`	What does a commuter bike need, and how often?	Rewrite existing
Chain care	Supporting	`/guides/bike-chain-care`	How do I clean, oil and check a chain?	New
Brake pad wear	Supporting	`/guides/bike-brake-pads`	When do brake pads need replacing?	Existing, update
Winter commuting setup	Supporting	`/guides/winter-bike-commuting`	What changes for a bike ridden in rain and cold?	New
Tyre pressure	Supporting	`/guides/bike-tyre-pressure`	What pressure should I run?	New

Keep URLs short and descriptive, as in SEO-Friendly URLs: How to Build Readable, Stable Web Addresses. If you are weighing a bigger reorganisation, read Site Architecture SEO: Plan Your Pages and URL Structure Before Launch first.

What success looks like: A map you could hand to a writer, with no two rows answering the same question.

Step 5: Write the pillar page as an overview that sends readers on

The pillar page should answer the broad question on its own. Give each part of the topic a short section that states the key point, then links to the supporting page for the detail. Add a short contents list at the top with links to the section headings. Write the sections fresh instead of pasting in the supporting page text, because repeated paragraphs add length without value. Use headings as described in Heading Structure for SEO: Use H1 to H6 for Meaning, Not Style: one H1 for the page, H2s for the main parts.

What success looks like: A reader who never clicks a link still comes away with a correct, useful overview.

Step 6: Write each supporting page to stand alone

Each supporting page should answer its single question completely, start with the answer, and mention the broader topic only where it helps. Google's helpful content guidance asks about substance, not about a page's role. If you cannot find enough to say about a question, fold it into the pillar page or a sibling as a section instead of publishing a thin page.

What success looks like: Each page can be read first by someone who arrives from a search and still makes sense.

Step 7: Link the pages in context

Add links where a reader would want them: from the sentence on the pillar page that mentions chain wear to the chain care page, and back from the chain care page to the pillar with wording that says what the pillar covers. Use real links with descriptive text:

<p>Check the chain for wear every month; the
<a href="/guides/bike-chain-care">bike chain care guide</a>
shows how to measure stretch.</p>

Google follows links that are <a> elements with an href. It describes good link text as descriptive, reasonably concise and relevant, and "click here" or "read more" as too generic. It also says there is no ideal number of links per page, but an excessive number is likely too many, so link where it helps instead of adding every sibling to every page. More on this in Internal Linking Strategy: Link Your Pages for People and Crawlers and Anchor Text Best Practices for Internal and External Links. Also add each new page to your XML sitemap.

What success looks like: Every page in the map is reachable by at least one in-content link from another page in the cluster.

Step 8: Publish, then review in Search Console

Publish the supporting pages first or together with the pillar so the pillar's links do not point at pages that do not exist. After a few weeks, look at the Page indexing report for the new URLs and at the Performance report for the pages in the cluster. Indexing and impressions are decisions made by Google, so absence after a few weeks is not proof of an error; see How Long Does Google Take to Index a Page?.

What success looks like: The cluster map has a "last reviewed" date and a note of what changed.

How do I keep a cluster from turning into thin filler?

Three patterns cause trouble. The first is near-duplicate pages written for slight variations of one query. Google's spam policies describe doorway abuse as pages made to rank for similar queries that funnel users to a less useful intermediate page, and scaled content abuse as many pages made mainly to manipulate rankings, however they are produced. The second is one page per keyword, each with a few paragraphs. The fix is to merge them, as described in Thin Content and Duplicate Pages: How to Find and Fix Them. The third is stale pages; Content Pruning: Decide What to Update, Merge or Remove covers the decision.

Crawvix's orphan-page check compares the addresses in your sitemap with the links it finds on your pages, and its thin-page check reports pages with almost no visible text, so both are useful after you publish a cluster. They cannot judge whether a page is helpful; that is an editorial call.

Final verification checklist

The topic is one you can cover with first-hand knowledge, and the cluster has a stated audience.
The cluster map lists each page, its role, URL and the single question it answers.
No two pages in the map target the same intent.
The pillar page stands alone as an overview and links to each supporting page near the relevant sentence.
Each supporting page is complete on its own and links back to the pillar.
Links are <a href> elements with descriptive anchor text.
Every page appears in the XML sitemap and is linked from at least one other page.
Merged or renamed pages use a redirect and updated internal links.
A review date is recorded for the topic clusters and pillar pages.

Common mistakes to avoid

Treating the cluster as a quota. Publishing 20 supporting pages because a template said so produces thin pages. Publish only for real, separate questions.
Copying paragraphs from supporting pages into the pillar. Summarise in new words and link instead.
Linking everything to everything. A wall of links helps nobody. Link where the reader would ask "where is the detail?"
Vague anchors. "Read more" tells neither people nor Google what the destination is. Name the topic.
Forgetting the old pages. If an existing page already answers the question, update it instead of creating a rival, and use Orphan Pages: How to Find Pages With No Internal Links and Fix Them to find pages left out of the structure.
Changing URLs without redirects. Moving a page into a new section without a redirect strands its links and visitors.
Never reviewing. A cluster of outdated pages is worse than a small current one.

Frequently asked questions

How many supporting pages does a topic cluster need?

There is no required number. Google gives none. Start with the real questions you can answer well and stop when you run out.

Should the pillar page be the longest page?

Not necessarily. The pillar covers breadth and the supporting pages carry depth. Google states it has no preferred word count; see How Long Should a Blog Post Be?.

Do I need a special URL structure for a cluster?

No. Descriptive URLs help readers, and grouping similar pages in directories can help on large sites, but a flat structure with good internal links works too. Do not move live URLs only to fit a model.

Can I build a topic cluster with existing pages?

Yes, and it is usually the better first move. Map your current pages to the plan, rewrite weak ones, merge overlaps with redirects and add links between them before writing anything new.

Will a cluster improve my rankings?

It may make your site easier to understand and navigate, but Google does not promise any outcome from a structure, and ranking depends on many factors outside it.

Official references

Next step: Try the free website sample to see how your own site does on a few of these checks. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.