Topic clusters: organise content around reader questions
Build topic clusters around questions, intent and useful next steps; distinguish pillar and supporting pages without duplicating content.
Updated: · AI-generated editorial illustration
A topic cluster organises a subject into related pages with distinct roles. It helps a reader move from an overview to a specific answer, rather than generating many pages that mention the same keyword. A useful cluster has understandable paths and a separate job for each page.
The examples use ecommerce websites as an editorial planning exercise. They are not measured keyword-volume estimates. For your business, add actual customer questions and available search data before deciding priorities.
1. Choose a subject connected to real needs
Start with what the business understands and what customers need to decide. For an ecommerce website, questions might cover platform choice, catalog preparation, product copy and checkout testing. Avoid unrelated subjects merely because they offer many keywords. A cluster without an accountable content owner can become a collection of superficial articles.
Google's helpful-content guidance supports evaluating the reader's purpose. The key question is whether a page helps someone complete a task. Article count and repeated phrases do not replace depth, examples and evidence. Keep the subject close enough to the service that recommendations can be made responsibly.
2. Distinguish pillar, guide and service roles
A pillar introduces the subject and major decisions. A supporting guide answers one question more deeply. A service page describes offered work and how to discuss it; it should not pretend to be neutral advice when its primary purpose is buying a service. These pages can connect without reproducing each other's entire content.
For example, an ecommerce preparation pillar can lead to platform, product-page, category and checkout guides. The checkout guide focuses on errors, totals and confirmation, mentioning platforms only where relevant. Write a one-sentence task for every URL first. Nearly identical tasks indicate that the scope needs clarification.
3. Prioritise questions using available evidence
Group questions from email, conversations, forms and Search Console by problem. Record their source so assumptions do not become invented research findings. A new site without search data can start with hypotheses about important buying decisions, clearly labelled as hypotheses.
Do not assign search volume or difficulty without the tools and data required to support those numbers. Search Console can reveal queries and existing pages, but it does not describe the entire market. Complete one useful guide before opening many similar ones. Prioritise material that removes a real decision barrier, not simply the easiest phrase to turn into a headline.
4. Link according to the reader's next step
Let pillars lead to relevant guides and supporting pages lead to context or the next task where needed. Anchors should describe the destination. Linking every article to every other article in a long list is not an automatic improvement. A link earns its place by explaining why the reader might need that page next.
Google's crawlable-link guidance supports the technical review. Use actual links with href rather than script-only navigation. For bilingual guides, preserve language along the reading path. Check working destinations, canonical coherence and whether every published article is reachable from the catalogue.
5. Check overlapping intent before adding a page
A guide to website speed and another to speed optimisation may perform the same task. A renamed title does not make the second page distinct. Compare answer, audience and scope. Merge, expand the existing page or separate genuine causes such as images, caching and interaction when each guide has its own material.
Preserve the existing URL when its purpose still fits an expansion. If merging and retiring a page, plan an equivalent redirect and update internal links. Canonical is not an automatic editorial remedy for different pages competing for the same intent. Decide what the reader should find first, then choose the appropriate technical signals; see the canonical guide.
6. Review the whole group and refresh evidence
Maintain URL, task, owner, source-review date and important links. When a platform changes, check the related group rather than updating only one page. Modification dates should correspond to substantive edits instead of making unchanged content appear fresh.
Review the group together: which questions are answered, which pages lead to relevant services and where gaps remain. More page views are not automatically better; readers may be circulating because an answer is unclear. Combine quantitative signals with content and task review. A complete cluster is a maintained reading system, not merely a batch of articles published on the same day.
Frequently asked questions
How many articles does a cluster need?
There is no fixed count. It depends on the distinct questions worth answering. A small, complete, well-linked group is more useful than many pages performing the same task.
References and further reading
To apply this to your current website, explore the SEO optimisation service or contact Dean Vu to define a scope around your existing site and actual evidence.