Featured snippet stats: which numbers are real, and which aren't

Search “featured snippet statistics” and the same handful of numbers recur across dozens of posts: snippets appear in 23.7% of search results, or 35%, or 19%, depending which post you land on; featured snippet CTR is 35.1%, or an older Ahrefs figure of 8.6%; and 41.2% of voice searches return a featured snippet. The spread between the low and high prevalence claims is nearly 2x. This piece traces each number to whatever it claims as a source, keeps the ones that check out, and drops the ones that don’t.

The prevalence numbers that don’t check out#

None of 23.7%, 35%, or 19% traces to a named, dated study with disclosed methodology. The 23.7% figure appears in aggregator posts that cite each other rather than a tracker; one repeats it alongside a claimed “19.2% in 2025” prior-year figure, also unsourced, that would itself contradict the unrelated “19%” claim circulating elsewhere as a current number. The 35% figure turns out to be two different things wearing the same digits: a 35.1% click-share result from a 3,500-respondent self-report survey run by Engine Scout in April 2022, which asked people about their perceived clicking behavior rather than measuring actual SERP click logs, and a separate, unrelated Ahrefs data point about one domain’s snippet-triggering queries falling 35% in six months. Neither is a general featured-snippet prevalence rate, and neither matches how it gets cited. The 19% figure has no disclosed source at all; it does not match either of Ahrefs’ two real, dated prevalence numbers below.

What Ahrefs actually measured, twice#

Ahrefs has published two real, dated, disclosed studies that bracket this topic eight years apart.

29 May 2017, ~100k keywords for CTR, ~14 million of a 112 million keyword database for prevalence. Featured snippets appeared in 12.29% of queries. Where a snippet was present, the snippet itself captured an average 8.6% of clicks, the organic result sitting directly beneath it captured 19.6%, and a normal #1 result with no snippet present above it captured 26%. That last comparison is the study’s real finding: a featured snippet did not just add a new result, it took clicks that would otherwise have gone to position one and redistributed most of them to position two instead.

22 July 2025, 1 million randomly selected US desktop SERPs. Featured snippet visibility fell from 15.41% in January 2025 to 5.53% in June 2025, a 64% relative decline, correlated at -0.91 with the growth of AI Overviews over the same window. This is the study that actually answers whether the 2017 numbers still describe today’s SERP: they describe a layout that six in ten of its own featured-snippet queries no longer produce.

What Google’s own documentation says#

Google’s featured-snippet documentation describes the mechanism, not a rate. It states that Google’s systems determine algorithmically whether a page would make a good featured snippet, that a site owner cannot manually mark or request one, and that a page can opt out entirely with a nosnippet rule or reduce its odds with a shorter max-snippet setting. No click-through percentage and no share-of-queries statistic appears anywhere in it. Any claim that attributes a specific CTR or prevalence figure to Google itself is attributing a number Google has not published.

The voice search claim, traced#

“41.2% of voice searches return a featured snippet” does not match the study it most plausibly descends from. Backlinko’s real, dated voice search study, published 28 February 2018 from an analysis of 10,000 Google Home results, found that 40.7% of voice search answers came from a page that also held a featured snippet in desktop search results. That is a narrower and different claim: it says a correlation existed between a page’s featured-snippet status and its odds of being read aloud by Google Home, not that four in ten voice searches directly surfaced a snippet on screen. The 41.2% figure appears to be drift from the real 40.7%, close enough to look like a citation and different enough not to be one.

Why we care#

The through-line across all four unverifiable claims is the same: a real number existed somewhere in the chain, and repetition sanded off its edges until the source, the date, and the exact question it answered all fell away, leaving only a percentage that sounds precise enough to trust. That matters more than usual here because the underlying SERP has genuinely changed: Ahrefs’ own tracking shows featured snippet prevalence fell 64% in the first half of 2025 as AI Overviews expanded, so a 2017 CTR figure, real or not, describes a search results page that most featured- snippet queries no longer produce. Publishing a number without its source doesn’t just risk being wrong today; it risks staying uncorrected after the SERP it described has moved on. Anyone citing a featured-snippet statistic should be able to name the tracker, the sample, and the date, or should say plainly that no such source could be found.