AEO/GEO Playbook 2026: Your Next B2B Buyer Is a Machine

Every claim below is labelled MEASURED, VENDOR-REPORTED, PROJECTION, or ANECDOTE, and sourced. Anything that could not be verified is named in Appendix B rather than quietly dropped.

Part 0 — Executive Brief

Something moved, and most companies have not noticed because the thing that moved does not show up in any dashboard they currently look at. The front door to B2B software discovery has shifted. In G2's March 2026 survey of 1,076 buyers, a figure that is VENDOR-REPORTED and should be read as such, 51% now say they start their research in an AI chatbot more often than they start it in Google. In April 2025 that number was 29%.

Here is what did not move, and this is the part the hype cycle keeps burying. AI-referred traffic is still roughly 1% to 3% of sessions for most B2B sites. Conductor's 2026 AEO/GEO Benchmarks Report, built on 13,770 enterprise domains and 3.3 billion sessions between May and September 2025, puts it at 1.08% on average, rising to 2.80% in IT, and growing at roughly one percentage point per month.

Hold those two facts next to each other, because the tension between them is the whole story. Half your buyers are starting in a chatbot, and yet almost none of your traffic arrives from one. That is not a contradiction. It is a description of a channel that has stopped delivering clicks and started delivering something else: shortlists. The shift that matters is not traffic volume. It is that consideration sets now form inside model outputs, and being cited is quietly replacing being clicked as the unit of distribution.

Which means the real risk of doing nothing is not a slow bleed in sessions. It is silent exclusion. You get left out of the shortlist, and there is no sales call at the end of it in which you can recover the miss, because there was never a call. You simply were not named. G2 found that 33% of its buyers purchased from a vendor they had not been familiar with before an AI surfaced it. That is the mechanic in one number: unfamiliar vendors are getting into consideration sets, which means familiar ones are getting pushed out of them.

So, Monday morning. Two moves. First, run a buyer-prompt audit: 30 to 50 real prompts, across four engines. Second, and more urgently, check whether AI crawlers can even read your site without executing JavaScript. If your site is a client-side-rendered single-page app, you may already be invisible to ChatGPT, Claude, and Perplexity, and no amount of content strategy will fix that. That one fact outranks everything else in this report, and if you read nothing past this paragraph, go check it.

Part I — What Actually Changed (and What Didn't)

The vocabulary, defined once and precisely

Before anything else, the terms, because this field is thick with people using the same words to mean different things.

An answer engine is a system that responds to a query with a synthesized answer instead of a ranked list of links. That includes ChatGPT with search, Perplexity, Google AI Overviews and AI Mode, Microsoft Copilot, Gemini, and Claude. AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) are the overlapping practices of getting your content surfaced and cited inside those answers. A citation is the source an engine attributes, quotes, or links to when it generates an answer. And agentic commerce is the use of autonomous AI agents to research, select, and, in narrow cases, actually transact on a buyer's behalf.

Keep that last distinction in your pocket. Almost every inflated claim in this space comes from blurring the line between an agent that researches and an agent that buys.

How much traffic does an AI Overview actually cost you?

The strongest single piece of evidence in this entire field is a randomized field experiment by Saharsh Agarwal of the Indian School of Business and Ananya Sen of Carnegie Mellon University's Heinz College, posted to SSRN on April 3, 2026 and revised on July 8, 2026. It is MEASURED and pre-registered with the AEA RCT Registry, which matters more than it sounds like it does.

They built a custom Chrome extension and ran it on 1,065 US desktop Chrome users recruited through Prolific between January 7 and February 10, 2026. What they found: organic outbound clicks fell 39.8% when an AI Overview appeared. Zero-click searches rose 34.5%. AI Overviews showed up in 42% of observed queries. And there was no improvement in self-reported satisfaction, in perceived quality, or in downstream engagement to compensate for any of it.

This is the first causal evidence on the question, not merely correlational. It also settles a smaller argument: it corroborates the second-hand Eric Seufert claim (C2: roughly 40% click loss, roughly 41% AIO trigger rate) and upgrades it from a tweet into a MEASURED fact.

Pew Research Center, also MEASURED and non-vendor, triangulates the same direction from a completely different angle. Tracking 900 US adults across 68,879 Google searches in March 2025, Pew found that when an AI summary appeared, users clicked a traditional result 8% of the time, against 15% when no summary was present. Only 1% clicked a source inside the summary itself. Summaries triggered on 18% of searches. And 26% of AI-summary sessions ended without any onward click at all, against 16% otherwise.

Now the honest part, because the range of click-loss estimates in circulation is genuinely wide and pretending otherwise would be exactly the kind of vendor behavior this report is trying to inoculate you against. Pew implies roughly a 47% relative CTR reduction. Ahrefs measured a 34.5% drop across 300,000 keywords. Seer Interactive reported a 61% CTR drop. Authoritas found up to 79% for top-ranked news sites appearing below an Overview.

They diverge because they are not measuring the same thing. Different query mixes, informational versus commercial. Different windows. Different working definitions of what counts as a "click." The safe, defensible statement, and the one you should use in a board deck, is this: clicks fall materially, somewhere between roughly one-third and two-thirds, when an AI Overview is present.

Google says this is wrong. Is it?

Google publicly disputes the traffic-destruction narrative, and its objections deserve a hearing rather than a dismissal.

A Google spokesperson called the Pew queryset "flawed" and "skewed," argued that AI features open new opportunities for people to connect with websites, and insisted the company sends billions of clicks to websites every day. Former Bing executive Duane Forrester independently raised a related point, questioning what a roughly 66,000-query sample can really say about a system handling something on the order of 500 billion queries a month.

Google's strongest methodological objection is real, and it is worth stating plainly: Pew compared March user sessions against April-scraped results, and AI outputs are dynamic and personalized, so the two do not cleanly line up.

But that objection is precisely the one the Agarwal and Sen design was built to defeat. A randomized field experiment inside live browsing isolates causation in a way an observational comparison cannot. So the adjudication is this: the direction, that clicks fall when an AI Overview appears, is now MEASURED and causal. The exact magnitude remains a range. Anyone quoting a single precise percentage as settled is overreaching.

Why there is no such thing as "AI search"

This is the central error running through most of the existing literature, and it will cost you money if you inherit it: do not collapse the engines into one abstraction called "AI search." They do not agree with each other.

Profound's cross-lingual analysis found a Jaccard hostname overlap of just 0.15 to 0.34 between languages on the same engine, and that figure is VENDOR-REPORTED. Read it as evidence that the source set is unstable, not as a cross-engine number. Profound separately found only 11% domain overlap between ChatGPT and Perplexity across 100,000 prompts. A BrightEdge analysis put pairwise cross-engine citation overlap in a 16% to 59% band.

That range also resolves a widely circulated anecdote. The Reddit claim that engines agree only about 21% of the time (C3) is an ANECDOTE, n=1, anonymous. It is directionally plausible, and it should not be cited as fact. The published measured overlap sits in an 11% to 59% band, and that is the range to use.

The operational consequence recurs in every section that follows, so absorb it now: a single blended "AI visibility score" is a lie. There is no such number. Measurement has to be per-engine, or it is measuring nothing.

Are agents actually buying your software?

This is the weakest leg of the whole thesis, which is exactly why it deserves the most careful handling rather than the most enthusiastic.

Agent-assisted research is real, and it is now common. 6sense's 2025 Buyer Experience Report, published November 12, 2025 with n=3,986 global B2B buyers, found that 94% of buyers report using LLMs during their buying process. And yet, in the same study, those buyers still averaged 16 interactions with the winning vendor, unchanged year over year. Read that pair of findings together. The research got faster and more machine-mediated. The buying process did not get shorter.

Agent-executed purchase in B2B, by contrast, is rare, narrow, and nascent.

The claim you have seen reposted a hundred times, that 90% of B2B buying will be agent-driven, does trace to a genuine primary source. Gartner's October 21, 2025 press release, "Gartner Unveils Top Predictions for IT Organizations and Users in 2026 and Beyond," states that by 2028, "90% of B2B buying will be AI agent intermediated," pushing over $15 trillion of B2B spend through AI agent exchanges (C4).

But look hard at the word "intermediated," because it is carrying an enormous load. It explicitly includes agent-assisted research. It does not mean autonomous purchase. This is a PROJECTION, and a forecast is not a finding. Never let anyone conflate agent-assisted research, which is real and common, with agent-executed purchase, which is rare and narrow.

The one place where agent-driven vendor selection is plausibly already true at scale is developer tooling, and I come back to that in Layer 5.

Hype-vs-Substance Ledger

Part II — How AI Engines Actually Choose Who to Cite

This is the technical spine of the report. Every prescription later in the playbook rests on the mechanics described here, which is why none of it is shortcut. If you skim one part, do not let it be this one.

What is actually under the hood of each engine?

ChatGPT Search uses Bing's index as a core component. OpenAI's VP of Engineering confirmed as much in a launch-week AMA, saying "we use a set of services and Bing is an important one," and OpenAI told The Verge it relies on "a mix of search technologies," Bing among them. It supplements that with its own crawlers: OAI-SearchBot for indexing, ChatGPT-User for live fetch. The practical implication is one line long and worth acting on: if you are not in Bing's index, you may be invisible to ChatGPT.

Microsoft Copilot runs on the Bing index plus OpenAI models. That is a small piece of leverage most teams miss, because it means a strong Bing presence buys you coverage across two engines at once.

Perplexity operates its own crawler, PerplexityBot, building what Head of Search Alexandr Yarats has described as "a much more compact index optimized for quality," and it partners with third-party crawlers as well. Notably, it leans on classic information-retrieval methods, BM25, n-grams, and PageRank-like authority signals, rather than pure vector embeddings. Perplexity-User handles on-demand fetches. The exact third-party API mix is undisclosed.

Google AI Overviews and AI Mode use Google's core index along with a documented technique called query fan-out. Google's own "AI Features and Your Website" documentation states that both "may use a 'query fan-out' technique — issuing multiple related searches across subtopics and data sources." AI Mode runs on a custom Gemini. Google VP of Product Robby Stein described it as using "a 'query fan-out' technique," and Google's Head of Search, Elizabeth Reid, described it breaking a question "into different subtopics" and issuing "a multitude of queries simultaneously."

Gemini uses Grounding with Google Search, generating one or more search queries against Google's live index and returning inline citations. One detail with teeth: grounding does not use pages that disallow Google-Extended.

Claude web search is powered primarily by the Brave Search API. The evidence here is strong but circumstantial rather than confirmed: Anthropic added Brave to its subprocessor list on March 19, 2025, one day before launch; developer Simon Willison independently found a BraveSearchParams parameter inside Claude's search function; and image search is officially Bing. Anthropic has never confirmed Brave on the record, and this report does not pretend otherwise.

Engines retrieve passages, not pages

This is the structural insight that should change how your content is written, and it is not a stylistic preference. It is a description of the machinery.

Google's fan-out feeds "relevant 'chunks' — or passages — from pages" into its answers, as Olaf Kopp documented in Digiday in May 2025. Anthropic's own Contextual Retrieval research cut failed retrievals by 49% by restoring context to isolated chunks, which is direct evidence that Anthropic, too, thinks in chunks rather than in documents.

Follow that through to its conclusion. A page is decomposed before any part of it is used. Which means content has to be written as self-contained, extractable passages that survive being ripped out of their surroundings, because that is precisely what will happen to them. A beautifully argued 2,000-word essay whose key claim only makes sense in the context of the four paragraphs above it will lose to a plain, standalone paragraph that answers the question on its own.

On the merging step, multi-query systems typically combine results using Reciprocal Rank Fusion (Cormack et al., ACM SIGIR 2009). No engine has confirmed using RRF internally, so treat it as the standard technique for this class of system rather than as a disclosed engine fact.

The crawler distinction that makes companies invisible

This is the highest-leverage distinction in the entire report, and it is routinely fumbled. Each major vendor runs two separate families of bot, and confusing them will make your company invisible in live answers while still being trained on, which is the worst of both worlds.

Training crawlers are GPTBot (OpenAI), ClaudeBot (Anthropic), Google-Extended (Gemini training), CCBot (Common Crawl), Meta-ExternalAgent, and Applebot-Extended. Blocking these opts you out of model training. It does NOT remove you from live answers.

Search, retrieval, and user agents are OAI-SearchBot and ChatGPT-User (OpenAI), Claude-SearchBot and Claude-User (Anthropic), PerplexityBot and Perplexity-User, and Bingbot. Blocking these removes you from citations. OpenAI states plainly that sites opted out of OAI-SearchBot "will not be shown in ChatGPT search answers."

On compliance: OpenAI, Anthropic, Perplexity, and Google all publicly commit to honoring robots.txt for their named crawlers. Bytespider (ByteDance) and Perplexity's documented stealth fetches have both been observed ignoring it, and for those, only server-level, WAF-level, or CDN-level rules will work. One more piece of trivia that is not trivia: Google-Extended is a robots.txt token only, not a live user agent, and disallowing it does not affect your Googlebot ranking.

Because training and retrieval run on separate agents, you have a genuinely nuanced choice available. You can block GPTBot, ClaudeBot, and Google-Extended to opt out of training, while keeping OAI-SearchBot, Claude-SearchBot, and PerplexityBot allowed so you stay eligible for citation. The default recommendation for any company that wants AI visibility: allow all retrieval agents, decide training separately as a business question, and keep sensitive paths such as checkout, account, and admin blocked for everyone.

The JavaScript finding that outranks everything else

If there is one paragraph in this report worth forwarding to your engineering lead, it is this one.

Vercel's "The Rise of the AI Crawler" study, published December 17, 2024 with MERJ and built on first-party server-log data, concluded flatly that "none of the major AI crawlers currently render JavaScript." GPTBot fetched JavaScript files in 11.50% of requests and never executed them. ClaudeBot fetched JS in 23.84% of requests and never executed them either.

These bots parse the raw HTML they are first handed, and then they move on. There is no second render pass the way Googlebot has one. The exceptions are Gemini, which runs on Googlebot's infrastructure and therefore does render JS, and Applebot.

The consequence is blunt and expensive. A client-side-rendered single-page app is effectively invisible to ChatGPT, Claude, and Perplexity retrieval. If your headline, your body copy, your pricing, or your product detail is not present in view-source, it does not exist to these engines. Not "ranks poorly." Does not exist.

Server-side rendering, whether static or incremental, is therefore the single highest-leverage technical move in the entire playbook. Everything else in this document is downstream of it. One clarification worth keeping, because it saves unnecessary rebuilds: data embedded in the initial HTML as inline JSON or as a server-rendered payload still counts, even if it is not visible prose. What is lost is anything the browser assembles client-side after load.

Where do citations actually come from?

Reddit dominates, and it is worth understanding why before you decide what to do about it.

Semrush's June 2025 analysis of 150,000 citations across ChatGPT, Perplexity, Gemini, and Google AI Overviews, a VENDOR-REPORTED figure, put Reddit at 40.1% citation frequency, Wikipedia at 26.3%, and YouTube at 23.5%, with Google's own properties, Yelp, and Facebook also placing in the top tier.

That position was engineered, not stumbled into. Google signed a content-licensing deal with Reddit in February 2024 reported at roughly $60M a year, confirmed through Reddit's S-1, which disclosed data-licensing arrangements entered in January 2024 with an aggregate contract value of $203M. OpenAI followed with its own deal, and the roughly $70M a year figure attached to it is an inferred estimate rather than a confirmed one: it comes from Search Engine Land's rough math, derived from COO Jen Wong's disclosure that AI licensing accounted for around 10% of Reddit's roughly $1.3B 2024 revenue, minus Google's confirmed $60M. It has never been officially confirmed. Profound, separately, found Reddit to be the most-cited domain for Google AI Overviews and Perplexity, and the second-most for ChatGPT, across August 2024 to June 2025.

Now the complication, and it is a big one. The distribution varies wildly by engine, and it is volatile.

Yext's analysis of 6.8 million citations found Gemini leaning on brand-owned websites for 52.15% of its citations, ChatGPT leaning on third-party directories and consensus sources at 48.73%, and Perplexity leaning on reviews and industry expertise. Tinuiti's Q1 2026 data showed Reddit at roughly 5% of citations on ChatGPT, versus 0.1% on Gemini, versus roughly 24% on Perplexity. ChatGPT's Reddit citation rate reportedly collapsed from around 60% to around 10% within two weeks in September 2025, after Google removed the num=100 search parameter. Semrush also found LinkedIn weighted heavily for professional queries, at 14.3% of ChatGPT citations, 13.5% of Google AI Mode, and 5.3% of Perplexity.

Sit with that September 2025 collapse for a second. A 50-point swing in a fortnight, triggered by an unrelated change to a Google URL parameter. The durable lesson writes itself: source weights are unstable, so never bet a program on any one engine's current mix.

Do you need to rank on page 1 to get cited?

No, and it is not sufficient either, which is the answer to C9 and it goes both ways.

Ahrefs studied 15,000 prompts and found that only 12% of the URLs cited by assistants ranked in Google's top 10. Per-engine overlap ranged from roughly 28.6% at Perplexity down to roughly 2.1% at ChatGPT, per Semrush. Google AI Overviews are the exception, showing high correlation with traditional rankings for the obvious reason that they draw directly on Google's index.

Verdict: C9 HOLDS. The comfortable assumption that you can "just do SEO and GEO follows" is only partly viable, and mainly for Google's own surfaces. It does not transfer to ChatGPT, Claude, or Perplexity. If your entire AI strategy is a rebranded SEO retainer, you are covering one engine and hoping about the rest.

What we do not know: non-software B2B

Nearly all published citation research covers SaaS, ecommerce, or B2C. For industrial manufacturing and professional services, B2B-specific citation-distribution evidence does not exist at scale. That is a visible and important gap, and the responsible thing is to name it rather than paper over it.

So do not silently import the Reddit-dominant SaaS distribution into, say, industrial component sourcing, where trade publications, standards bodies, and distributor catalogs almost certainly carry different weight. This is unmeasured. Saying so is more useful to you than guessing well.

What demonstrably moves citation

The foundational academic work here is Aggarwal et al., "GEO: Generative Engine Optimization," published on arXiv in November 2023 and presented at KDD 2024, out of Princeton, the Allen Institute for AI, Georgia Tech, and IIT Delhi. It is built on GEO-bench, a benchmark of 10,000 queries, and it is MEASURED.

The finding: adding citations, quotations from relevant sources, and statistics boosted source visibility by up to 40% across queries. The best methods improved Position-Adjusted Word Count by 41% and Subjective Impression by 28%. Keyword stuffing, the reflex that a decade of SEO trained into every content team in the market, produced almost no lift at all.

This is the cleanest evidence in the field of what actually works, and, unusually for this space, it was not produced by anyone selling a fix.

Three things everyone is doing that the evidence does not support

llms.txt does nothing for citation. This is C8, it is decision-critical, and it is resolved. Google's John Mueller stated that no AI service uses it, noting that you can see in server logs that they "don't even check for it," and compared it to the long-discredited keywords meta tag. Gary Illyes confirmed at Search Central Live in July 2025 that Google "does not support it and has no plans to." Google's own AI optimization guide, updated June 15, 2026, says you "don't need to create new machine readable files, AI text files, markup, or Markdown" to appear in generative AI search. Ahrefs analyzed 137,000 sites and found that 97% of llms.txt files received zero requests in May 2026. Otterly logged just 84 of 62,100 AI-bot requests, 0.1%, hitting the file. Publishing one is a cheap, low-risk agent-readiness bet if you sell an API-heavy or docs-heavy product. It is NOT a citation lever, and selling it as one is malpractice.

Schema.org is largely cargo-culted for AI. Google's "AI Features and Your Website" states that there is "no special schema.org structured data that you need to add" in order to appear in AI Overviews or AI Mode. Structured data does help entity understanding and accuracy, and it remains worthwhile for all the SEO and knowledge-graph reasons that already existed before any of this. But there is no controlled evidence that it directly lifts AI citation. Do it for entity clarity. Do not do it as a GEO hack.

Keyword optimization on its own produced near-zero citation lift in the GEO paper. One honest correction to a claim you will see made in this space, including in earlier drafts of this report: the same paper found that fluency optimization did measurably help. So this is not a licence to write badly. It is that polish alone does not earn the citation — statistics, quotations, and citations do.

Part III — The Playbook (Six Layers, in Dependency Order)

The layers are ordered by dependency, not by preference. Skipping to the interesting ones is the most common way teams waste a year.

Layer 0 — Diagnose: the buyer-prompt audit

This layer gives you a replicable baseline of where you actually appear in AI answers, which almost nobody has and everybody assumes.

Build 30 to 50 real buyer prompts spanning five intent classes: category discovery ("best X tools"), problem-first ("how do I solve Y"), comparative ("A vs B"), validation and alternatives ("alternatives to Z"), and procurement (pricing, security, compliance). Run every prompt across at least four engines: ChatGPT, Perplexity, Google AI Mode, and either Gemini or Copilot.

For each result, record six things: whether you were mentioned, whether you were cited, your position, the sentiment of how the engine described you, the source URL the engine cited, and which competitors were named alongside you.

To verify, repeat monthly with the same prompt set and log the drift. What you end up with is a citation-gap matrix, and the single most actionable column in it is the source URL, because it does not merely tell you that you are losing. It tells you exactly which surface to go win: a specific Reddit thread, a specific G2 page, a competitor's comparison post. That is the difference between a diagnosis and a to-do list.

Cost: one to two days a month done manually, or a tool, which is Layer 6.

Layer 1 — Crawlable

If the bots cannot fetch or render you, nothing downstream counts. Everything else in this playbook is a rounding error until this is true.

Three moves. First, audit robots.txt and explicitly allow OAI-SearchBot, ChatGPT-User, PerplexityBot, Claude-SearchBot, Claude-User, and Bingbot, deciding your training-crawler policy for GPTBot, ClaudeBot, and Google-Extended as a separate question. Second, check your CDN and WAF, because Cloudflare's "Block AI bots" toggle overrides robots.txt entirely, and this is where the damage usually hides. ParseAI research analyzing roughly 3,000 mostly US and UK B2B SaaS and eCommerce sites found that 27% block at least one major LLM crawler, and that most of that blocking happens at the CDN or WAF layer rather than through robots.txt, reported via ziptie.dev. Third, confirm your content is server-side rendered, because if key content is not in view-source, AI crawlers cannot use it.

To verify, do not trust the config file. Pull server logs and confirm that OAI-SearchBot, PerplexityBot, and ClaudeBot are actually fetching 200s rather than 403s.

Cost: 0.5 to 2 engineer-days. This is the cheapest, highest-return work in the entire document.

Layer 2 — Parseable

Engines retrieve passages, not pages, so the unit of content design is the passage.

Structure content as self-contained, answer-first blocks with question-shaped headings. Use tables and lists for comparative facts, because comparative facts are what buyer prompts ask for. Make sure every passage stands alone without needing the surrounding context to make sense.

Then maintain the canonical fact surfaces that every B2B buyer-agent goes looking for: pricing, integrations, security and compliance, comparisons, and docs, all of them in crawlable HTML. Keep your entity records consistent across Wikipedia and Wikidata where genuinely warranted, Crunchbase, and a consistent sameAs. On schema: add it for entity clarity and accuracy, not as a citation lever. On llms.txt: treat it as optional agent-readiness for docs and API products only, with no citation effect.

To verify, run the test that matters. Paste a page URL into a coding agent and ask it a buyer question. If it answers correctly using only your content, your passages work. If it hedges or hallucinates, they do not.

Cost: ongoing content operations rather than a project.

Layer 3 — Citable

The content model itself changes here. The old chain was keyword, then click, then convert. The new chain is question, then answer, then citation. Content built for the first chain does not perform in the second, which is why so many well-run content programs are quietly producing nothing.

Publish answer-first content carrying concrete statistics, named sources, and direct quotations. Those are the GEO paper's three proven levers, and they are proven in the only non-vendor study in the field.

Original data is the highest-leverage citation asset you can build, and the reason is mechanical rather than aspirational. A proprietary benchmark or survey supplies a number that exists nowhere else, and engines quote numbers. If you own the only number, you own the citation.

And stop producing thin listicle-bait and commodity 1,500-word SEO filler. The GEO paper shows keyword tactics do not earn citations, and Gaetano DiNardi's point lands hard here: AI is "the great neutralizer" of the listicle playbook, because it simply summarizes everyone's listicle and then recommends the competitors named inside it. You wrote the article. It recommended your rivals.

To verify, watch citation count and position in your Layer 0 matrix.

Cost: this reallocates your existing content budget rather than adding to it, which makes it one of the easier internal arguments to win.

Layer 4 — Present (the distributed citation footprint)

Here is the uncomfortable part. Engines pull heavily from third-party surfaces you do not own and cannot control: Reddit at 40.1% of citations per Semrush, review platforms including G2, Capterra, TrustRadius, and Gartner Peer Insights, plus YouTube, Wikipedia, "best X" listicles, and comparison pages.

So the work is to earn genuine presence wherever your buyers' questions actually get answered. Authentic Reddit participation. Current, complete review-platform profiles. YouTube explainers. Accurate inclusion in third-party listicles. Kevin Indig's research shows that web-search position drives LLM citation, and DiNardi's own conclusion, reading it, is that a brand cannot "bulldoze" its way into recommendations for a topic it has no recognition for. You cannot buy your way past the recognition problem. You can only build past it.

And this is where the line sits: legitimate participation ends where manufactured citation begins, which is Part V and is not a soft warning.

To verify, track share of voice in your target subreddits and review categories inside the Layer 0 matrix.

Cost: months of authentic community effort. This one costs time, not money, which is precisely why most companies will not do it and why it compounds for the ones that do.

Layer 5 — Transactable (scoped honestly)

Where agents can act, being machine-buyable matters. That is the whole case, and it needs a reality check bolted directly to it: this is real today mainly for developer tooling and self-serve SaaS. For most B2B, it remains forward-looking.

If it does apply to you, expose a public API, an MCP server (Anthropic's Model Context Protocol, donated to the newly formed Agentic AI Foundation in December 2025), machine-readable pricing, structured product data, and docs an agent can actually act on.

The rails genuinely exist. Google's AP2, the Agent Payments Protocol, launched September 16, 2025 with more than 60 partners including Mastercard, PayPal, Coinbase, and American Express. OpenAI and Stripe have ACP. MCP handles tool access. But B2B autonomous purchase remains nascent, and the single most expensive mistake available in this section is to confuse the existence of rails with the existence of buyers riding on them.

To verify, ask a concrete question: can a coding agent complete a real task using only your public surfaces?

Cost: product and engineering investment, and it is justified only where agent-led adoption is genuinely real for your category. If it is not, this layer is a distraction dressed as a strategy.

Layer 6 — Measured (never a blended score)

Because engines overlap with each other only 11% to 59% of the time, a single "AI visibility score" is meaningless by construction. Track per engine or do not bother.

What is instrumentable today: Bing Webmaster Tools' AI Performance report, launched February 2026 and expanded in June 2026 with Intents, Topics, Citation Share, and Compare, shows citation counts and grounding queries for Copilot and Bing AI. This is the first first-party AI citation data from any major engine, and it confirms C10, that Microsoft now reports AI-search traffic to site owners, as HOLDS. Its limits are real, though: it covers only the Microsoft ecosystem and carries no click data. Alongside it you have GA4 referral tracking for chatgpt.com, perplexity.ai, gemini.google.com, and copilot.microsoft.com, plus Cloudflare AI-crawler analytics and raw server logs. Google Search Console began surfacing AI Mode and AI Overviews impressions in June 2026, which gives impressions only, with no citation detail and no click data.

What is not instrumentable: which competitors get cited alongside you, outside of dedicated tools, and most of the dark funnel, meaning the prospect who asks ChatGPT, comes away with your name, and then arrives via direct or branded search with no referrer attached. That dark funnel is the reason AI sessions look microscopic in GA4 while your pipeline visibly moves. If you judge this channel by referral volume alone, you will conclude it does nothing, right up until a competitor owns the shortlist.

The metric set that replaces page views and MQLs: per-engine share of voice, citation count and position, prompt coverage, the sentiment of how the AI describes you, branded-search lift, direct-traffic lift, and self-reported attribution, the humble "how did you hear about us" field that suddenly matters again.

On tooling, and note that these are all VENDOR tools, none of them can see click-through, and each has blind spots: Profound (entry tier from around $99 a month, rising steeply for multi-engine coverage), Peec AI, Ahrefs Brand Radar (around $699 a month for full platform access), Semrush's AI Visibility Toolkit (around $99 a month per domain, and it tracks ChatGPT, Google AI Mode, Gemini, and Perplexity — not Claude or Copilot), Otterly (from $29 a month), plus AthenaHQ, Scrunch, Evertune, and Goodie. Every price here was checked in July 2026 and they move constantly, so read them off the vendor's own page before you budget.

The build-versus-buy line is clean. A small team can run Layer 0 manually alongside Bing WMT and GA4 for nothing. Buy a tool at the point where you need multi-engine tracking across more than roughly 30 prompts weekly and cannot spare the hours.

And a monthly AEO report contains: per-engine citation share, gap-matrix drift, new competitor mentions, sentiment changes, and AI-attributed pipeline. Not sessions.

Part IV — Sequencing, Cost, and Ownership

The 30/60/90 for a company starting from zero

Days 0 to 30, crawlability and baseline. Fix robots.txt and the CDN/WAF toggle, confirm server-side rendering, and run the first Layer 0 audit. Budget roughly 2 to 4 engineer-days plus 1 to 2 marketing-days. Time-to-signal: crawler fetches become visible in server logs within days, and Bing WMT citation data within weeks.

Days 31 to 60, parseable and citable. Restructure the top 10 to 20 buyer-intent pages into answer-first passages, build the canonical pricing, security, and comparison surfaces, and publish one original-data asset. Budget roughly 0.5 FTE of content work. Time-to-signal: the median time-to-first-citation for a new page is around 6 to 7 days according to Profound, but stable movement takes one to three months.

Days 61 to 90, present and measured. Begin authentic Reddit, review-platform, and YouTube presence, stand up per-engine tracking, and produce the first monthly AEO report. Community-driven citation change lags three to six months, so start it before you need it.

What this actually costs, and how long it takes to show up

Set expectations honestly, because the latency profile is the thing that gets programs killed at month two. Technical fixes show crawler response within days. Citation movement from content and third-party presence lags one to three months. Community-driven citation lags three to six months.

For a company of 1 to 20 people, the cost runs roughly 0.25 to 0.5 FTE ongoing, plus $0 to $400 a month in tooling. Which tells you where the real expense sits, and it is not the budget line. The expensive input is the authentic third-party presence, and it cannot be bought without incurring the risks in Part V.

Who owns this?

Not the SEO team alone, and the evidence on this is decisive rather than diplomatic. Roughly 40% of citations come from third-party surfaces that no SEO practitioner controls, and DiNardi argues persuasively that GEO is a cross-functional reputation problem rather than a siloed optimization task.

So assign a single accountable owner, either the head of growth or the head of marketing, and give them a standing claim on engineering time. The rationale is a split in leverage that no single function spans. The highest-leverage technical moves, server-side rendering and bot access, sit with product and engineering. The highest-leverage assets, original data and community trust, sit with content and brand. One owner has to coordinate both, and nobody else in the org is positioned to.

Part V — Risks, Failure Modes, and the Line You Don't Cross

Astroturfing and manufactured citations

This is C11, and it is the failure mode most likely to be sold to you as a service in the next twelve months.

Bloomberg, on July 6, 2026, documented brands seeding stealth Reddit content specifically to farm AI-chatbot citations, with agencies such as ReachLLM productizing the practice outright. Reddit's own AI now flags roughly 25,000 spam posts and comments a day and has cut spam exposure by around 20% year over year. Cornell Tech research shows that user-generated content can measurably manipulate AI research tools, which is exactly what makes the tactic tempting and exactly what makes it a target.

The legal exposure is not theoretical either. The FTC's rule against fake and manipulated reviews (16 CFR Part 465) creates real liability for planted reviews, although enforcement posture under the current administration is uncertain. The Consumer Review Fairness Act is often cited alongside it and does something different: it bans contract clauses that gag customers from leaving honest negative reviews, rather than penalizing the planting of fake ones. Reddit's own terms of service prohibit coordinated inauthentic behavior.

So the line is simple to state and only hard to hold when a quarter is going badly: participate authentically, never plant. Manufactured citations are becoming both more detectable and more legally exposed, and the platforms feeding the engines are actively hunting for them.

Over-indexing on a channel that is still 1% to 3% of sessions

AI is a small-volume, high-intent channel, and it should be funded like one.

Justify action by the slope, which is roughly one percentage point of growth per month in Conductor's data, together with the shortlist mechanic. Do not justify it by the level, because the level is small and anyone paying attention will say so. The correct risk framing is exclusion from consideration, not lost traffic today.

And do not reallocate the majority of a budget away from the channels still driving 90% or more of your pipeline. This report is an argument for a 0.25 to 0.5 FTE bet, not for burning the demand-gen engine down.

Blocking crawlers by accident

The most common high-impact error in the whole field, and it is almost always an artifact rather than a decision: a leftover 2023 "block everything" rule, or a CDN toggle nobody remembers switching on. ParseAI's 27% finding shows just how widespread this is. Audit quarterly.

Optimizing for an engine that re-architects next quarter

Citation weights are volatile. ChatGPT's Reddit share fell from roughly 60% to roughly 10% in two weeks. Diversify across engines, re-baseline quarterly, and never bet a program on any single engine's current weights.

Building on vendor stats that don't survive scrutiny

Much of the AEO evidence base is produced by the same firms selling the fix. This report labels every such number VENDOR-REPORTED and pairs it with independent evidence wherever any exists.

The defense is structural rather than clever: build your program on how retrieval actually works, on crawlability, passage structure, and third-party presence. Those mechanics remain true even if the entire AEO tooling category collapses tomorrow, and some of it will.

Part VI — Predictions (12 Months)

AI-referred traffic share rises from roughly 1% to 3% up to roughly 3% to 6% of B2B sessions by mid-2027. Medium confidence. The reasoning: Conductor's consistent ~1pp per month growth, though it is compounding off a small base and is partly offset by an overall contracting click surface.

Engine convergence versus divergence: continued divergence. High confidence. Structurally different indexes, Bing, Brave, Google, and proprietary ones, combined with exclusive licensing deals, prevent convergence. The 11% to 59% cross-engine overlap will not close materially within twelve months.

Agentic purchasing in B2B remains research-assist dominant, with autonomous purchase staying confined to developer tooling and low-consideration self-serve SaaS. High confidence. The $15T and 90% Gartner figure is a 2028 projection, not a 2027 reality, and it will be quoted as though it were the latter roughly once a week.

The AEO tooling category begins consolidating, with several of the roughly ten trackers merging or folding as Bing and Google ship more native reporting. Medium confidence.

SEO as a function absorbs GEO rather than being replaced by it. High confidence. Google itself states that its AI features rest on core Search ranking, and the durable levers, authority, structure, entity clarity, freshness, and third-party presence, are shared across both. The genuine deltas are narrower than the discourse suggests: per-engine measurement, passage-level structure, third-party citation surfaces, and crawler and rendering hygiene.

Part VII — The Machine Visibility Scorecard

Score each layer 0–2 (0 = not started, 1 = partial, 2 = solid).

• Crawlable: Retrieval bots allowed + content server-side rendered + fetches verified in logs?
• Parseable: Answer-first passages + canonical fact surfaces (pricing/security/integrations/comparisons/docs) + consistent entity records?
• Citable: Original data asset + answer-first content with statistics and quotes + stopped commodity output?
• Present: Authentic Reddit / review-platform / YouTube / listicle footprint in your category?
• Transactable: Public API / MCP server / machine-readable pricing (only if agent-relevant to you)?
• Measured: Per-engine tracking + monthly AEO report tied to pipeline, not sessions?

How to read your score. 0–3: you are likely invisible to AI answers, and the single highest-leverage next move is Layer 1, crawlability and rendering, full stop. Nothing else you do will register until that is fixed. 4–7: you are crawlable but not citable, so prioritize Layer 3, build one original-data asset, and run the Layer 0 audit to find where your gaps actually are. 8–9: you are present but flying blind, so build Layer 6 per-engine tracking and start seeing what is working. 10–12: you are defensible, so focus on deepening the Layer 4 community moat and re-baselining quarterly, because the ground moves every quarter and a defensible position is a temporary one.

Wherever you land, the sequence is the same: fix crawlability, restructure for passages, earn citations, then measure per engine. When you reach that last step, our vendor-neutral comparison of GEO monitoring tools covers what each tracker can and cannot see — and where running the audit yourself still beats paying for one.

Frequently asked questions

Is AI search actually replacing Google for B2B buyers?

Not in traffic terms. G2's March 2026 survey (n=1,076) found 51% of B2B buyers now start research in an AI chatbot more often than Google, but Conductor's benchmarks across 13,770 domains put AI-referred traffic at just 1.08% of sessions. The shift is in where shortlists form, not where clicks come from.

Do AI Overviews really reduce clicks to your website?

Yes, and it is now causal rather than correlational. A pre-registered randomized field experiment by Saharsh Agarwal (Indian School of Business) and Ananya Sen (Carnegie Mellon) with 1,065 Chrome users found organic outbound clicks fell 39.8% and zero-click searches rose 34.5% when an AI Overview appeared. Published estimates of the magnitude range from roughly one-third to two-thirds; the direction is settled.

What is the single highest-leverage technical fix for AI visibility?

Server-side rendering. Vercel and MERJ's server-log study found that none of the major AI crawlers execute JavaScript — GPTBot fetched JS files in 11.50% of requests and ran them in 0%. If your headline, pricing, or product detail is not present in view-source, it does not exist to ChatGPT, Claude, or Perplexity. Not 'ranks poorly' — does not exist.

Does publishing an llms.txt file help you get cited by AI engines?

No. Google's John Mueller stated that no AI service uses it and that server logs show they do not even check for it, and Gary Illyes confirmed Google has no plans to support it. Ahrefs analyzed 137,000 sites and found 97% of llms.txt files received zero requests in May 2026. It is a cheap agent-readiness bet for docs-heavy or API-heavy products, not a citation lever.

Can I block AI crawlers from training on my content without losing citations?

Yes — training and retrieval run on separate agents. Blocking GPTBot, ClaudeBot, and Google-Extended opts you out of model training but does not remove you from live answers. Blocking OAI-SearchBot, Claude-SearchBot, or PerplexityBot removes you from citations entirely; OpenAI states that sites opted out of OAI-SearchBot will not be shown in ChatGPT search answers.

Are AI agents actually buying B2B software autonomously?

Agent-assisted research is real and common: 6sense's 2025 report (n=3,986) found 94% of buyers use LLMs during the buying process, though they still averaged 16 interactions with the winning vendor. Agent-executed purchase is rare and largely confined to developer tooling. Gartner's '90% of B2B buying agent-intermediated by 2028' is a projection, and 'intermediated' explicitly includes assisted research.

How should you measure AI visibility?

Per engine, never as a single blended score — measured cross-engine citation overlap is only 11–59%, so an averaged number describes no engine that exists. Track per-engine share of voice, citation count and position, prompt coverage, sentiment, and branded-search lift. Bing Webmaster Tools' AI Performance report, launched February 2026, is the first first-party AI citation data from a major engine.

Appendix A — Claims & Sources

Appendix B — What Could Not Be Verified

A report that flags everyone else's evidence quality owes you the same audit of its own. Here is what did not survive it.

C3, the 21% cross-engine agreement figure. The original r/GrowthHacking thread (1ulicmw) is anonymous, n=1, unpublished, and unreplicated. I went looking for the specific "50 prompts × 3 engines = 21%" study behind it and found no published equivalent anywhere. I replaced it in the body with the measured overlap range from Profound and BrightEdge, which is 11% to 59%. Treat 21% as an untested hypothesis worth replicating, not as a fact.

C5, the Resend 63% versus SendGrid 7% claim. This traces to Insight Partners' "Agent-led growth" blog and an Improbability Substack post, and neither one states a method, a sample, or a test date. The Supabase growth story next to it, by contrast, is first-party confirmable: CEO Copplestone's own statements, the June 4, 2026 $500M round at a $10.5B valuation, and the claim that more than 60% of new databases are launched by some sort of AI tool, with Claude Code cited as the largest single source. Note the wording: Supabase says "AI tool," not "agent," and the distinction is exactly the one this report keeps insisting on. The Resend and SendGrid percentages are not confirmable. So I killed the specific figures and kept the named, documented Supabase case as the defensible example of agent-driven developer-tool selection.

C7, the 66% / 58% / 52% / 47% content-leader survey, n=1,081. The LinkedIn post by Justin Ethington of TrendCandy does not name a published instrument, and I could not locate the underlying survey's publisher, field dates, or sample composition within budget. Marked UNVERIFIED, DO NOT LOAD-BEAR. The directional claim, that page views and MQLs are declining in perceived importance, is independently supported by multiple 6sense, Forrester, and Content Marketing Institute sources on the death of the MQL. The specific percentages remain unverified. This was the intended measurement-section instrument in the original brief, and since I could not upgrade it, I built Layer 6 on instrumentable, primary-sourced measurement instead: Bing WMT, GA4, and Conductor.

Non-software B2B citation distribution. No large-scale study of AI citation sources for industrial manufacturing or professional services was located. This is explicitly unmeasured, and I did not import the SaaS distribution to fill the hole.

RRF inside named engines. No engine confirms using Reciprocal Rank Fusion internally. It is attributed here only as the standard technique for multi-query and hybrid retrieval (Cormack et al., SIGIR 2009), not as a disclosed engine fact.

Claude's search backend. Brave is strongly implied by Anthropic's subprocessor list and by independent code inspection, but it has never been confirmed on the record. It is reported here as circumstantial, and it should be repeated as circumstantial.