SaaS · UK · Direct engagement
B2B SaaS:
from invisible to answer-engine cited.
Topical authority plus answer-engine optimisation (AEO): structured data, answer-first content, entity cleanup. Organic up 127% in five months, with citations in AI Overviews for money queries.
A UK B2B SaaS platform grew organic traffic +127% in 5 months. A direct engagement: topical authority built from a standing start, plus the AI-search layer (structured data, entity cleanup and answer-first content) so the product is cited by Google AI Overviews on commercial queries, not just ranked in blue links.
A UK B2B SaaS was invisible in classic search while its buyers had started asking AI engines about the category.
- Built a topical authority map and an answer-first content library
- Shipped site-wide structured data and entity cleanup
- Verified AI-crawler access and question-formed page structure
Result: +127% organic traffic in five months, with citations in AI Overviews on money queries
The visibility,
in two states.
| Before | After | |
|---|---|---|
| Organic traffic | Flat, pre-engagement baseline | +127% growth (5 months) |
| AI-search visibility | Invisible to answer engines | Cited in AI Overviews for money queries |
| How machines describe the product | Inconsistent product story across the web | One consistent story, structured data site-wide |
- Organic trafficBeforeFlat, pre-engagement baselineAfter+127% growth (5 months)
- AI-search visibilityBeforeInvisible to answer enginesAfterCited in AI Overviews for money queries
- How machines describe the productBeforeInconsistent product story across the webAfterOne consistent story, structured data site-wide
Invisible where
buyers actually look.
A B2B SaaS platform in the UK came to us directly with a pipeline problem dressed up as a marketing one. Nearly every qualified lead was arriving through paid channels or outbound: organic search, the channel that compounds instead of billing monthly, contributed almost nothing.
The deeper issue was visibility in the places buyers had moved to. Prospects researching the category were asking ChatGPT and reading Google AI Overviews. The product appeared in neither, nor in the classic results underneath them. The site had thin content, no coherent topical structure, and enough inconsistent naming that answer engines couldn't confidently say what the product even was.
The brief we agreed was specific: make organic a real pipeline channel, and make the brand citable by answer engines, measured against traffic and pipeline, not rankings for their own sake.
Authority first,
citations follow.
A topical map from a standing start
The questions buyers ask, clustered into topics the site could credibly own, sequenced by commercial value. Every piece published traced back to this map: no orphan blog posts, no content for content's sake.
Answer-first content
Each page opens by answering its own question in a form an engine can quote verbatim, then earns the depth underneath. The same structure serves a human skimming and a model deciding what to cite.
Schema and entity cleanup
Structured data across the site, and one consistent story about what the product is, told identically everywhere machines look. Entity confusion is the quiet killer of AI-search visibility. This is the unglamorous work that fixes it.
The answer-engine (AEO) architecture
Crawler access verified for the engines that matter, question-form headings, and passages an engine can quote as they stand: the discipline from our AEO and GEO services (answer-engine and generative-engine optimisation), built into the SEO programme rather than bolted on after.
Reporting tied to pipeline
A weekly review in Prism connecting rankings to sessions to signups, with AI-citation appearances tracked alongside classic positions, so progress was judged on the numbers the board cares about.
The decisionsThree forks, and the roads not taken.For the detail readers
Answer-engine visibility is new enough that most of the decisions here had no established playbook to follow. These are the calls that mattered.
Chase volume keywords, or build topical authority first?
Authority first. Depth across a tightly-defined topic set before breadth across a wider one.
Targeting the highest-volume terms directly, which is what a keyword tool recommends and what most plans do. For a site with no existing authority in the category, those terms are contested by sites that have it: the effort produces pages that rank on page four indefinitely. Depth in a narrower area is winnable; breadth in a contested one is not.
Optimise for classic rankings or for AI citation?
Both from one architecture: answer-first structure, schema and entity clarity serve blue-link rankings and answer-engine extraction simultaneously.
Treating AEO as a separate later workstream. It is a common framing, and it doubles the work. Retrofitting answer-first structure onto content written for a different shape means rewriting the content. The two are the same job if sequenced together and two jobs if not.
Publish faster with lighter pieces, or slower with deeper ones?
Slower and deeper. Fewer pages, each genuinely complete on its subject.
A higher-cadence content calendar. Volume is the easier plan to sell and the easier plan to report on: there is always something shipped. It also produces exactly the thin, consensus content that answer engines now absorb and answer directly, which means the traffic it earns is the traffic most at risk.
The work,
itemised.
The hard partsWhat this actually cost.A case study with no hard parts is a brochure
Entity cleanup was more work than it sounds and less visible than anything else in the engagement. Machines build confidence about what an organisation is from consistency across every place they read about it: the site, structured data, third-party profiles, the way the company describes itself in different contexts. Where those disagree, confidence stays low, and nothing about that disagreement is visible on the website itself. Finding and reconciling it is genuinely tedious and it does not photograph well in a monthly report.
The measurement lag was the harder management problem. A B2B SaaS sales cycle means content that ranks in month three may not attribute to a closed deal until month eight or later. For that first stretch, an ecommerce-style revenue-attribution report shows a programme that appears to be underperforming, while it is in fact working exactly as designed. Holding a plan through that window requires agreeing up front what will and will not be visible when.
Answer-engine citation is also not directly controllable in the way a ranking is. You can structure content to be extractable, make entity signals consistent, and answer questions completely. But the specific decision about what to cite belongs to a system nobody outside it can query. The accurate framing is that this work materially raises the probability of citation rather than delivering it on a schedule.
When this pattern
transfers, and when it doesn't.
Answer-engine work is being oversold across the industry right now. Here is where this specific approach genuinely fits.
This pattern transfers if
- You sell something with a considered, multi-stakeholder buying cycle rather than an impulse purchase.
- Your category has an established vocabulary buyers already search: you are competing for understood terms, not inventing one.
- You can wait two quarters before judging the programme on pipeline rather than on rankings.
- There is subject-matter depth in the business that content can actually draw on.
It probably doesn't if
- You need leads this month. Nothing in this approach is fast, and a paid programme is the right answer to an urgent pipeline gap.
- Your product is genuinely new enough that nobody is searching for the category yet. That is a demand-creation problem, and search follows demand rather than creating it.
- Nobody internally can spare time for subject-matter review. Content of this depth cannot be produced without it, and content without it is the thin kind this engagement deliberately avoided.
The services behind this result
The same programme, classic SEO with the AI-search layer built in, is how every search engagement here runs.
Want a result like this
on your own numbers?
A senior strategist records five minutes on your website: speed, search rankings, AI visibility, conversion leaks. Yours to keep, no strings.
Response in 48 hours · No retainer required · NDA standard
Last updated