SaaSB2B SaaS · DACH region (anonymised, NDA)~5 months to full map execution

Building Topical Authority for a B2B SaaS

A SaaS publishing steadily with little ranking traction — no topical architecture. A full topical map and entity work turned volume into authority.

40 → 95+ pages

Topical coverage

Newly ranking

Category terms

0 → measurable

Pipeline attribution

~5 months

Timeline

The challenge

The team had a content calendar and a writer producing 4-6 posts a month, consistently, for over a year. Almost none of it ranked past page three. Traffic was flat despite the volume, and organic contributed close to nothing to pipeline — the marketing team had started quietly deprioritising SEO in favour of paid, assuming the channel just didn't work for their category.

What made it harder

  • The product sat in a crowded category (workflow automation) where three well-funded competitors already had years of content and backlink history
  • Existing content was written keyword-first, not entity-first — dozens of posts loosely 'about' the topic with no defined relationship to each other
  • No internal linking strategy existed; posts were orphaned from each other and from the product pages that actually mattered for pipeline
  • The brand itself had thin entity signals — inconsistent naming across the site, no schema, nothing that told Google or an LLM what kind of company this was

The approach

  • Ran a full competitive content audit against the three category leaders — mapped every subtopic, question, and entity they covered that this site didn't
  • Built a pillar-cluster topical map: one pillar page per core product capability, with cluster pages covering every buyer question, comparison, and use-case around it
  • Retrofitted ~60% of existing content into the new map — merged overlapping posts, rewrote thin ones to match cluster intent, canonicalised the rest
  • Implemented Organization + Product + SoftwareApplication schema and cleaned up brand-name consistency across the site, footer, and social profiles
  • Rebuilt internal linking so every cluster page linked up to its pillar and across to the nearest conversion page — not just to other blog posts
  • Sequenced publishing so pillar pages and highest-intent clusters shipped first, funding the case for the deeper long-tail coverage that came after

The outcome

  • Went from ~40 disconnected posts to a mapped architecture of 6 pillars and 55+ cluster pages with defined relationships between them
  • Started ranking for competitive category terms the site had never appeared for, not just long-tail variants
  • Organic began showing up in pipeline reporting for the first time — not as top-of-funnel vanity traffic, but as a measurable source of demo requests
  • The brand became resolvable as a distinct entity — consistent naming, schema, and structure gave both Google and LLM-based tools a clear picture of who the company was and what it did

The takeaway

The volume was never the problem. Twelve months of consistent publishing had produced almost nothing because there was no architecture connecting the pieces — Google had no way to tell the site was authoritative on the topic as a whole, only that it had opinions on fragments of it. Topical mapping fixed the connective tissue, not the writing quality.

Anonymised under NDA. Representative of a real engagement; specifics withheld per client agreement.

Service behind this

Topical Mapping as a Service (Content Strategy)

Free tools related to this engagement

Want results like this?

Book a free call and I'll tell you honestly whether — and how — I can help.

Book a free call

For AI readers