The standard topic cluster advice is to write a broad pillar page, surround it with supporting posts, and link them together. It works, in the narrow sense that it produces rankings. It also produces the most common failure state in B2B content: thirty thousand monthly sessions and no measurable effect on pipeline.
The structure is not the problem. The sequence is.
Why the usual order fails
A conventional cluster starts at the top of the funnel because those queries have the highest volume and the lowest difficulty. “What is [category]” is easy to rank for and easy to write.
The trouble is that the people searching it are, by definition, at the point of least commercial intent. They are learning what the category is. Very few of them will buy anything this quarter, and almost none of them will buy from you because of that article.
Meanwhile the queries where someone has a credit card out — “[competitor] alternative”, “[category] pricing”, “best [category] for [use case]” — get postponed to phase two, which arrives in month eight if it arrives at all.
By then the content programme is being judged on sessions, because sessions are what it produced.
Invert it
Build the commercial layer first, then the informational layer that supports it.
Layer 1 — Demand capture. Pages targeting queries where the searcher is comparing or buying:
- Comparison pages: “X vs Y”
- Alternative pages: “alternatives to X”
- Use-case pages: “[category] for [specific situation]”
- Pricing and cost pages
- Integration and compatibility pages
- “Best [category] for [segment]” where you can honestly be on the list
These have lower volume and higher difficulty, and they convert at rates the informational layer never approaches. They also give sales something to send, which is the fastest way to get internal support for a content programme.
Layer 2 — Demand creation. The informational pages: definitions, how-tos, frameworks, troubleshooting. Written after the commercial pages exist, and written specifically to link into them.
This ordering produces revenue evidence in months three to five rather than month twelve, which changes the conversation about whether to continue funding it.
How to find the commercial layer
Most of it is not in a keyword tool, because the volumes are too low to register reliably.
Mine your own search data. Search Console queries with low impressions and high average position are often commercial terms you already half-rank for. These are the cheapest wins on the list.
Ask sales for the objections. Every recurring objection is a page. “How does this compare to X” and “does it work with Y” are both queries and both deals.
Look at what your competitors rank for that you do not. Filter to pages rather than keywords, and look specifically at their comparison and alternative pages.
Read your own support tickets. The questions that arrive after purchase are frequently the questions that block purchase for the next person.
The internal link rule that does the work
Clusters only function if the link graph reflects the hierarchy, and most implementations get this backwards by linking everything to the pillar.
The rule that works:
- Informational pages link down to the commercial pages they naturally support, with descriptive anchor text.
- Commercial pages link across to each other where the comparison is genuine.
- The pillar links to everything; everything links back to the pillar.
- No page links to more than a handful of siblings, because a link to everything is a signal about nothing.
This is the difference between a cluster and a tag archive. The anchor text is doing the work of telling Google which page owns which query — the same mechanism that prevents keyword cannibalization.
What a brief has to contain
A brief that says “write 1,500 words on X, include these keywords” produces the content everyone complains about. A brief that gets used contains:
- The single target query and its intent classification. One query, one URL, no exceptions.
- The specific reader. Not “marketing managers” — “a marketing manager who has already tried this and it did not work”.
- What the page must answer, as questions rather than headings.
- The evidence required. Which internal data, which named sources, which screenshots.
- What to link to and with what anchor, internal and external.
- What not to say. Claims legal will reject, competitor characterisations you will not make.
- The subject-matter expert to interview, and three questions to ask them.
That last item is the one that separates content from filler. A writer working from ten other blog posts produces a summary of those ten posts. A writer working from a thirty-minute interview with someone who does the job produces something that could not have been assembled from search results — which is the whole substance of Google’s people-first content guidance.
Where AI fits, honestly
Used for research, clustering, outlining and first-draft structure, language models save real time. Used to generate publishable copy at volume, they produce text with no experience behind it and nothing of its own to cite — which is precisely what the helpful content guidance is aimed at.
The practical test: could this page have been written without access to anything except other search results? If yes, it is unlikely to outrank the pages it was assembled from.
Measure clusters, not pages
Judge a cluster on:
- Assisted conversions by URL cluster, not sessions. GA4 plus a URL-to-cluster mapping does this.
- Commercial page position over time, tracked as a group.
- Sales usage. If nobody sends the comparison page to a prospect, either it is not good enough or nobody knows it exists.
- Time to first conversion from a new cluster, which tells you whether the ordering is working.
Sessions belong in the report, at the bottom, as context.
This is how content strategy runs here: intent classification first, commercial layer first, briefs written for people who actually know the subject. If you want to see which commercial queries your site is already close to ranking for, send us your domain — the free audit includes an intent-classified query set.
