Topic Clusters for Small Sites: Avoid Cannibalization

A topic cluster is an editorial planning method, not a Google ranking feature. For a small site, its value is practical: assign every important page one primary job, connect related jobs with useful internal links, and stop creating a new URL for every keyword variation.

Start with a page map, not a large content calendar. If two proposals would answer the same question for the same person at the same stage, they probably belong on one URL. This guide prevents overlap before publication. If live pages already trade impressions for the same queries, use the Search Console cannibalization guide to diagnose real data first.

What a useful topic cluster contains

Google recommends a logical site structure, links to important pages from relevant pages, and concise, relevant anchor text. It also says there is no magical ideal number of links on a page. Build the structure for readers and maintainability, then make that structure crawlable.

Start with page jobs, not keyword counts

Write one sentence for every existing or proposed URL:

This page helps [audience] make [decision or complete task]
using [evidence or method].

Three pages can discuss SEO audits while doing different jobs:

• a service page helps a buyer purchase a fixed technical audit;
• a Search Console guide helps an owner inspect first-party data before hiring;
• a pricing guide helps a buyer compare scope and budget.

Now compare two weak proposals: “what an SEO audit includes” and “what is included in an SEO audit.” Different wording does not create a different job. Put the useful material on one stronger URL.

Build a page map before writing

The closest-existing-URL field is mandatory. It forces the writer to plan against the site that already exists instead of an empty spreadsheet.

Group query variations by user intent

SEO audit price, SEO audit cost, and how much is an SEO audit usually belong to one query family because the reader wants the same decision. Use the natural variations inside one complete page.

Create a separate URL only when the answer requires a different action, audience, format, or evidence.

Keyword tools can reveal phrasing and demand. They cannot make the final editorial decision about whether two users need the same page.

Choose the right cluster center

The center is the page that best orients a reader to the subject. It does not have to be a long pillar article. A useful center may be a service category, product category, concise guide hub, definitive guide, or resource index.

For a small service site, a commercial page can remain the main business destination while an educational hub organizes practical guides. They should link when the next step is useful without pretending they serve identical intent.

• What page should introduce this part of the site?
• What page should receive contextual links when the subject is discussed broadly?
• Can it remain useful as supporting pages are added?
• Does it orient the reader, or does it merely repeat card titles?

Give every page a contract

Primary audience:
Primary decision:
Main query family:
Must answer:
Will not answer in depth:
Unique evidence:
Primary conversion:
Closest existing page:
Required internal links:

The “will not answer in depth” line prevents drift. This topic-cluster guide owns pre-publication mapping, query boundaries, hub choice, and link planning. It acknowledges live overlap, but sends the reader to the separate Search Console workflow for diagnosis.

Require unique evidence or utility

A distinct keyword is not enough. A page should contain something that belongs to its job: a decision table, calculation, tested procedure, annotated screenshot, case, template, failure path, or official-source interpretation.

If two proposals would use the same H2 outline, examples, and conclusion, merge them before writing. Changing only the title creates maintenance debt and competing signals.

Plan internal links by reader movement

Google can crawl normal <a href> links and uses their context and anchor text to understand pages. Plan three useful directions:

Broader to narrower

A hub or broad guide links to a specific task when the reader needs detail.

SEO guide hub -> Search Console pre-audit

Narrower to broader

A specific guide links to the service or broader framework when the reader needs context or a next step.

Search Console pre-audit -> technical SEO audit service

Sibling to sibling

Related guides link when a real sequence joins them.

topic cluster planning -> cannibalization diagnosis

Use descriptive anchors such as Search Console cannibalization diagnosis or old-page merge and redirect decision. Avoid repeated “read more” links and keyword-heavy anchors forced into every article.

Do not confuse overlap with duplication

Canonical tags are for duplicate or very similar URLs. They are not a method for choosing a winner between two useful pages with different primary content. If a page is retired, a permanent redirect is usually clearer than leaving two full pages and hoping a canonical repairs the editorial decision.

Run a pre-publication collision test

Compare the proposal with the three closest existing URLs. Answer yes or no:

1. Does it serve the same audience?
2. Does it solve the same primary task?
3. Does it target the same intent and funnel stage?
4. Would it use substantially the same H2 outline?
5. Would it rely on the same examples and evidence?
6. Would the same internal anchor naturally point to either page?
7. Would a reader need both pages?
8. Can the writer state the boundary in one sentence?

Several yes answers in the first six questions, combined with weak answers to the last two, are a warning. Update the existing page, merge the useful material, reposition the proposal around another task, or reject the new URL.

How many pages should a small cluster have?

There is no correct number. A cluster may begin with one commercial destination, one orientation page if needed, two or three supporting guides with separate jobs, and one case or proof page. That is an example shape, not a quota.

FloxoLab adds a dedicated cluster hub only after six related guides are live and at least three more are planned. This is an internal maintainability threshold, not a Google rule. Before that point, the existing SEO guide hub and contextual links are enough.

Every registered FloxoLab article also needs contextual links from at least two distinct articles or cases. Hub cards do not satisfy the rule. The requirement prevents isolated pages and forces link support to be part of publication rather than cleanup months later.

Maintain the cluster as one system

Review the map when a new article is proposed, a service changes, several pages begin earning the same query family, a migration changes URLs, or the hub stops representing the current library.

1. Update page contracts and boundaries.
2. Confirm canonical URLs and remove redirecting internal links.
3. Find orphaned or weakly linked pages.
4. Review content that repeats another page's job.
5. Update sources and verified dates after substantive changes.
6. Use Search Console page and query patterns to test suspected overlap.
7. Record merge, redirect, reject, or reposition decisions.

When an old URL no longer deserves its own role, use the old-page decision framework to choose between updating, merging, redirecting, noindexing, keeping, and deleting.

Compact planning checklist

• Inventory existing pages before researching new titles.
• Group query variations by user task.
• Assign one primary job to each URL.
• Record the closest existing page.
• State what the proposed page will not cover in depth.
• Require unique evidence or utility.
• Plan broader, narrower, and sibling links.
• Run the collision test before drafting.
• Reject or merge proposals that cannot defend a separate role.
• Review the map as the site and services change.

The goal is not to own every phrase with a separate URL. It is to make the site's knowledge and offers understandable: one page per primary task, connected to the next useful decision.

Sources checked

Google's site-structure, internal-link, and canonical guidance was verified from official sources on July 27, 2026. The page-contract, hub-threshold, and two-source inlink rules are FloxoLab editorial methods, not Google requirements.

• Google Search Central: sitelinks and logical site structure
• Google Search Central: link and anchor text best practices
• Google Search Central: canonical URL guidance
• Google Search Central: SEO Starter Guide