SEO Topic Clusters:
Plan, Link, and Measure

An SEO topic cluster connects a broad pillar page with supporting pages that answer specific questions about the same subject. In HubSpot’s topic cluster model, internal links connect the supporting pages back to the pillar and, where relevant, to each other. Building a cluster involves choosing a subject, assigning each page a clear purpose, connecting the pages, and reviewing the coverage over time.

What belongs in an SEO topic cluster?#

The pillar, supporting pages, and internal links form the structure. The division of content follows HubSpot’s description of pillar and cluster pages: the pillar covers the broad subject, while supporting pages explore its subtopics in detail.

Use a category page to help visitors browse a collection; use a pillar to explain the subject. A category can serve as a pillar when it provides that explanation as well as navigation. For planning purposes, keep the keyword list separate from the page map: the list records search language, while the map assigns questions and links to specific pages.

Why topic clusters matter for SEO#

Google’s SEO Starter Guide says logical site organization helps people and search engines understand how pages relate. Topic clusters offer a way to apply that guidance: collect related answers, make their relationship clear, and provide routes between them.

Use the structure to identify missing answers and reduce repeated coverage. Evaluate it alongside the quality of each page; Google’s starter guide emphasizes useful content and explicitly rules out automatic first-place rankings from following its advice.

How to build an SEO topic cluster#

1. Choose a subject with a clear boundary#

Write down the broad question the pillar will answer. Then list the narrower questions that need a definition, explanation, procedure, or comparison of their own. Define what the cluster will cover before collecting more keyword variations.

Choose a subject that fits the site’s purpose and available knowledge. Google’s people-first content guidance asks whether a site has a primary focus, demonstrates expertise, and leaves readers with enough information to achieve their goal. Use those questions to assess the proposed subject.

Keep the scope manageable. Put a narrower question on a separate page when it needs substantial detail to answer clearly. Keep it within the pillar when a short section completes the answer.

2. Inventory the existing content#

Review published pages before commissioning new ones. Record each page’s URL, main question, relevant search terms, content scope, and internal links. Read the body as well as the title: a title alone is insufficient for deciding whether to keep, revise, or combine the page.

Assign each page an action:

• Keep: retain a useful page with a distinct purpose.
• Update: improve an incomplete or outdated answer.
• Combine: bring repeated answers together in one maintained page.
• Create: fill an important question that the existing content does not answer.

Select an existing overview as the pillar when it can cover the broad question. Expand its explanation and add relevant links. Create a new pillar when the inventory has useful narrow answers but lacks a suitable overview.

3. Map search questions to pages#

Give each proposed page a one-sentence assignment stating what it will explain or help someone do. Record the main search query, related phrases, intended format, and the point where the pillar will link to it.

Review the search results for the target queries to assess the kinds of answers being presented. Compare their scope with the proposed assignment. Treat this as research for deciding the page’s purpose and format, then check the assignment against the existing content.

Group phrases that call for the same answer. Google’s language-matching guidance explains that a page can relate to multiple queries without explicitly including every exact variation. Use those variations naturally within the relevant page.

Separate questions when completing each answer requires different material. Look for differences in the procedure, evidence, comparison criteria, or troubleshooting steps. Repeated outlines and conclusions are a reason to review whether the proposed pages should be combined.

Keep the map practical: one row per planned or existing page, with its question, URL, role, scope, action, and intended links. Update the map after revisions so it reflects the published content.

4. Write the pillar and supporting pages#

Write the pillar to answer the broad question on the page itself. Explain the main concepts and decisions, then introduce the narrower subjects where they fit. Link to deeper coverage at the point where the overview reaches its scope boundary.

Write each supporting page to answer its specific question from the opening onward. Include the detail needed to complete that answer, and keep general background brief. Check that the page is understandable to someone arriving directly from search.

During editing, read the pillar and supporting pages together. Short definitions may be needed in more than one place; give detailed procedures and long comparisons a primary home, then link to them from the overview. This makes the content map usable during revisions as well as publication.

5. Add internal links in context#

Connect the pillar to the important supporting pages from the sections that introduce their subjects. Add links back to the pillar where the wider explanation helps. Link supporting pages to each other where the destination adds useful detail or continues the procedure being described.

Google’s link best practices say it uses links to discover pages and assess relevance. The same guidance recommends that every important page receive a link from at least one other page on the site. Check incoming links as well as outgoing links during the cluster review.

Use descriptive anchor text that identifies the destination. Google’s anchor-text guidance recommends concise, relevant wording and advises against forcing keywords into links. Read each anchor without its surrounding paragraph to check whether it gives a useful indication of the next page.

Check the rendered link markup. Google generally extracts crawlable links from an HTML a element with an href attribute, as its crawlable-link documentation explains. JavaScript can insert those links, but a script-controlled button without suitable link markup is less reliable for crawling.

Review each link for usefulness and placement. Google states in its internal-link guidance that there is no ideal link count. Add links where they help explain or navigate the subject, then test the destinations.

How to fix overlapping pages#

Compare pages by the question they answer and the substance of the answer. Shared terminology is a reason to examine them together. Before combining them, compare their definitions, steps, evidence, and conclusions.

Keep pages separate when their purposes remain distinct. Make those purposes explicit in the titles, openings, and headings, and move detailed material to the page assigned to cover it. Combine pages when they substantially repeat the same answer and a single page can retain the useful material.

Distinguish that editorial work from duplicate-URL handling. Google’s canonicalization documentation describes selecting a representative URL from duplicate or very similar pages. Canonical signals communicate a preferred URL; Google treats that preference as a hint and may choose a different canonical.

Use canonicalization for duplicate or near-duplicate versions that remain accessible. Make the content decision separately for articles that need rewriting or consolidation: identify the answer to retain, bring useful material into the chosen page, and confirm that the replacement covers the retired page’s purpose.

For a permanent move to a replacement page, Google’s redirect guidance recommends a permanent server-side redirect when possible. HTTP 301 and 308 indicate a permanent move, and permanent redirects signal that the target should be canonical.

After consolidation, update internal links to the final destination. Test the old URL’s redirect and the replacement page’s incoming links. Review the pillar’s summary and anchor text to ensure they still describe the answer at the destination.

How to measure a topic cluster#

Keep a list of the published cluster URLs and record when content, links, or redirects change. Establish a baseline before making revisions, then review the same pages over comparable periods.

Google’s Search Console Performance report provides clicks, impressions, click-through rate, and average position, with views grouped by pages and queries. Use those views to examine the pillar and supporting pages individually, then review the coverage across the cluster.

Start with these checks:

• Queries: compare the reported searches with each page’s assigned question.
• Pages: identify which URLs receive search visibility and clicks.
• Content: reread pages whose reported queries suggest a scope mismatch.
• Navigation: check that the pillar and supporting pages remain connected after revisions.

Keep report settings consistent, including date range and search type. Pay attention to aggregation: Google’s report documentation explains that page rows and property totals count data differently, so their totals can differ. Record the view used for each comparison.

Use changes in performance to choose what to inspect next. Review the answer, its links, and its technical accessibility before deciding on another revision. Keep the change record alongside the results so future reviews can distinguish content updates, linking changes, and URL consolidation.

Frequently asked questions#