A featured snippet is the text box Google sometimes places above every organic result, built directly from the words already on a page, with no special markup required at all. A rich result is any visual extra built from schema.org structured data in your code: review stars, a breadcrumb trail, a price range, a how-to layout. Google's own documentation confirms the split: snippets are "primarily created from the page content itself," while a rich result needs valid markup just to become eligible. Neither one can be bought, requested, or forced; Google's systems choose automatically, for one search at a time, and there's no dashboard toggle on either side. What you control is different for each: for a snippet, it's whether your content directly answers a real question in the first sentence after a heading, using a real list or table where one fits. For a rich result, it's whether the matching schema type is correctly in your code and matches what a visitor actually sees on the page.
By the numbers
- Google rewrote its own snippet documentation on January 5, 2024, to correct this exact confusion. The earlier wording implied structured data and meta descriptions fed the featured snippet. The update states plainly that snippets are primarily created from the page content itself, with the meta description used only as a backup when it describes the page better than the content does. GOOGLE DOCUMENTED
- One switch turns a page's snippet off everywhere, including inside AI Overviews. Google's robots meta tag specification documents
nosnippet(blocks all snippets for a page),data-nosnippet(blocks just one marked section), andmax-snippet(caps the snippet length, with no guarantee). Google states this scope now reaches "web search, Images, Discover, AI Overviews and AI Mode," so the same instruction that keeps a paragraph out of a classic snippet also keeps it from being quoted inside an AI Overview. GOOGLE DOCUMENTED - Google's own help documentation is explicit that a snippet can't be requested or purchased. Its systems choose automatically for each search, and content that violates its policies, including certain claims about medical, legal, or other public-interest topics, is blocked from ever appearing as a snippet. GOOGLE DOCUMENTED
- Rich results run on the opposite rule: markup is required, but still not a guarantee. Google's general structured data guidelines state that valid schema makes a page eligible for a related search feature, not that the feature will appear, and that adding it carries no separate ranking boost. One specific, timely case already changed on this site's own schema guide: the FAQ drop-down rich result was retired from Google Search entirely on May 7, 2026, so FAQPage markup is still valid to keep, but no longer earns the expandable question box it used to. GOOGLE DOCUMENTED
- Independent tracking tools disagree sharply on the size of the drop, but agree on the direction: featured snippets have gotten measurably rarer as AI Overviews expanded. Different analyses of U.S. search results put current snippet frequency anywhere from roughly 5% to the high teens of all queries, down from a widely-cited 2017 baseline near 12%, with most of the disagreement coming from different sample sizes and tracking methods rather than a single clean number anyone has settled on. INDEPENDENT RESEARCH
Two different mechanisms, side by side
Both can make a result stand out. Neither is built, checked, or earned the same way.
| Featured snippet | Rich result | |
|---|---|---|
| Built from | Page content: the visible text, lists, and tables on the page | Structured data: schema.org JSON-LD in the page's code |
| Schema required? | No. No schema type produces a featured snippet. | Yes, a specific, matching schema type for whatever feature you want |
| How to check eligibility | No dedicated tool; the practical sign is already ranking for the query | Google's free Rich Results Test, run against the live URL |
| How many at once | Usually one per search, pulled from a single page | Several types can apply to the same page at once |
| Can you opt out? | Yes, with nosnippet, data-nosnippet, or max-snippet | Yes, by removing or not adding the markup |
| Does it guarantee a ranking boost? | No | No |
The practical result of this split: a site can build flawless schema for a service page and never win a single rich result if the content underneath is thin, and a different page can win a featured snippet with zero schema at all if it directly answers a real question. See schema markup by trade for the code side of this; this guide is about the content side.
The three snippet formats, and the structure that earns each one
Google pulls a snippet from whichever shape already matches the question. Building the right shape for your own best answer is the only lever you actually have.
- A direct "what is" or "how much" question earns a paragraph snippet. Put the real question in a heading, then answer it in the first sentence that follows, plainly and completely, before adding detail. Independent studies that have measured snippet length land in roughly the same short range, something like a sentence or two, though neither Google nor any study treats that as an enforced word count, just a practical target.
- A "steps" or "how to" question earns a list snippet. Use a real
<ol>or<ul>element, not a styled paragraph with line breaks that only looks like a list. Google needs the actual HTML list markup to lift it cleanly. - A comparison or "how long/how much by option" question earns a table snippet. Use a real
<table>element with proper header cells, the same structure this guide's own comparison table above uses, rather than a grid built from styled divs. - Target a question you can already answer completely in one place. A snippet is pulled from a single page, so spreading the real answer across three different sections or three different pages means none of them is the clean, complete answer Google is looking for.
- Check whether you're already a realistic candidate before investing more time. Google has never published a required rank for snippet eligibility, but the practical, widely observed reality is that a page already needs to be ranking for the query, usually on the first page of results, to be in the running at all. A brand-new page with no ranking history yet is optimizing for a result it isn't eligible for.
Three real doubts about this
"Doesn't winning a snippet just give my answer away for free?"
Sometimes, yes, and that's a real tradeoff worth naming honestly rather than hiding. A full, correct answer in a snippet can satisfy a searcher without a click. What it also does is put your business name at the very top of the page, above every competitor, for a question your competitors may not be answering clearly anywhere. For a "near me" trade search, that visibility is often worth more than the click it occasionally replaces, especially since the same page keeps ranking normally below it either way.
"Is a featured snippet the same thing as an AI Overview?"
No, and they're selected differently, though the same nosnippet instruction now controls both. A featured snippet is one page's existing content, lifted as-is into a box above the results. An AI Overview is a generated answer that pulls from several pages at once through retrieval and synthesis, closer to the mechanism covered in our AI search optimization guide, which is the guide to read next if this one is useful to you.
"We already added FAQ schema. Doesn't that cover featured snippets too?"
No, and this is the single most common version of this mix-up. FAQ schema was built to earn the FAQ drop-down rich result, which Google retired from Search entirely on May 7, 2026; see schema markup by trade for that change in full. It was never the mechanism behind a featured snippet, which has always been a content-and-structure match, not a markup match. Keeping FAQ schema is still fine. It just isn't doing the job most sites assume it's doing.
Questions we get
Frequently asked questions
What's the actual difference between a featured snippet and a rich result?
A featured snippet is a text box built from a page's existing content, with no schema markup required. A rich result is any visual search feature, like review stars or a breadcrumb, built from schema.org structured data in a page's code. They're won in completely different ways.
Do I need schema markup to win a featured snippet?
No. Google's own documentation says snippets are primarily created from the page content itself. Structured data drives rich results, not featured snippets. Adding more schema to try to win a snippet has no effect.
Can I pay Google or request to have my page shown as a featured snippet?
No. Google's systems select featured snippets and rich results automatically for each individual search. There is no paid placement, submission form, or manual request process for either one.
How do I stop my page's content from being used in a featured snippet?
Add the nosnippet meta tag to block all snippets for the page, or the data-nosnippet HTML attribute to block just one section while leaving the rest eligible. Google states both now also block that content from being quoted inside AI Overviews and AI Mode.
Does winning a featured snippet guarantee more clicks or a higher ranking?
No. A snippet doesn't change a page's ranking position on its own, and independent studies disagree on whether holding one increases or decreases total clicks for a given search. What it reliably does is make a result take up more space at the very top of the page.
We built FAQ schema. Why doesn't our page show up in a featured snippet?
FAQ schema was built for a different rich result, the expandable question drop-down, which Google retired from Search entirely on May 7, 2026. It was never the mechanism behind a featured snippet. A snippet comes from directly answering a real question in your visible content, not from any schema type.
Sources
- Page One Power, Google Updates Featured Snippet Documentation: the January 5, 2024 clarification that snippets are primarily created from page content, not structured data or the meta description.
- Google Search Central, Robots meta tag, data-nosnippet, and X-Robots-Tag specifications: the
nosnippet,data-nosnippet, andmax-snippetcontrols, and their stated scope across web search, Images, Discover, AI Overviews, and AI Mode. - Google Search Help, How Google's featured snippets work: automatic selection, no way to request or pay for placement, and the content-policy limits that block certain snippets.
- Schema markup by trade, this site: Google's general structured-data eligibility rule (eligible, not guaranteed, not a ranking factor) and the May 7, 2026 FAQ rich result retirement, both already sourced and cited there in full.
This environment's network policy blocks direct access to developers.google.com and support.google.com, so the documentation-dated claims above were each cross-checked across multiple independent secondary write-ups quoting the same underlying Google pages, the same standard used elsewhere on this site when a primary source isn't directly reachable. The snippet-frequency decline is independently tracked by several SEO analytics tools whose published figures disagree widely on magnitude; this page states the direction only, not a specific percentage, since no single number is reconcilable across sources.