Topic clusters for technology companies

The topic cluster model has been part of the SEO conversation for nearly a decade and most B2B tech companies have heard of it. Far fewer have actually implemented it well. The pattern we usually find: a marketing team that says they “do topic clusters” but in practice has 200 blog posts published roughly chronologically, no clear pillars and no internal linking discipline.

Done properly, topic clusters are how technology companies build genuine topical authority and how they get their best content to rank for competitive terms. Here’s how we go about it.

What a topic cluster actually is

A topic cluster has three parts:

1. A pillar page that comprehensively covers a broad topic.
2. A set of cluster pages that cover specific subtopics in depth.
3. Internal links that consistently connect cluster pages back to the pillar and across to relevant siblings.

The pillar ranks for the broad term. The cluster pages rank for long-tail variations. The internal links concentrate topical authority on the pillar and distribute it back out.

It’s a simple model. The execution is where most teams struggle.

Choosing pillars: the test we use

A good pillar topic for a tech company:

• Has meaningful search volume (aggregate across the cluster, not just the head term).
• Maps to a service or product the company sells.
• Is broad enough to support 8-20 supporting articles without forcing it.
• Is something the company has genuine expertise to write about.

For an MSP, plausible pillars might be:

• Managed cyber security
• Cloud migration services
• Microsoft 365 management
• IT support for [target vertical]

For a SaaS, pillars might be:

• The category they compete in (e.g. “endpoint detection and response”)
• A core use case (e.g. “incident response automation”)
• An adjacent topic where they want to build authority (e.g. “SOC 2 compliance for SaaS”)

We avoid pillars that are too narrow (“Microsoft Teams calling features”) because they don’t give you room to expand. We avoid pillars that are too broad (“cyber security”) because the SERP is impossible to crack and the cluster sprawls.

Pillar page structure

A good pillar page:

• Is 2,000 to 4,000 words. Long enough to comprehensively cover the topic, short enough that it doesn’t become a 10-page slog.
• Has a clear structure with H2s for major subtopics. Each H2 should map to one or more cluster pages.
• Links out to every cluster page. Generously. The pillar is the hub, not a dead end.
• Targets a primary head term in the H1 and meta title.
• Includes an FAQ section answering common questions Google surfaces in People Also Ask.
• Has clear conversion paths for buyers ready to act.

We’ve broken the page-level architecture down further in pillar page structure.

For SaaS sites, the pillar often doubles as a category landing page. For MSPs, it’s usually a service page with a long, content-rich body. Our SEO for SaaS product pages post covers the SaaS-specific structure in more detail.

Cluster page structure

Cluster pages:

• Are 1,000 to 2,000 words.
• Each target one specific long-tail query that the pillar can’t realistically rank for.
• Link back to the pillar with descriptive anchor text.
• Link sideways to 1-3 closely related cluster pages.
• Don’t try to cover the whole pillar topic. They go deep on one slice.

A common mistake we see: cluster pages that are mini-pillars themselves. They cover too much, dilute the focus and end up competing with the actual pillar. The discipline is to keep each cluster page genuinely focused on one query.

A worked example: managed cyber security for MSPs

Let’s make this concrete. For an MSP’s “managed cyber security” pillar, the cluster might look like:

• Pillar: A 3,000-word “Managed cyber security services” page on the services section, targeting the head term and outlining the company’s full approach.
• Cluster pages in the blog or resources:
  • “Cyber Essentials Plus: what’s required and how to prepare”
  • “Endpoint detection and response for SMB: what to look for”
  • “Phishing simulation programmes: how often, what works”
  • “SOC outsourcing vs in-house: a 50-employee decision”
  • “Cyber insurance requirements 2026: what brokers look for”
  • “Microsoft Defender vs third-party EDR for managed services clients”
  • “Incident response retainers: what’s included and what isn’t”
  • “Ransomware tabletop exercises: how to run one”

Eight to ten focused articles, each ranking for its own long-tail term, all linking back to the pillar. The pillar accumulates topical authority and starts to rank for “managed cyber security” and related broad terms.

This is exactly the structure we cover in our pillar-cluster approach for SaaS content on the content marketing side.

Internal linking discipline

The cluster only works if the linking is consistent. We’ve seen plenty of “topic clusters” where the pillar page links to four cluster articles, the other six are orphaned and the cluster articles never link to each other.

The rule we apply: every cluster page must link to the pillar in the body copy (not just the nav or footer) and link to at least two other relevant cluster pages. Every pillar must link out to every cluster page in its set, with descriptive anchor text.

Audit this quarterly. New cluster pages get added. Old links get broken in CMS migrations. Without a review cadence, the structure decays.

Our internal linking strategies for large tech websites post covers the linking discipline in more detail.

Choosing cluster topics: where to find them

Most teams choose cluster topics by brainstorming. We use data:

• Search Console: Queries the site already gets impressions for, where it isn’t ranking. These are intent-validated topics.
• Ahrefs or Semrush: Keyword research within the pillar topic, filtered for long-tail variations.
• People Also Ask: Questions Google is already answering for the broad topic. Each one is a potential cluster page.
• Sales calls and demos: Questions buyers actually ask. Often these are the highest-converting topics.
• Competitor cluster analysis: What clusters do competitors rank for? Where are they weak?

For more on the long-tail side, our long-tail keywords for MSPs post covers the research process in detail.

When clusters don’t work

Topic clusters aren’t the right framework for every site or every topic.

• Very broad B2C-style topics with massive SERP competition. Topic clusters don’t beat the BBC or Wikipedia. They work in B2B niches where authority is more accessible.
• Topics with no commercial relevance. Building a 15-article cluster on a topic that doesn’t relate to your services is a waste, however much traffic it earns.
• Sites without the discipline to maintain the structure. Clusters need a content lead who keeps the linking and quality consistent. Without that, they decay.

For a pragmatic alternative on smaller sites, we sometimes recommend a flatter “hub and articles” approach with one or two major hubs and 5-8 supporting articles each, rather than four full pillars.

Measuring cluster performance

Track at three levels:

• Pillar page rankings and traffic for the head term and close variations.
• Cluster page rankings and traffic in aggregate. Are the cluster pages collectively bringing in long-tail traffic?
• Conversion rate from cluster pages. Are they driving enquiries, demos, sign-ups?

We also look at “topical authority” indirectly. Does Google start ranking the site for terms within the topic that we haven’t even targeted directly? That’s the signal that the cluster is working. The pillar’s authority is helping pages rank for tangential queries.

Topic clusters and AI search

LLM-powered search systems benefit from cluster structures even more than traditional Google does. Well-organised pillars and supporting articles make it easy for AI assistants to gather context and cite specific subtopics. Our primer on AI search optimisation covers this in more detail. The related piece on writing content LLMs cite explains how to structure cluster articles for AI visibility.

A starter framework

If you’re building your first cluster from scratch, the steps:

1. Choose one pillar topic. Just one.
2. List 8-12 cluster topics. Validate volume and intent.
3. Write or commission the pillar (or extend an existing service page).
4. Publish 2-3 cluster articles per month, building toward the full set over a quarter.
5. Audit internal links monthly. Make sure every new article is linked from the pillar and from the previous articles.
6. After 6 months, assess performance and decide whether to start a second cluster or deepen the first.

Topic clusters are slow. The first cluster takes 6-9 months to mature. The second is faster because you’ve built the discipline. By the third, you have an organic engine.

If you’re staring at a content backlog and not sure which pillars to commit to first, we’d be glad to compare notes. Our SEO service and content marketing service pages cover how we approach this work end to end.