Key takeaways
- A topic cluster is a connected set of pages answering different customer questions within one subject.
- Check existing pages before writing: an incomplete answer may need improving, not duplicating.
- Give each proposed page a brief covering its question, outcome, evidence and boundary.
- Link pages only where the connection genuinely helps the reader continue.
- A rolling register of page purpose, status and links prevents overlap early.
A publishing schedule tells you when content is due, but not why each page deserves to exist. Start with the customer question, check existing answers and define what a new page contributes. A topic cluster connects those distinct answers within one relevant subject.
What makes a cluster useful, not bloated?
A useful cluster gives every page a clear purpose. Some visitors need an overview; others need to compare options, understand a quote or prepare for an appointment. Those needs can justify separate pages when each needs a substantive answer. Different headlines alone do not create different purposes.
Compare the intended reader, question, evidence and outcome before approving another article. If two ideas would give substantially the same answer, improve the stronger existing page instead. Publishing frequently does not in itself demonstrate expertise.
Start with the customer's decision, not a keyword
A cluster planned around a real decision holds together naturally. A cluster planned around a keyword list can fragment because keywords multiply faster than reader needs. Ask what the person is trying to work out and what they need before they can move forward.
“Garden services” is too broad. “Helping a homeowner assess a proposed patio installation” gives a clearer boundary. A service explanation, material comparison and quotation guide may then have distinct jobs without overlapping.
- Use questions customers have actually asked in calls, emails and enquiries.
- Record relevant search suggestions or related questions with source and date.
- Treat published competitor titles as qualitative signals, not proof of traffic or commercial value.
Audit existing pages before writing another
Gather current service pages, published articles, drafts and approved briefs before commissioning new content. For each page, record the URL, reader, central question, outcome and status. Read the page itself; titles can hide overlap or make genuinely different pieces sound similar.
The audit commonly reveals several pages pursuing the same intent, a useful guide with no internal links, or an old page competing with a newer answer. Where an existing page already answers the proposed question well, maintain it instead. Where it is incomplete, decide whether an update fills the gap without changing its purpose.
Brief every proposed page with a distinct job
A short brief should state the customer question, the outcome the reader should achieve, the evidence needed and the scope boundary: what the page deliberately leaves to another page. It should also say what the new page contributes that the nearest existing one does not.
If the only difference from an existing article is the headline, it is usually not a new page. A distinct page can still link to a fuller explanation elsewhere rather than repeating it in full.
Keep, update, merge or separate?
Two pages can sit together when they serve different needs and both have enough substance. Update a page when new information fits its current purpose. Consider merging when two pages repeat the same answer for the same audience, while recognising that changing live URLs is a separate technical decision.
A new article earns its place when there is credible evidence of demand, the topic needs substantive treatment and inserting it into an existing page would distort that page's job. These are editorial decisions, not a rule that search engines need one page for every keyword.
Link pages where it helps readers move forward
Links help when they appear at the point a reader needs the next answer: someone reading about quotation factors may need a materials comparison next. Use descriptive wording that tells the reader what the destination covers. Google's SEO Starter Guide explains how links help users and search engines discover pages and understand context.
Not every article must link to every other article. Forced links create clutter. The useful question is what the reader needs next and whether the destination genuinely supplies it.
Keep a rolling register
A simple record of each page's question, purpose, status, URL, source material and related links makes overlap easier to spot before it happens. Mark whether a page is an idea, researched candidate, approved brief, draft, reviewed item or live page. Use that record as the starting point for the next content batch.
Clusters organise answers; they do not guarantee AI visibility
Google says established SEO practices, including sensible internal links, remain relevant to its AI features. It does not say a particular cluster size or link pattern produces AI citations. Record completed publishing and linking work separately from search appearances, AI mentions and enquiries.
Map the current pages, write a distinct purpose for the next proposal and decide whether the best next step is improving an existing answer or creating a genuinely new one.