
Google AI Overviews & AI Mode — How to Optimize Your Site So AI Cites You
AI Overviews are Gemini-generated answers above Google's results; AI Mode is a separate, fully conversational search tab. The shortest answer to "how do I get in": your page must be indexed and eligible to appear with a snippet, and the content must add unique value — according to Google's first official guide published in May 2026, there is no separate AI index, no separate submission, and no special "AI markup". Google says it plainly: optimizing for generative search features is still SEO. But the devil is in the data: on queries with an AI Overview, a #1-ranked page loses up to 58% of its CTR, and ~93% of AI Mode sessions end without a click — so the prize is no longer the position, it's presence inside the answer.
AI Overviews already trigger on a large share of queries, and a #1-ranked page loses up to 58% CTR when they appear. In May 2026 Google published its first official AI optimization guide. What's required, what's a myth (llms.txt, special markup), how AI Mode's query fan-out works, and what measurably increases your citation odds.
This guide collects everything known for certain as of mid-2026: market data (including Senuto's 18-million-keyword study of the Polish market), Google's official requirements and busted myths, the mechanics of AI Mode's query fan-out, and the factors that measurably correlate with citations.
What AI Overviews and AI Mode are — and how they differ
Both features generate answers with the same core (Gemini + Google's ranking systems), but they behave differently:
| Feature | AI Overviews | AI Mode |
|---|---|---|
| Where it runs | A block above classic results | A separate tab — a full chat interface |
| When it appears | Automatically on a subset of queries (mostly informational) | Whenever the user picks it |
| Mechanics | An answer with citations above the SERP | Query fan-out: the question is split into sub-queries and synthesized |
| Links | Citations next to answer fragments | Sources in a side panel and inline |
| Zero-click | 80–83% of AIO queries end without a click | ~93% without a click |
| EU availability | Live (Poland since March 2025) | Rolling out — full EU availability announced for late 2026 |
AI Overviews trigger on roughly 29% of phrases in Polish Google (Senuto data) while covering ~15% of search volume — Google fires them mostly on informational queries (over 88% of triggers), rarely on transactional ones. AI Mode is the destination "search as chat" interface: it passed a billion monthly users globally, with the full European rollout announced for the end of 2026 (regulatory alignment around the AI Act is ongoing).
How much traffic they really take — the data
/// AI OVERVIEWS & AI MODE IN NUMBERS (2026)
The Polish market data is brutally specific. In June 2025, 19.4% of clicks vanished from the Polish web year over year — while impressions grew by 3.3%. Across H2 2025 the median organic traffic drop reached ~19.9%, with nearly two-thirds of analyzed sites affected. That's the classic AI Overviews signature: you stay visible (impressions up), but the user gets the answer without clicking.
There is a flip side: brands cited in AI answers see roughly +35% higher organic CTR than non-cited ones. The divide no longer runs between position #1 and #5 — it runs between "you're in the answer" and "you don't exist." I cover that shift in depth in the GEO guide.
How AI Mode picks sources — query fan-out
AI Mode's key technical difference from classic search is query fan-out:
/// QUERY FAN-OUT — HOW AI MODE PICKS SOURCES
Deep content can get cited for a question it was never optimized for
When a user asks "which CRM for a 10-person services company with invoicing integration," the system doesn't run one search. It splits the question into a series of sub-queries (CRM comparisons, plan limits, accounting integrations, reviews), retrieves content from dozens of sources in parallel, and synthesizes an answer, citing the sources it judged most credible for each fragment.
The practical consequence is huge: your page can get cited for a question it was never optimized for — if it covers the topic deeply enough to answer one of the sub-queries. That rewards complete topical coverage (topical authority) over single-phrase pages. And conversely: shallow "one keyword, one page" content has nothing to offer any sub-query.
Google's official position — what's required and what's a myth
On May 15, 2026, Google published its first consolidated guide to optimizing for generative features. The key takeaways:
/// GOOGLE’S OFFICIAL GUIDE (MAY 2026) — REQUIREMENTS VS MYTHS
"Optimizing for generative search features is still SEO"
Hard requirements (without these you don't exist in AI):
- 1.Indexing — the page must be in Google's index and meet Search technical requirements. There is no separate AI index and no separate submission.
- 2.Snippet eligibility — the content must be allowed to appear as a snippet. The `nosnippet`, `data-nosnippet`, `max-snippet` and `noindex` directives also govern presence in AI Overviews and AI Mode.
- 3.Unique value — the systems reward content that adds something beyond compilation: original data, experience, concrete answers.
Myths busted directly by Google:
- llms.txt is not needed — Google doesn't use it. My full analysis of that file (and the one scenario where it makes sense) is in the llms.txt article.
- There is no "special AI markup" and no requirement for Markdown versions of pages.
- You don't need to chop content into small chunks — Google's systems "understand the nuance of multiple topics on a page" and pick the relevant fragment themselves.
- AEO and GEO are, from Google's perspective, still SEO — AI features run on the same ranking systems as classic search.
Watch out for a commonly confused detail: Google-Extended does not control AI Overviews. That robots.txt directive governs Gemini model training — presence in AI Overviews and AI Mode is controlled solely through the regular indexing and snippet mechanisms. Which makes opting out expensive: blocking AI via `nosnippet` also kills your snippets in classic results.
What measurably raises your citation odds — the research
Beyond the official requirements, a growing body of correlational research (2025–2026) points the same way:
| Factor | Research finding | Practical takeaway |
|---|---|---|
| Top-10 position | Position #1 → ~33% citation odds; #10 → ~13% | Classic rankings are still the widest door into AIO |
| Citations beyond top 10 | 38% of AIO citations come from outside the top ten (24% a year earlier) | Source selection is decoupling from rankings — depth earns a second chance |
| Content freshness | Cited pages are on average ~26% "fresher" than the organic top 10 | A scheduled update cycle for key content is a real factor |
| Brand mentions | 0.66 correlation with AIO visibility (backlinks: 0.22) | Digital PR and mentions outweigh classic links |
| Content depth | 2,500+ word pages cited ~1.6× more often than <800 words | Complete topic coverage beats shallow posts |
| Sources in the body | Pages citing named sources are cited ~2.1× more often | References and sourced data are citation fuel |
| HowTo schema | ~1.7× higher citability on instructional queries | Structured data aids understanding, though it's not a "ticket" |
These numbers form the pattern you already know from E-E-A-T: content with evidence, kept fresh, deep, and signed by a recognizable entity wins. AI Overviews didn't invent new rules — they turned up the weight on the existing ones.
The step-by-step action plan
- 1.Verify the foundation. Clean indexing, snippets not blocked, crawl budget under control. Without this, no "AI optimization" exists.
- 2.Map the AIO queries in your niche. Check which of your business's phrases trigger an AI Overview — that's where the game is about citations, not positions.
- 3.Answer in the first sentences. Every key section opens with the direct answer (answer-first), context afterwards. Fan-out extracts fragments; it doesn't read intros.
- 4.Headings as questions. An H2/H3 structure mirroring real user questions hands the system ready matches for its sub-queries.
- 5.Build depth, not post count. One complete guide (2,500+ words, tables, data) covers dozens of fan-out sub-queries — ten shallow posts cover none.
- 6.Cite sources and show data. Named sources in the body (research, documentation, your own numbers) correlate with ~2.1× higher citability.
- 7.Close the entity layer. Structured data (Article, FAQPage, Organization, Person with sameAs) and a consistent brand profile — the systems must know WHO is answering.
- 8.Set a freshness cycle. A quarterly review of key content with a visible update date — cited pages are markedly fresher than average.
- 9.Build mentions, not just links. Brand-mention correlation with AIO visibility (0.66) beats backlinks (0.22) — industry publications, expert commentary, roundups.
- 10.Measure presence, not just positions. Search Console doesn't separate AI Overviews traffic — you need your own AI Share of Voice measurement.
The most common mistakes
- Optimizing "for AI" without the SEO foundation. A page with indexing problems won't enter AIO regardless of content format.
- Deploying llms.txt and "AI markup" as the cure. Google officially doesn't use them — that's time taken from factors that matter.
- Blocking snippets in a panic over "content theft". `nosnippet` removes you from AI and cripples your classic results at the same time — a business decision, not a technical one.
- Writing for a single phrase. Query fan-out rewards topic coverage; one-keyword pages answer no sub-query.
- Judging results by CTR. With AIO, the CTR drop is systemic; the right question is whether you're cited and how your share of answers grows. How to translate this shift into KPIs and the board conversation is laid out in the zero-click era strategy post.
Summary
AI Overviews and AI Mode didn't void SEO — they moved the finish line. The entry requirements stayed classic (indexing, snippets, quality), but the prize changed address: presence inside the answer matters more than position, and it's decided by content depth, freshness, named sources and a recognizable entity. The traffic data leaves no illusions — click declines are systemic, and the only "winning" side is the cited one.
Strategically: treat this guide as a layer on top of a solid GEO strategy and E-E-A-T signals. Start with the map of AIO-triggering queries in your niche, rebuild key content into answer-first format, and start measuring citations — before your competitors do.
---
I optimize brand visibility in Google AI Overviews and AI answers as part of AI optimization (GEO) and technical SEO. I teach it in the SEO & GEO course. Get in touch — I'll start with a map of the AI Overviews queries in your niche and a measurement of whether AI already cites you.
Related articles
/// RELATED_SERVICES
Need these concepts implemented? Explore the services related to this topic.
/// SOURCES
- 01Google – Optimizing your website for generative AI features (May 2026)
- 02Google – AI features and your website
- 03Senuto – AI Overviews in Poland report (18M-keyword analysis)
- 04Ahrefs – 38% of AI Overview citations pull from the top 10
- 05Search Engine Journal – Google's New AI Search Guide Calls AEO and GEO 'Still SEO'
/// RELATED_RECORDS
AI Browsers and Agent Experience (AX) — Can an Agent Actually Use Your Website?
Within twelve months we got Comet from Perplexity (free worldwide since October 2025), Claude for Chrome and ChatGPT Atlas — and in July 2026 OpenAI announced it is retiring Atlas and folding agentic browsing directly into ChatGPT. Browser brands come and go, but the capability stays: an agent that clicks, fills forms and completes tasks on your site on the user's behalf. Crawlers only needed readable HTML — an agent has to be able to ACT. What Agent Experience (AX) is, what most often blocks agents (captchas, modal walls, div-buttons, unlabeled forms) and how to test your own site with an agent in 30 minutes.
Agentic Commerce — How to Sell When the Buyer Is an Agent (ChatGPT Checkout, ACP, AP2, UCP)
In February 2026 OpenAI launched "Buy it in ChatGPT" — and in March it pulled back from native checkout, pivoting to agentic storefronts: the purchase completes in the merchant's store, not in the chat. The AI transaction layer is in motion, but the direction is settled: the ACP (OpenAI/Stripe), AP2 (Google) and UCP protocols are already standardizing how an agent finds a product, pays and places an order. What a store should do today to avoid burning budget on a moving target: the product feed as the zero-risk investment, API readiness, and a cool-headed decision matrix — join now or wait deliberately.
SEO and GEO for SaaS and B2B — How to Get Recommended When the Customer Asks AI "Which Tool Should I Pick"
GenAI chats are now the number one source influencing B2B vendor shortlists — 17.1% of mentions, more than review sites (15.1%) and vendors' own websites (12.8%) — and about half of software buyers start their research with an AI conversation (G2, 2025). Buyers spend a mere 17% of the purchase journey with sales reps — the decision largely forms before anyone fills in a form. How to make the models recommend your product in that invisible phase: comparison pages, quotable pricing, G2 and communities, and category-level SoV measurement.
Signal received?
Terminate
Silence
Initiate protocol. Establish connection. Let's build something loud.
