The four types, and what triggers each
Google picks the snippet format from the shape of the question. You can't override it, but you can make sure your page contains the format the query wants — which is most of the work.
| Type | Queries that trigger it | What Google extracts from |
|---|---|---|
| Paragraph | What is, why does, who is, how long does | A short block of prose directly under a matching heading |
| Numbered list | How to, steps to, process for | An ordered list, or headings Google can read as sequential steps |
| Bulleted list | Best, types of, ways to, checklist | An unordered list, or a set of short subheadings |
| Table | Cost of, comparison, dimensions, rates | An actual HTML table with a clean header row |
| Video | How to, tutorial, demonstration | A YouTube video with a timestamped moment matching the query |
The format that wins the paragraph snippet
Paragraph snippets are the most common and the easiest to design for. The recipe is boring, which is why so few pages follow it.
- Phrase the heading as the question, in the words people actually type. Not "Understanding Retainer Pricing" — "How much does an SEO retainer cost in India?"
- Directly beneath it, answer the question in one paragraph of roughly 40 to 60 words. That's the observed crop length, not a published rule, but writing to it means you decide where the sentence ends rather than Google.
- Make it self-contained. It will be lifted out of the page and read with no surrounding context, so it can't start with "this" or "as we mentioned above".
- Include one concrete thing — a number, a range, a named process. "It depends on your goals" wins nothing.
- Put the nuance, the caveats and the exceptions after the answer, not inside it. Hedging in the first paragraph is what disqualifies most pages.
- Answer only that question in that block. A second question in the same paragraph makes the extract ambiguous.
Which queries are worth targeting
Snippets cluster on informational, long-tail and definitional queries — the ones with a single correct-ish answer. They're much rarer on commercial head terms, where Google would rather show ads, a local pack or a set of options.
Eligibility is the constraint people forget. Snippets are drawn from pages already ranking on the first page for that query, so "how do I get a featured snippet for a keyword I rank #40 for" has a boring answer: rank first, format second. The efficient targets are queries where you're already sitting in positions two to eight and someone else's badly formatted page holds the box.
- Pull your Search Console queries with average position between 2 and 10 and reasonable impressions.
- Keep the ones phrased as questions, or that clearly imply one.
- Search each one and look at what's in the box. If the current holder is a vague, padded paragraph, that's a cheap win.
- Rewrite your page's relevant section into the format above. Change nothing else, so you can attribute the result.
AI Overviews changed what the prize is worth
For years the snippet was called position zero and treated as the top prize. Now AI Overviews sit above it on a growing share of queries, including in India, synthesising several sources into one answer with citations off to the side.
Two honest consequences. First, winning a snippet on an informational query is worth fewer clicks than it was — the answer is being given twice before anyone scrolls. Second, the same formatting that wins snippets is what makes a page easy for a generative system to quote: direct answers, clean structure, facts attributable to a named source.
So the work doesn't change; the expected return does. Don't build a content plan on snippet counts. Build it on queries where someone who reads the answer still needs you afterwards — pricing, process, diagnosis, anything requiring judgement. We've written about the traffic side of this in what AI Overviews did to organic traffic.
How to tell whether you actually have one
Search Console doesn't report featured snippets as a separate feature, so nobody has clean data on this. What you have are proxies, and it's worth being straight about their limits.
- Average position pinned around 1.0 for a query, combined with a click-through rate that's oddly high or oddly low, usually means the box.
- A rank tracker with SERP feature detection flags snippets per keyword. Useful for trends, unreliable on any single day, and it's checking one location and one device.
- Check it yourself in an incognito window with the location set to your target city. Crude, and it's the only method that shows you what the box actually says.
- Watch clicks, not the flag. A snippet that answers the question so completely that nobody clicks is not a win, however good it looks in a report. See zero-click search.