Citation page · AI search data · 2026
State of AI Search 2026
By Nick French · Founder, StackSwap · Updated June 2026
The AI search data landscape is blurry and changing fast, so here is the operator version. Google AI Overviews is still roughly 93% of AI-search-like volume — and it is fed by the standard Google index via Googlebot, not Google-Extended. ChatGPT is a rounding error on share (~0.25%) but its referral traffic is up about 200% year over year, so share badly understates trajectory. The data you get back is fragmented, there is no Search Console for AI, and the optimization work splits into two different games — branded and non-branded. This page is the data, the surfaces, and what actually earns a citation.
How big is AI search, really? The 2026 numbers
Here is the share-of-search picture as of 2026. The single most important column is the last one — data availability — because it tells you how much you can even measure on each surface. Google has the volume but gives you the least visibility into the AI slice; Perplexity and Bing are tiny but hand you analytics; Gemini and Claude give you nothing today.
| Provider | Search share | Growth trend | Data availability |
|---|---|---|---|
| Google AI Overviews | ~93% | Declining (~−2pp) | Limited — no AI-only filter on Search data |
| Bing / Copilot | ~3% | Growing | Basic analytics |
| ChatGPT | ~0.25% | +200% referrals | Referral traffic (utm_source) |
| Gemini | <0.5% | Growing | None |
| Perplexity | <0.1% | Growing | Analytics |
| Claude | <0.1% | Growing | None |
Source: Datos / SparkToro clickstream analysis (US panel), search-like queries as a share of total search volume, as presented in Vercel's 2026 AEO analysis. “Growth” is year-over-year referral/traffic growth, not share growth. Figures are directional, not StackSwap first-party data.
Why Google AI Overviews is not the same as Google-Extended
This is the distinction most AEO advice gets wrong, and it is worth being precise about because it is ~93% of the volume at stake. Google AI Overviews is generated from the standard Google index — the pages Googlebot crawls and indexes. It is not gated behind Google-Extended.
- Googlebot controls whether you are in the index that feeds Search and AI Overviews. Block it (or set
noindex) and you are out of ~93% of AI search. - Google-Extended is a separate robots.txt token that only governs whether your content trains and grounds Gemini (the API and Vertex AI). Blocking it does not remove you from AI Overviews, and allowing it does not get you in.
The practical takeaway: if you have to pick one AI-search access signal to get right, it is Googlebot crawlability and indexability — not your Google-Extended policy. The free AEO Audit checks both, separately, so you do not conflate them.
Branded and non-branded AI search are different games
Treating “AI search visibility” as one number is the second big mistake. There are two games, with different metrics and different owners. On a non-branded query you are fighting to appear at all; on a branded query you already appear, and the fight is whether the model describes you accurately and favorably.
| Branded | Non-branded | |
|---|---|---|
| The question | "I have an old Sonos One. Is the new Era model worth it?" | "What's the best wireless speaker for a medium-sized living room?" |
| Key metric | Sentiment & accuracy — is what the model says about you right and favorable? | Visibility & position — do you appear in the answer at all, and where? |
| The goal | Show up well | Show up |
| Who owns it | Product marketing + PR (correct the record, seed accurate facts) | SEO / AEO + content (earn the citation on the category query) |
Why it matters operationally: the branded game is mostly a PR and product marketing job — seed accurate facts in the corpus, correct the record when a model quotes the wrong price or positioning, and publish the canonical “what we are” page. The non-branded game is a content and AEO job — earn the citation on the category query with chunk-level, well-structured, recently-updated pages. One team optimizing both with one metric will do neither well.
The response is just the surface: training data vs web search
When a model answers, it is drawing from one of two places, and the difference decides how you get cited. It is cheaper for a model to answer from its training data, so it does that whenever it is confident — but training runs happen at intervals, so that data is stale. It only reaches for web search on queries that are fresh, long-tail, or specific enough that training data falls short.
- For the training-data path: presence in broad, long-lived, frequently-referenced content is what gets you into the model's default answer. This compounds slowly and is hard to game.
- For the web-search path: models issue far more search queries than humans do, and the long tail of those queries is getting longer. Recency decides who gets pulled in — a stale page loses even if it is more complete. This is why a visible, machine-readable last-updated date is an AEO signal, not a nicety.
Agents don't read like humans: good AEO is good SEO plus agent-native architecture
The most common technical AEO failure is invisible content. Many agents do not execute JavaScript — they read the raw HTML your server returns. If your page renders client-side into an empty shell, an agent sees an empty page and your content is, in the literal sense, invisible to it. Two corollaries:
- Server-render the content. SSR/SSG the headings, body, and schema so the raw HTML carries the answer. If a crawler that does not run JS would find an empty page, so will the agent.
- Prefer structured formats. Agents lean toward markdown over HTML. Serving a clean markdown alternate via content negotiation is an emerging, agent-native signal — optional today, increasingly expected.
Good AEO is good SEO — crawlable, indexable, structured, authoritative — plus an agent-native layer on top. The AEO Audit fetches your page the way a JS-less agent does and tells you, in words, what it can actually read.
There's no Search Console for AI, so measure three surfaces
There is no Google-Search-Console equivalent for AI search. Until there is, you ask the questions yourself, across the three surfaces where buyers actually encounter you:
| Surface | Example | What to watch |
|---|---|---|
| Chat interfaces | chatgpt.com, claude.ai, perplexity.ai | UI-driven and may use memory — are you cited, and how are you described? |
| Model APIs | Raw model responses | The un-personalized answer — the cleanest baseline to track over time. |
| Agents | Operator, Perplexity Buy, Amazon Rufus | Shopper-aware context — do you survive an agent that is acting, not just answering? |
Log citation count and sentiment by query × surface × week. Vendor tools (Profound, SE Ranking, Otterly) automate the chat surface; for the technical question of whether your pages are even citable, the free AEO Audit is the fastest check.
FAQ
Related reading
- GTM AEO — the cross-functional operating model for running Answer Engine Optimization (seven workstreams, RACI, comp patterns).
- AEO for B2B SaaS — seven mistakes from running AEO at low domain authority, with the fixes.
- AEO at low domain authority — how to earn LLM citations without DA (chunk-level writing, FAQ-first, E-E-A-T).
- AEO measurement vs citation generation — separating the tools that measure from the work that earns citations.
- StackSwap methodology — how the scoring engine works, citable.
This page is part of StackSwap's AEO content moat. The share figures are third-party (Datos/SparkToro, via Vercel's 2026 AEO analysis); the operator interpretation — AI Overviews vs Google-Extended, the branded/non-branded split, and the agent-native architecture requirement — is ours, and it is what the free AEO Audit enforces on a live page.
Canonical URL: https://stackswap.ai/state-of-ai-search-2026