AI Overviews vs Featured Snippets: What Actually Changed
AI Overviews vs featured snippets: one extracts from a single page, the other synthesizes many. How selection differs, and what each does to your clicks.

Most coverage of AI Overviews vs featured snippets treats the second as the first with better writing. It isn't. One lifts text out of a single page and takes that page's blue link away. The other writes new text from several pages and leaves your listing exactly where it was. Those two facts pull your traffic in opposite directions, which is how a site loses featured snippets, gains AI Overview citations, and still watches its clicks fall.
The Short Version
A featured snippet is an extraction. A search engine copies a paragraph, a list or a table out of one indexed page, shows it at the top of the results, and links back to that page. Nothing is written and nothing is merged.
An AI Overview is a generation. A model runs several searches behind the one you typed, pulls passages from multiple pages, and writes a new answer with source links beside it. The sentence on screen exists nowhere on the web.
Everything else follows from that one difference: who is doing the writing. It changes the selection process, the number of winners, the placement rules, the measurement and the click math. The two also co-occur, so an AI Overview firing does not mean the snippet is gone.
What a Featured Snippet Actually Is
Google's Search Console documentation defines it in one line: "A featured snippet displays information extracted from a single, specific web page. It includes a link to the source web page." Three words there do the work. Extracted, so the text is yours verbatim. Single, so there is exactly one winner. A link to the source, so it is a placement of your own listing rather than a summary standing in front of it.
You cannot opt in. Google's featured snippets documentation is blunt about how to mark a page up for one: "You can't. Google systems determine whether a page would make a good featured snippet for a user's search request, and if so, elevates it." No schema, no attribute, no submission form.
On reporting, the same help page says a featured snippet "has a link to the source property, and so it (typically) occupies position 1," and that standard impression rules apply. Hold that sentence. The AI Overview equivalent reads differently.
Stuck on page two?
Real human clicks that lift your CTR and move you up the rankings.
What an AI Overview Actually Is
Four dates. Announced at Google I/O in May 2023 as the Search Generative Experience. Launched in the United States as AI Overviews on 14 May 2024. Expanded to more than 100 countries on 28 October 2024. AI Mode, the conversational surface, reached the US in May 2025.
The important machinery is retrieval, not writing. Google's AI features documentation says these features may use a "query fan-out" technique, described as "issuing multiple related searches across subtopics and data sources." Your query is decomposed into narrower machine-generated searches you never see, and the answer is assembled from what comes back. Where fan-out sits in each engine's pipeline is covered in how AI assistants pick sources.
Eligibility is short: to appear as a supporting link, "a page must be indexed and eligible to be shown in Google Search with a snippet." There is no way to mark up in. The documentation states you don't need "new machine readable files, AI text files, or markup to appear in these features."
Two reporting rules separate an AI Overview from a snippet completely. First: "An AI Overview occupies a single position in search results, and all links in the AI Overview are assigned that same position." Second, the one almost nobody quotes: "To be counted as an impression, the link must be scrolled or expanded into view."
AI Overviews vs Featured Snippets, Side by Side
| Featured snippet | AI Overview | |
|---|---|---|
| Text on screen | Copied verbatim from one page | Generated, exists on no page |
| Number of sources | One | Several |
| Unit selected | A block inside a page | Passages across pages, after fan-out |
| Query answered | The one the user typed | The typed query plus machine-generated sub-queries |
| Effect on your organic listing | Replaces it, deduplicated since January 2020 | Leaves it in place |
| Reported position | Typically 1 | The block's single position, shared by every link inside it |
| Impression counted when | Standard impression rules | The link is scrolled or expanded into view |
| Opting in | Not possible, no markup | Not possible, no markup |
| Opting out | nosnippet, data-nosnippet, max-snippet | The same three, plus noindex |
| Isolated in Search Console | No | Impressions only, from June 2026, limited rollout |
| Repeatability | Fairly stable per query | Can vary between runs of the same query |
Extraction and Synthesis Are Different Selection Jobs
Extraction rewards something liftable: a self-contained block under a heading that matches the question, answer before context, in a shape that survives being copied out. A short paragraph, an ordered list, a table. The engine is choosing a rectangle of your page to photocopy, and if your answer only makes sense after the two paragraphs above it, there is no rectangle to take.
Synthesis is a different problem, because the target is a claim rather than a query. An answer makes several assertions and each needs support, so your page competes for the slots it can support and no others. That is why a 700-word page can take a slot from a 4,000-word guide that mentions the same detail in passing. How a page gets cut into retrievable units is covered in AI answer engine retrieval, where the unit is a chunk and not a page.
The practical difference is how many winners exist. A featured snippet is one slot: you hold it or you don't. An AI Overview is a handful of support slots that engines spread across domains, so being second-best on a sub-question is often still worth a citation. Losing a snippet is total. Missing one citation usually is not. The two jobs are not opposed, though, because both reward a clear, self-contained answer under a heading that names what it answers. What differs is the payoff structure, not the craft.
The Deduplication Rule Only Applies to One of Them
This is the part of the comparison that gets skipped, and it changes how you read your own reports.
On 22 January 2020, Google deduplicated featured snippets. Before that, a page could hold the featured snippet and a regular listing on page one, giving eleven entries on a ten-result page. After it, the snippet counts as one of the ten and the source page's ordinary listing is removed. Search Engine Land, Search Engine Journal and Seer Interactive all documented the change at the time, and the rule has held since.
A featured snippet is therefore a trade, not a bonus. You swap a blue link carrying the title and description you wrote for a block of text the engine chose, placed first. Sometimes the engine picks the paragraph that answers the question so completely that nobody needs your page.
An AI Overview does not work that way. Nothing in Google's documentation removes your organic listing because you were cited in one, or because an AI Overview appeared at all. The block is added above the results. Your ten blue links are still ten.
| Outcome | Your organic listing | What you gained | What you gave up |
|---|---|---|---|
| You win the featured snippet | Removed from page one | First placement, your text shown in full | Your title and description as the click prompt |
| You are cited in an AI Overview | Still there | A link inside the block | Attention above your listing, and the click if the answer is complete |
| You lose a featured snippet to an AI Overview | Comes back | Your ordinary listing returns | First placement |
Read that third row twice. Through 2025, plenty of sites watched average position slide on informational queries and filed it as a ranking loss. Wherever a snippet was replaced by an AI Overview, part of that slide is a deduplicated listing being handed back: position moves from roughly 1 to whatever the page ranks organically, often between 2 and 5, with nothing changing about the page's actual standing. Diagnose that as a demotion and start rewriting content, and you're treating a placement change as a quality problem.
The Volume Shift, With Numbers
Ahrefs published the cleanest available measurement of the trade, across 1,000,000 randomly selected US desktop results pages between January and June 2025.
| Feature | January 2025 | June 2025 | Relative change |
|---|---|---|---|
| Featured snippet visibility | 15.41% | 5.53% | Down 64% |
| AI Overview visibility | 3.93% | 27.43% | Up 598% |
The correlation between the two series was -0.9053, which Ahrefs describes as very strong, with a visible switch-over point in March. Their earlier work noted the two features commonly appearing alongside one another, so this is displacement in aggregate rather than a clean one-for-one swap.
Four caveats belong beside those numbers: US desktop only, one tool's SERP sample, a six-month window that ended over a year ago, and a market-level correlation that is not proof of substitution on any individual query. Treat the direction as durable and the levels as stale.
What holds up is the base rate. The snippet opportunity has shrunk sharply on the query classes where AI Overviews fire, which skew informational. Navigational and transactional queries are far less affected, which is why brand terms make such a useful control set in the audit below.
What Each Surface Does to Your Clicks
The strongest public evidence on AI summaries comes from the Pew Research Center, published 22 July 2025. Pew analyzed browsing data from 900 US adults who agreed to share their activity, covering 68,879 unique Google search queries in March 2025, of which 12,593 produced an AI summary.
| Behavior | Page with an AI summary | Page without one |
|---|---|---|
| Clicked a traditional search result | 8% of visits | 15% of visits |
| Clicked a link inside the AI summary | 1% of visits | Not applicable |
| Ended the browsing session there | 26% of pages | 16% of pages |
Now the honest reading. This is a behavioral panel, not a controlled experiment, and the two groups are not comparable populations of queries. AI summaries fire more often on open informational questions, which had lower click rates than navigational queries long before generative search existed, so some of the gap is query mix. Google publicly disputed the study. The direction still matches what publishers reported independently, but quoting "AI Overviews halve your clicks" as a clean causal fact overstates the evidence.
Featured snippet click effects are harder to pin down, because nearly all the well-known snippet CTR studies ran before January 2020, measuring a world where the snippet holder also kept a blue link. That arithmetic no longer exists, and few circulating figures price in the lost listing.
The mechanism both features share is simpler than either study. When the answer arrives on the results page, the click doesn't happen. That is the dynamic covered in zero click searches and where your impressions go, and it predates generative search. What changed is scale and authorship.
The Two Features Are Not Measured on the Same Terms
Here is the trap inside every "featured snippet CTR vs AI Overview CTR" comparison you will read.
A featured snippet follows standard impression rules. It shows, it counts. An AI Overview link counts as an impression only when it "must be scrolled or expanded into view," per Google's own documentation. Links inside a collapsed AI Overview the user never opened generate no impression at all.
That biases the comparison in the opposite direction most people assume. AI Overview impressions are counted only over the subset who scrolled or expanded far enough to reveal the link, a more engaged population by construction. So any CTR you compute for AI Overview citations sits on a filtered denominator. Compare it to a snippet CTR, computed over everyone, and you are comparing two denominators and calling the difference a performance gap.
On 3 June 2026, Google added generative AI performance reports to Search Console, covering AI Overviews and AI Mode. Read the fine print before building a dashboard on it:
- Impressions only. No queries, no clicks, no click-through rate, no average position.
- Broken down by page, country, device and date.
- A breakout, not new data. Google confirmed AI impressions were already inside your existing totals, so your aggregate numbers do not change.
- Limited rollout. It reached a subset of site owners first, so an account without the report is not an account without AI impressions.
So you can now see where AI features surfaced your links, and still not what they cost you in clicks. There is no featured snippet filter under Search Appearance either, so neither surface can be isolated on the click side. For anything involving clicks, the results page itself is still the instrument.
Worked Example: Tell a Snippet Loss From an AI Overview Loss
Both look identical in a dashboard: impressions up, clicks down, position worse. They call for opposite responses.
Step 1: pull the query set
In Search Console, open Performance, then Search results. Set the date range to Last 3 months and switch on Compare to previous period. Leave Search type on Web. Open the Queries tab and export to Sheets. Keep only rows where impressions rose and clicks fell.
Step 2: split the queries by class
Add a "Queries containing" filter and build two buckets. Bucket one holds question and comparison phrasing: how, what, why, best, vs, difference. Bucket two holds your brand terms. AI Overviews concentrate on the first, so if the click loss sits in bucket one while bucket two stays flat, the results page changed, not your site. That split resolves most of these investigations before you touch a page.
Step 3: read the position column against the deduplication rule
For a query you previously held a snippet on, the signature of a snippet-to-AI-Overview replacement is position moving from roughly 1 to your underlying organic rank, with impressions steady or rising. A genuine ranking loss pushes you below your historical organic band and takes impressions down with it. Position falling while impressions climb is nearly always a placement change.
| Query | Position before | Position after | Impressions | Clicks | Most likely cause |
|---|---|---|---|---|---|
| how long does onboarding take | 1.0 | 3.2 | Up 12% | Down 41% | Snippet replaced by an AI Overview, listing returned |
| best tool for x | 4.1 | 4.3 | Up 34% | Down 38% | AI Overview added above an unchanged listing |
| x pricing | 2.0 | 6.8 | Down 22% | Down 45% | Real ranking loss, impressions fell with position |
| yourbrand pricing | 1.0 | 1.0 | Flat | Flat | Control query, no AI feature firing |
Those figures illustrate the four patterns. They are not measured data.
Step 4: verify on the results page
Take 15 to 20 affected queries and run them by hand, in a private window, on the device mix your report shows. Record four columns: AI Overview present, featured snippet present, your domain cited inside it, and your organic listing still visible. Twenty queries checked manually beat any inferred metric, because neither feature is filterable on the click side.
Step 5: design the before and after properly
- Baseline: 28 days before your change, weekdays aligned to the comparison window.
- Change window: 28 days after re-crawl, not after publish. Read the Last crawl date in URL Inspection and start the clock there.
- Control set: 10 to 15 pages on comparable queries you deliberately do not touch.
- Metric: clicks per 1,000 impressions on the treated set, minus the same figure on the control set. The subtraction removes seasonality and results-page churn.
- Noise floor: decide it before you look, not after. A query with a few hundred baseline impressions cannot produce a readable result from a handful of clicks.
The report paths and the two sampling limits that quietly bias any Search Console CTR number are in how to measure organic CTR in Google Search Console.
The Controls You Have, and What They Cost
Google's AI features documentation lists nosnippet, data-nosnippet, max-snippet and noindex as the controls that limit what is shown from your pages, and states these are the same controls used for Search generally. The featured snippets documentation names the first three for snippets.
| Control | Featured snippets | AI Overviews | Collateral cost |
|---|---|---|---|
| `nosnippet` | Blocked | Text blocked | Your ordinary search description goes too, leaving a bare title link |
| `data-nosnippet` on a block | That text cannot be used | That text cannot be used | Covers only what you wrap, and you have to find every instance |
| `max-snippet` set low | Google says the shorter the setting, the less likely a featured snippet | Limits available text | Shortens your regular description as well |
| `noindex` | Page removed | Page removed | Page removed from search entirely |
| robots.txt disallow for Googlebot | Page removed | Page removed | One crawler serves both, so you cannot separate them |
The honest summary: no control suppresses AI Overviews while keeping featured snippets, none does the reverse, and none does either while leaving your ordinary description untouched. Google's preview controls treat all of it as one system. If a tool or an agency offers a clean AI Overview opt-out that preserves normal search presence, ask which documented directive delivers that.
What you do not control
Whether an AI Overview fires on a query. Which passage gets lifted. Whether the extracted block is the one you would have chosen. Whether a citation link is ever scrolled into view, which decides whether it registers as an impression at all.
Nothing you can purchase moves any of it. To be direct about our own products: SparkCliks sells search clicks and website visits, which appear in your analytics as clicks and sessions. Selection for either feature happens during retrieval, before a human sees the results page. We make no claim that bought clicks influence it, and you should be skeptical of anyone who does. The same applies to the signals in brand mentions vs backlinks: you can build them, you cannot buy the outcome.
Frequently asked questions
FAQ
They are displacing them at scale without eliminating them. Ahrefs measured featured snippet visibility falling from 15.41% to 5.53% of US desktop results pages between January and June 2025 while AI Overview visibility rose from 3.93% to 27.43%, and the two still appear together on the same page for some queries.
A featured snippet is text extracted verbatim from one specific page, with a link to that page. An AI Overview is newly written text generated from several sources after a query fan-out, with source links beside it, and the sentence it shows exists on no single page.
Yes. Since 22 January 2020, a featured snippet is deduplicated: it counts as one of the ten results on page one and the source page's ordinary listing is removed. Being cited in an AI Overview does not do this, so your organic listing stays where it was.
Yes, when both features fire on that query. They are separate surfaces with separate selection processes and neither excludes the other, though featured snippets now appear far less often on the informational queries where AI Overviews are most common.
Not yet. Google added generative AI performance reports on 3 June 2026, but they show impressions only, with no queries, clicks, click-through rate or average position, and they rolled out to a subset of site owners first. There is no featured snippet filter under Search Appearance at all, so checking the live results page by hand remains the reliable method.
No. Both are selected automatically with no markup, no submission and no paid placement, and Google's documentation states plainly that you cannot mark a page up for a featured snippet. Click services and traffic services, ours included, operate after the results page is built, so they do not touch which page or passage gets selected.
Related articles

GEO vs AEO vs AIO: What Actually Differs
GEO vs AEO vs AIO: which acronym has a real definition, where the three genuinely diverge, and how to settle it inside your own Search Console data.

Why AI Answers Cite Pages That Don't Rank in the Top Ten
Why AI answers cite pages that don't rank in the top ten: query fan out, passage level retrieval, source diversity, and a citation gap audit you can run.

llms.txt Explained: What It Does and Who Actually Reads It
llms.txt explained: what the spec actually does, what it cannot do, and which tools really fetch it. Plus Google's stated position and a log check to run.
