Six months deep into AEO/GEO for a Series B SaaS and this is everything I've learned, tested, and still don't fully understand.
Been quietly working on answer engine optimization for a Series B agritech SaaS over the last several months. Started as an internal audit, turned into a full implementation. Sharing everything I've mapped so far i.e. what worked, what's still unclear, and what I'm genuinely curious about from people further along than me.
This is long. Worth it if you're actively building in this space.
A- The starting point viz. why Google rank means nothing for AI visibility
The company I was auditing ranked well on Google across their core category keywords. Decent traffic, solid backlink profile, clean technical SEO. Completely invisible in ChatGPT, Perplexity, and Gemini when buyers searched the same queries.
The gap isn't an anomaly. It's structural. Google rewards topical authority and backlink equity. LLMs reward entity clarity and off-site corroboration. Different trust signals entirely. A brand can rank #1 on Google and still be absent from every AI-generated answer in their category.
B - The On-site extraction architecture
This is where most AEO advice starts and stops. It's necessary but not sufficient on its own.
What actually moves citation probability on-site:
Research consistently shows ~44% of LLM citations pull from the first 30% of a page's content. Front-loading matters more than comprehensive coverage. Lead every section with the answer, follow with the proof. Never the reverse.
Headers should mirror exact prompts your ICP types into AI tools, not keyword targets, not some clever copy. If your buyer asks ChatGPT "how does X solve Y problem" your H2 should read exactly that way.
FAQ sections bolted at the bottom of pages don't work. The FAQ logic needs to be embedded in the body content structure itself. Each section functioning as an implicit question and answer.
JSON-LD schema for FAQPage, HowTo, and Article types genuinely helps. Not because Google cares, yet because it gives the LLM a pre-parsed semantic structure to extract from without ambiguity. Organisation schema with consistent NAP data across every page builds entity clarity.
llms.txt is worth implementing. Analogous to robots.txt but specifically for LLM crawlers lets you signal which content is highest priority for extraction. Still early but adoption is growing fast enough that ignoring it is a mistake.
robots.txt make sure you're not accidentally blocking AI crawlers. GPTBot, ClaudeBot, PerplexityBot all need explicit allowance if you've been aggressive with your crawl restrictions.
C- Off-site entity footprint
This is where most brands have the biggest gap and where the audit for the Series B company was most revealing.
LLMs triangulate brand legitimacy from independent third-party sources. If you only exist on your own domain, the model has nothing to corroborate you with and won't cite you confidently regardless of how well-structured your pages are.
What the citation environment mapping revealed: their competitors were being cited primarily through four source types viz. G2 and Capterra reviews, Reddit threads in niche subreddits, Crunchbase and Tracxn profiles, and long-form technical content on Medium. The company had minimal presence across all four.
The priority fix order matters by category. For B2B SaaS: review platforms first (G2, Capterra brands with active review profiles have meaningfully higher AI citation rates), structured entity data second (Crunchbase, Wikipedia if notability threshold is met), community presence third, long-form editorial fourth.
For developer tools the order shifts: GitHub presence and Stack Overflow tags move to the top. LLMs answering developer queries pull heavily from these sources.
Review velocity is a real signal. A detailed user review that says "this tool solved our API routing issues in three days" functions as a direct citable answer to a future prompt from someone asking Perplexity for API routing solutions. The review isn't just social proof it'll be your citation infrastructure.
D-Citation environment mapping
Before optimising anything, map what's actually getting cited in your category.
Run your target queries through ChatGPT and Perplexity. Don't search your brand, instead go on to search your category. Screenshot every cited source. Categorise them by source type. This gap map tells you exactly what you need to build, in what order, rather than optimising blindly.
The brands consistently winning citations in most B2B categories share a pattern: they have presence across at least 4-5 independent source types simultaneously. Single-source brands i.e. even with excellent on-site content, sometimes get bypassed.
E- What I've been experimenting with 'CBaaS architecture'
One thing I've been testing is building what I'd call Citation Banks viz. single content nodes engineered to satisfy multiple related query intents simultaneously rather than one piece per keyword.
The logic: LLMs extract semantic tokens rather than reading pages linearly. A single well-architected piece can serve as the cited source for an entire family of related queries. Every successful retrieval strengthens that node's citation weight for adjacent queries. The compounding is real, a piece that answers 6 related intents accumulates citation weight 6x faster than 6 separate pieces each answering one.
Construction requirements are different from standard SEO content. Query clustering before writing via mapping the entire family of intents you're targeting. Semantic bridges between sections that help the LLM understand the relationship between adjacent questions. Front-loading the most critical answers in the first 30% of the document.
Still testing this properly but early signals from the Series B implementation are promising.
F- The founder content signal, something I wasn't expecting
One finding that surprised me: founder-authored content was getting cited significantly more than equivalent brand content across the same topics.
The mechanism makes sense in retrospect. LLMs are trained heavily on conversational, human-written content i.e. Reddit threads, technical blogs, build-in-public posts. Authentic founder voice pattern-matches to this training data. Polished brand copy pattern-matches to advertising, which retrieval systems treat with skepticism.
A founder documenting a real product decision including the wrong assumptions, the pivot, the failed experiment, creates context-rich content that retrieval systems extract for "how-to" and "best practice" queries. The specificity and honesty is what makes it retrievable, not the polish.
Have been calling this Thought Leadership as a Service internally viz. the systematic documentation of a founder's building journey structured specifically for LLM extraction rather than human readers. Shifting thought leadership from PR vanity metric to data infrastructure.
G-Entity velocity, what I still don't fully understand
This is where I have observations but incomplete theory and would genuinely value input from people further along.
Entity velocity seems to matter, the rate at which new citation signals are accumulating across independent sources. A brand that optimised six months ago and went quiet appears to lose citation ground over time even if their content hasn't changed. The retrieval system seems to interpret signal stagnation as entity decay.
What I can't fully quantify: the half-life of a citation signal. How quickly does a G2 review or a Reddit thread decay in citation weight? Is it uniform across source types or does it vary? Does a Wikipedia entry decay more slowly than a Reddit thread because of perceived permanence?
If anyone has data or even directional observations on this I'd genuinely find it useful.
What's still unclear to me
A few things I haven't been able to resolve cleanly:
How much does llms.txt adoption actually move citation probability right now versus six months from now as crawler support matures?
For brands in genuinely niche B2B categories with low Reddit presence, is community seeding the right answer or is there a faster path to off-site entity corroboration?
Does author entity weight on Medium (follower count, publication history, external links to author profile) affect citation probability of articles published there? Or is it purely content and domain level signals?
How do retrieval systems handle contradictory information across sources — if your G2 reviews describe your product differently from your homepage, does that create citation ambiguity or does one source type override?
Happy to share more