Featured snippet
A summarised answer shown at the top of the classical SERP, drawn from a single source.
A featured snippet is a summarised answer box shown above the standard organic results — often called 'position zero' — pulled algorithmically from a single ranking page and typically formatted as a paragraph, a numbered or bulleted list, or a table, depending on the query type.
Featured snippets are earned automatically; there is no separate submission or bid process. Google identifies a page already ranking on page one whose content structure and phrasing most directly and concisely answers the query, and promotes that specific passage into the snippet position, with an attribution link back to the source page.
Their relative importance has shifted as AI Overviews have expanded to cover many of the same query types that used to trigger featured snippets, sometimes replacing the snippet outright and sometimes appearing alongside it — but featured snippets remain common on well-defined factual, definitional, list, and comparison queries where AI Overviews haven't yet fully displaced classical results.
How Google selects a featured snippet
Google doesn't run a separate crawl or index for snippets — it re-uses its normal ranking process, then applies a secondary layer of extraction logic to identify whether a passage on an already-ranking page (almost always from the top 10, frequently the top 5) directly and concisely answers the literal query. Pages don't need to rank #1 to win the snippet, though they almost always need to already be ranking well for the underlying query.
The format Google chooses — paragraph, list, or table — is driven by the query's implicit structure: 'how to' queries tend to pull numbered lists, 'what is' queries tend to pull short paragraphs, and comparison or specification queries tend to pull tables. Structuring your content to match the implicit format of the query dramatically increases extraction odds.
Content structures that earn snippets
The highest-success pattern is placing a direct, self-contained 40–60 word answer immediately after the heading that matches the query, before diving into supporting detail — Google favours passages that answer completely without requiring surrounding context to make sense.
For process and how-to content, use genuine ordered <ol> lists with a short, direct sentence per step rather than long paragraphs disguised as list items. For comparison and pricing content, use an actual HTML <table> rather than a styled div grid, since Google's extraction logic specifically favours semantic table markup for spec- and comparison-style snippets.
- Answer the literal query in the first 40–60 words directly under a heading phrased close to the query itself.
- Use semantic HTML — <ol>, <ul>, <table> — matched to the query's implicit format, not just visual styling.
- Keep the direct answer self-contained; don't rely on 'as mentioned above' phrasing that requires surrounding context.
- Target queries already ranking on page one for your site; snippet wins almost always come from existing rankings, not new content.
Featured snippets vs AI Overviews
AI Overviews synthesise an answer from multiple sources and show several citations in a drawer, whereas a classical featured snippet attributes a single passage to a single source with one clear link. This means AI Overviews can dilute the traffic value of ranking well on a query even when your content is one of the cited sources, since the searcher's question may already feel answered without a click.
The content practices that earn featured snippets — a direct, self-contained, well-structured answer — are largely the same practices that earn AI Overview citations, so investing in snippet-ready structure remains valuable even as the classical snippet format itself becomes less dominant on some query types.
Measuring snippet performance
Search Console doesn't cleanly flag which impressions came from a snippet position versus a standard result, but a sudden jump in average position to below 1.0 combined with a CTR spike on a specific query is a strong indicator of a snippet win. Third-party rank trackers (Ahrefs, SEMrush, Moz) explicitly flag SERP features including featured snippets per tracked keyword, which is the more reliable monitoring method.
Common mistakes
Writing content that answers a question eventually, three paragraphs into a section, rather than immediately — Google's extraction favours the first clean answer it finds, and burying it costs the win to a competitor who leads with the direct answer.
- Burying the direct answer several paragraphs into a section instead of leading with it.
- Using visually styled lists or tables (divs with CSS) instead of semantic HTML that crawlers reliably parse.
- Targeting brand-new, non-ranking pages for snippet wins instead of optimising pages already ranking on page one.
- Ignoring that snippet wins can be lost overnight to a competitor who restructures their content more directly.
Local service-business application
Local businesses win snippets most often on pricing and process queries — 'how much does gutter cleaning cost', 'how long does a roof replacement take' — where a direct answer with a price range or timeframe, presented immediately, beats a page that only gets to the number after a long introduction. FAQ sections addressing exactly these questions, each with a self-contained 40–60 word answer, are a reliable and low-effort way to compete for these snippets against larger national competitors who write more generic content.
Snippet-triggering query patterns
| "What is" / "what does" | Paragraph snippet | Lead with a 40–60 word direct definition. |
|---|---|---|
| "How to" / "steps to" | List snippet | Use a real <ol> with a short sentence per step. |
| "vs" / "compare" / spec queries | Table snippet | Use semantic <table> markup, not styled divs. |
| "How much" / "how long" | Paragraph or list | Lead with the number or range in the first sentence. |
Frequently asked questions
- How do you get a featured snippet?
- You can't submit or request one — Google extracts it automatically from a page already ranking well for the query. Improve your odds by leading each relevant section with a direct, self-contained 40–60 word answer, using semantic HTML lists or tables matched to the query's implicit format.
- Do featured snippets increase or decrease traffic?
- It depends on the query. For some queries, winning the snippet increases clicks because it's the most prominent result. For others, particularly simple factual queries, the snippet fully satisfies the searcher and traffic drops — this is the same tension now amplified by AI Overviews.
- Are featured snippets being replaced by AI Overviews?
- On many query types, yes — AI Overviews increasingly cover the same informational, definitional, and how-to queries that used to trigger classical snippets, sometimes appearing instead of them. Both formats reward the same underlying content structure, so the optimisation work largely transfers.
- Can any page win a featured snippet, or does it need to rank #1?
- A page almost always needs to already be ranking on page one, but it does not need to be the #1 organic result — Google can and often does promote a page ranking #3 through #8 into the snippet position if its content structure most directly answers the query.
- How do I know if I have a featured snippet?
- Search Console doesn't label snippet impressions explicitly, but a jump to an average position below 1.0 with a CTR spike on a query is a strong signal. Third-party rank trackers like Ahrefs or SEMrush explicitly flag SERP features per keyword and are the more reliable way to monitor snippet wins and losses.
A 'how much does a water heater installation cost' query snippet is won by a page that opens the relevant section with 'A standard water heater installation in Austin typically costs $1,200–$2,400 including labour' rather than three paragraphs of general context before the number appears.
Need this applied to your site?
We turn concepts like these into shipped work every week.