Blog

Answer engine optimization is the practice of making your content a source that AI assistants such as ChatGPT, Perplexity, and Google’s AI Overviews cite when they answer your buyers’ questions. For B2B SaaS, the work comes down to three things: letting AI crawlers reach your site, structuring pages so individual sections can be quoted verbatim as answers, and being unambiguous about what your product is and who it serves. It extends SEO rather than replacing it, and most of the underlying work overlaps. The evidence base is young, so treat what follows as a defensible starting point, not settled practice.

How AI assistants answer buyer questions differently from search results

A search results page gives your buyer ten links and lets them choose. An assistant gives them one synthesized answer with a handful of citations, and most of the time they never click through. That changes what you are competing for: not a ranking for a keyword, but selection as the source an assistant pulls a specific passage from.

Google’s documentation describes AI Overviews and AI Mode using a “query fan-out” technique, issuing multiple related searches behind the scenes and assembling the answer from a diverse set of supporting pages. In practice, a page that would never rank first for a head term can still get cited if one of its sections answers a sub-question cleanly.

Keep the volumes in perspective. In Ahrefs’ study of 3,000 websites, 63% received at least one AI-referred visitor, but AI referrals averaged about 0.17% of traffic, with ChatGPT, Perplexity, and Gemini sending 98% of it. The authors note the real numbers are probably higher because some assistants strip referrer data, but this is still a small channel today. The case for working on it now is that the buyers who arrive this way tend to be deep into evaluation.

What actually influences citations

Three things show up consistently across platform documentation and independent testing.

Structure and extractability. Assistants quote passages, not pages. A section with a descriptive heading, a direct answer in the first sentence or two, and evidence immediately after is easy to lift. A 400-word paragraph that buries its point is not. The test I use: could this section be quoted verbatim as an answer and still make sense?

Entity clarity. Assistants need to know what your product is, what category it sits in, and who it is for. If your site describes the product five different ways across five pages, you make that harder. One plain-language definition, used consistently, helps retrieval and attribution alike.

Basic technical eligibility, not special markup. Google says appearing in its AI features requires nothing beyond normal indexing and snippet eligibility, and explicitly advises against creating special AI files or schema for the purpose. Independent data points the same way: when Ahrefs tracked 1,885 pages that added JSON-LD schema, AI citations barely moved on any platform, even though cited pages were about three times more likely to carry schema in the first place. That looks like correlation with overall site quality, not cause. I dig into this in whether schema markup helps AI citations.

A practical starter checklist for a B2B SaaS site

• Confirm AI crawlers such as GPTBot, ClaudeBot, and PerplexityBot are not blocked by robots.txt, your CDN, or your firewall. Check server logs, not just config files.
• Rewrite your top ten organic pages so every H2 section opens with a direct answer to the question its heading implies.
• Make each section self-contained: claim, evidence, source. Assume it will be read out of context, because it will be.
• Write one canonical definition of your product and category, and use it on the homepage, about page, and key product pages.
• Cover the comparison and alternatives questions buyers actually ask assistants, honestly, including where you are not the right fit.
• Keep normal SEO hygiene. A page that is not indexed and snippet-eligible is not a citation candidate at all.

How to measure whether it works

Referral traffic. Track sessions from assistant domains like chatgpt.com and perplexity.ai in GA4, monthly. I walk through the setup in how to track AI referral traffic in GA4. Note that Google folds AI Overviews traffic into the ordinary Web search type in Search Console, so you cannot fully isolate it there.

Citation checks. Keep a list of 20 to 30 real buyer questions, ask them in the major assistants each month, and log whether you are cited. Crude, but it measures the actual thing you are optimizing.

Conversion quality. Segment AI-referred visitors and watch what they do. Ahrefs reported that 0.5% of its visitors from AI search drove 12.1% of signups in a 30-day window. That is one company’s funnel, and the authors themselves caution against generalizing, but it fits the intuition that assistant-referred visitors arrive pre-qualified.

The honest limits of the evidence

Most published AEO evidence is correlational, single-company, or vendor-produced. Platforms change their retrieval systems without notice, so what correlates with citations this quarter may not next quarter. Referrer stripping means traffic data undercounts by an unknown amount. And nobody, including the platforms, can tell you how to guarantee a citation.

I still think the work is worth doing, because nearly everything on the checklist is also just good content practice. Clear structure, direct answers, consistent product definitions, and honest comparison pages help human readers and conventional rankings whether or not an assistant ever cites you. That makes AEO a low-regret bet, which, given the state of the evidence, is the right kind to make.

---

Structure a B2B SaaS keyword portfolio the way a portfolio manager structures positions: group keywords into three intent buckets (category, problem, and comparison terms), weight each bucket by expected return (volume x intent x winnability), and rebalance on a fixed schedule. Review rankings monthly and the portfolio itself quarterly. Cut any position that has not moved in two quarters and reallocate the effort to the buckets that are paying.

Group keywords by intent: the three position types

Every keyword sits somewhere on the path from “I have a problem” to “I am choosing a vendor.” Ahrefs’ guide to search intent splits queries into informational, navigational, commercial, and transactional, and notes that many queries mix intents, so treat any classification as a starting point rather than a law. For B2B SaaS, three working buckets cover most of the ground:

• Category terms describe the software category itself, like “call center software.” They carry buying intent, but everyone knows it, so they are the most expensive positions on the board.
• Problem terms describe the pain before the buyer knows the category exists, like “agents keep missing inbound calls.” Finding them requires actually talking to customers, which is why most teams skip them.
• Comparison terms include competitor names and alternatives queries. They convert best of all, because the searcher has already decided to buy and is choosing between shortlisted vendors.

Most teams overinvest in category terms because they are obvious, and underinvest in problem terms because they are not. The fix is mechanical: for every category page, commission two problem-led essays that link to it.

Weight positions by expected return

A flat list treats every keyword as equally important, which means nothing is. A portfolio assigns each position a weight, and the weight is a product of three factors:

• Volume: how many people search for it. Necessary, but the least interesting factor. Problem terms often show near-zero reported volume and still source real pipeline.
• Intent: how close the searcher is to money. A hundred visits from an alternatives query are worth more than ten thousand from a definitional one.
• Winnability: whether you can realistically reach the top of the page. Semrush defines keyword difficulty as a 0-100 measure of how hard it is to earn a top position, and Ahrefs adds the caveat that the score is derived largely from backlinks to the current top-ranking pages, so read it against your own site’s authority, not in a vacuum.

Multiply the three and the ranking of your buckets usually inverts. Comparison terms, small in volume, come out heavily overweight. Category terms, big and difficult, get a smaller allocation than instinct suggests. That is what weighting means: effort follows expected return, not search volume.

Rebalance on a schedule: the monthly review

Rankings get reviewed monthly; the portfolio itself gets reviewed quarterly. Keep the two separate, because they answer different questions.

The monthly review is a read, not a rewrite. Pull rankings, organic traffic, and signups or demos per bucket. Note what moved, flag what has been flat, and check whether new competitors entered the results for your comparison terms. Resist the urge to edit pages every month: positions need time to mature, and constant tinkering makes it impossible to tell what worked. The pull itself is mechanical, which makes it exactly the kind of work an AI SEO agent can run on schedule while you keep the judgment calls.

The quarterly review is the rebalance. This is where you reallocate: commission new problem essays for category pages that lack them, add comparison pages for competitors that started showing up in your deals, and decide which flat positions go on the kill list.

When to cut a position

The rule is deliberately blunt: a page that has not moved in two quarters gets cut, and the effort gets reallocated. Sunk cost is the portfolio’s enemy. A page you spent forty hours on is not an argument for keeping it.

Cutting does not always mean deleting. Diagnose first:

• Consolidate when two of your own pages compete for the same query and split the ranking signal between them. That is keyword cannibalization, and one merged page usually outperforms both of the pages it replaced.
• Reposition when the page is sound but aimed at the wrong query. Rewrite it against a different keyword and restart its two-quarter clock.
• Retire when the page exists only to hold a keyword. Google’s helpful content guidance is explicit that its ranking systems reward content made to benefit people, not pages manufactured to occupy a search result. Delete it, redirect it, move on.

Why this beats a flat keyword list

A flat keyword list only grows. Nobody deletes rows from a spreadsheet, so it accumulates every keyword anyone ever suggested, all implicitly equal, none with an owner or a review date. Effort gets allocated to whatever was added most recently or argued for most loudly.

A portfolio forces three questions a list never asks:

• What intent does this keyword serve, and which bucket does it belong to?
• What return do we expect, and what else could the same effort buy?
• When will we admit it failed?

Portfolio managers get fired for holding losers out of attachment. Hold your keyword sheet to the same standard: grouped by intent, weighted by expected return, reviewed on a schedule, and pruned without sentiment.

---

No attribution model tells you what caused a deal. Each one is a map: a simplified, deliberately distorted picture of a messy buying journey. So the useful question is never which model is right, because none of them are. The practical move is to run two or three, act where they agree, investigate where they disagree, and check any large budget decision against stronger evidence, such as an incrementality test or direct customer feedback.

Every common model is biased in a known way

Attribution models do not measure credit. They assign it, according to a rule somebody chose. Each rule distorts in a predictable direction:

• First touch gives all credit to the earliest recorded touchpoint. It overvalues top-of-funnel content and any channel that harvests cheap first clicks.
• Last touch gives all credit to the final touchpoint. It overvalues brand search, direct, and whatever sits closest to the demo form, and it erases the work that created the demand in the first place.
• Linear splits credit evenly across every touch. That sounds fair, but it is really a refusal to decide: strong signals get diluted and weak ones get inflated.
• Position-based models hard-code the assumption that the first and last touches matter most, typically weighted 40/20/40. The weighting is arbitrary, not observed.
• Data-driven attribution uses machine learning across converting and non-converting paths, which is genuinely better. But it can only redistribute credit among touchpoints your tracking can see, so it inherits every blind spot in your setup.

Why “which model is right” is the wrong question

A subway map and a topographic map of the same city disagree almost everywhere, and both are useful. Neither is the city. Attribution models work the same way: each answers a narrow question about observed digital clicks, and none of them observes the territory where B2B deals actually form – a colleague’s recommendation, a podcast mention, a Slack community thread, a conversation at a conference.

The territory has a habit of embarrassing the map. When eBay paused its brand keyword ads in a large-scale field experiment, researchers found the ads had no measurable short-term benefit: buyers who would have clicked the ad simply arrived through organic search instead. Click-based reports had made that same spend look like some of the company’s best-performing. If your last-touch report says brand search is your top channel, you may be looking at the model’s bias, not the channel’s contribution.

Use models as directional instruments

A compass does not tell you where you are, but it keeps you walking in a consistent direction. Use attribution the same way:

• Triangulate. Run at least two models side by side. Where they agree a channel is working, trust the signal more. Where they diverge, investigate – divergence usually flags early-funnel activity that last-click erases.
• Ask humans. A free-text “How did you hear about us?” field on every form routinely surfaces channels no model can see. Read the raw answers, not just the categorized rollup.
• Test incrementality where it counts. For your one or two largest budget lines, run a holdout: pause the channel in one region or segment and watch what actually changes. It is the only method here that measures cause rather than assigning credit.
• Anchor everything to revenue. A model arbitrating credit for form fills optimizes the wrong thing entirely; this is the same logic behind reporting on pipeline instead of MQLs.

What changed with GA4 and privacy

Google has quietly conceded much of this argument. As of November 2023, GA4 removed the first click, linear, time decay, and position-based models entirely, leaving data-driven attribution and last-click variants. The models most obviously disconnected from buying reality are simply gone from the product.

Privacy changes pull in the same direction. When visitors decline cookies, GA4’s behavioral modeling for consent mode uses machine learning to estimate their behavior from similar users who accepted. Portions of your reports are now modeled rather than observed – a reasonable response to consent requirements, and one more reason to treat the numbers as estimates, not ground truth. Meanwhile, new territory keeps appearing faster than the maps update: AI assistants now send real referral traffic that default channel groupings handle poorly, which is worth tracking deliberately in GA4.

Practical guidance for a B2B team

You do not need a data science team to do this well. You need discipline about what the numbers can and cannot say:

• Pick one primary model and write its known bias directly on the dashboard, so nobody forgets what they are reading.
• Review data-driven against last click quarterly. Reallocate budget only where they agree, and treat disagreement as a research prompt, not an error to reconcile.
• Keep a self-reported attribution field on every form and read it monthly alongside the model output.
• Before scaling or cutting a major channel, run a simple holdout test rather than arguing about credit weights.
• Match your lookback window to your sales cycle. A 30-day window on a six-month cycle guarantees the map is missing most of the journey.

A model that is wrong in a known way is still useful. A model mistaken for reality is how budgets get misallocated. Keep the map. Just stop billing the territory for it.

---

Most B2B SaaS teams should publish fewer case studies and make each one much deeper. A wide-and-shallow library – twenty logos, three paragraphs each, a pull quote – gets skimmed and forgotten, while one 2,000-word story with real numbers, named failure points, and decision context earns trust that no logo wall can. Buyers now run most of their evaluation without talking to sales, so the case study has to do the work a reference call used to do. One deep case study per segment, shipped one per quarter, is the better trade.

Why wide-and-shallow case study libraries underperform

The standard case study is a template: a challenge, a solution, a percentage improvement with no baseline, and a quote from a VP who clearly did not write it. Twenty of these side by side do not read as twenty proofs. They read as one ad, repeated. A buyer skims one, learns nothing they could not have guessed from the homepage, and leaves.

Skepticism is the default state of a B2B evaluator. Gartner’s sales survey found that 69% of B2B buyers report inconsistencies between what a vendor’s website says and what its sellers tell them. Generic customer stories feed that doubt instead of resolving it. A claim like 40% faster onboarding with no starting point, team size, or timeline is unverifiable, and buyers treat unverifiable claims as marketing. There is a search cost too: twenty near-identical pages compete with each other for the same handful of queries, and none is substantial enough to rank or be cited for anything specific.

What a deep case study actually contains

Depth is not length for its own sake. It is the presence of details a reader could check, or recognize from their own environment:

• Real numbers with denominators. Ticket backlog fell from 1,400 to 300 in nine weeks is believable. A bare 78% reduction is not.
• Decision context. Why the customer bought, what else they evaluated, who inside the account objected and why.
• Failure points. The integration that broke, the migration that ran long, the workaround that fixed it. Naming what went wrong is the strongest credibility signal available to a vendor.
• Named specifics. The stack, the team size, the rollout sequence, the time to first value.
• Operator voices. Quotes from the admin who ran the rollout, not only the executive who approved it.

A story with these elements reads like a colleague’s account instead of a brochure. That is the entire point.

How buyers actually use case studies

Modern B2B evaluation happens mostly out of the vendor’s sight. The same Gartner survey found 61% of B2B buyers prefer a rep-free buying experience. TrustRadius’s 2024 B2B Buying Disconnect research found that 71% of buyers went with the product that was already their first choice when they built a shortlist, which means your content does its persuading before anyone fills out a form. The same research found 56% of buyers talked to an existing user before purchasing. A deep case study is the scalable version of that conversation: it answers what a reference call answers – what actually broke, how long it really took, what the team looked like.

Case studies are also internal sales tools. Your champion forwards them to the CFO and the security reviewer to argue your case when you are not in the room. Marketers already know the format works: in the Content Marketing Institute’s 2025 B2B benchmarks, case studies and customer stories ranked among the top content types for producing results, and three quarters of B2B marketers used them. The format is not the problem. The execution is.

Depth earns citations, including from AI assistants

Specifics are quotable; generalities are not. A writer covering onboarding benchmarks can cite a backlog that fell from 1,400 tickets to 300 in nine weeks. Nobody links to significant improvement. The same logic now applies to AI assistants: when a buyer asks ChatGPT or Perplexity whether a product fits a mid-market team migrating off a legacy system, the engines favor pages with concrete, extractable facts – numbers, named integrations, described scenarios. Shallow case studies give them nothing to extract. Deep ones map directly onto the long-tail questions buyers actually ask, which is the core mechanic in our practical intro to answer engine optimization for B2B SaaS.

A practical production model: fewer per quarter, more access

The constraint on deep case studies is not writing capacity. It is access. So restructure the ask:

• One per quarter, one per segment. Map your two or three core segments and aim for one definitive story in each, refreshed as the numbers change.
• Trade volume for access. Instead of asking ten customers for a quote, ask one for ninety minutes with the admin who ran the rollout, a look at the real dashboard, and sign-off on specific numbers.
• Interview the skeptic. The person who argued against the purchase gives you objection-handling material no template produces.
• Retire the shallow ones. As each deep study ships, redirect the thin pages in that segment to it. Twenty weak pages dilute; one strong page compounds.
• Systematize the pipeline. Interview scheduling, transcript processing, approval tracking, and refresh reminders are exactly the repeatable work an automated content operations setup should carry, so human effort goes into the interviews and the storytelling.

The trade is fewer logos on the wall in exchange for stories buyers finish, sales sends unprompted, and machines cite. Make it.

---