Featured snippets
Google's reversed search result, where a passage lifted from a page is shown above the link — selected by Google's systems, requestable by nobody, and refusable with one meta rule.
Karl-Gustav Kallasmaa, Founder & CEOLast updated A featured snippet is a Google search result with its order reversed: Google describes them as "special boxes where the format of a regular search result is reversed, showing the descriptive snippet first." The passage comes from a page in the results; the link to that page sits below it rather than above.
The single most important fact about them is the asymmetry of control. Google states plainly that a site owner cannot request 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" — but documents three separate ways to prevent one. You can refuse; you cannot apply.
The mechanism
Selection is programmatic and unpublished. Google gives no formula, and every "featured snippet checklist" circulating in the industry is inference from observed boxes, not documented behaviour. What is documented is the shape of the thing being selected: a passage, extracted from a page, that stands as an answer on its own.
That is the actionable part. The unit is not the page. It is a span of text short enough to display and complete enough to read alone.
The controls, precisely
Google's robots meta tag reference defines the levers:
- `nosnippet` — "Do not show a text snippet or video preview in the search results for this page." All-or-nothing, and it removes the ordinary snippet too.
- `max-snippet:[number]` — "Use a maximum of [number] characters as a textual snippet for this search result."
0means no snippet and is equivalent tonosnippet.-1means Google chooses the length it believes most effective. Omitting the rule also leaves the choice to Google. - `data-nosnippet` — an HTML attribute valid on
span,divandsectionelements, designating specific text as ineligible for any snippet.
Google's featured-snippet guidance adds the qualifier that matters if you are using max-snippet as a targeted block: featured snippets "will only appear if enough text can be shown to generate a useful featured snippet," but "using a low max-snippet setting doesn't guarantee that Google will stop showing featured snippets for your page." It is a lever with a known direction and an uncertain endpoint.
Why it still matters when the reader is an agent
Not because the two systems are the same. They are not, and treating a featured snippet as a proxy for how an assistant will treat your page is a category error — one is a Google surface with its own selection systems, and appearing in it is evidence about Google alone.
What transfers is the discipline it enforces. Both a snippet extractor and a retrieval pipeline select a passage and present it away from its page. Text written to survive that trip has the same properties in both cases:
- The heading states the question; the first sentence answers it.
- The qualifier lives in the same sentence as the claim, because the sentence before it will not travel with it.
- Definitions, figures and steps appear in the form a reader needs, not as a promise that the detail is further down.
- The passage names its own subject, rather than saying "it" and relying on a paragraph three screens up.
A page written that way is legible to a passage-level reader of any kind. That is the durable benefit; the box itself is a byproduct.
Failure modes
- Believing you can opt in. Every technique aimed at guaranteeing a snippet is aimed at an interface Google says does not exist.
- Using `nosnippet` to block a featured snippet. It works, and it also removes your ordinary result snippet, which is usually a worse trade than the problem being solved.
- Assuming `max-snippet` is a switch. Google explicitly says a low value does not guarantee the featured snippet stops.
- Optimising for the box on queries where the box is the whole answer. If the reader's entire need is the number, winning the snippet wins the answer and loses the visit. See zero-click search.
- Reading a featured snippet as an AI-visibility signal. Different systems, different selection. AI Overviews and assistant answers are their own surfaces with their own behaviour.
Frequently asked questions
Can I request a featured snippet?
No. Google's documentation says its systems decide; there is no opt-in.
How do I block one?
nosnippet, a low max-snippet value, or data-nosnippet on the specific passage.
What does max-snippet:-1 mean?
Google picks the length it thinks most effective — the same as specifying nothing.
Does snippet optimisation help with AI answers?
Only in that both select passages. Write self-contained sections; do not treat one surface as evidence about the other.
Terms related to Featured snippets
A search that ends without the reader visiting any website, and the measured gap between sessions that show an AI summary and those that do not.
Google's AI-generated summary at the top of a results page, and the snippet controls that decide whether your page can appear inside one.
The standardised file that tells crawlers what they may fetch, now the main place where AI training and AI retrieval access are decided separately.