What Is a Featured Snippet? Winning Position Zero

Aug 10, 2026 · SEO Glossary

Search "why is my monitor flickering" and look at what sits above the first blue link: a box quoting two sentences from some support article, with the page's title and URL underneath. Google pulled that passage out of the page, decided it answered the question, and promoted it above every organic result — including, sometimes, above the page that ranks #1. That box is a featured snippet, and it's the one SERP feature an ordinary site can win through formatting decisions alone.

What is a featured snippet? It's an extracted answer — a passage, list, or table lifted from a ranking page — displayed in a dedicated box at the top of Google's results, with attribution and a link to the source. SEOs call the slot "position zero." Unlike knowledge panel facts, which Google compiles from its own knowledge graph, a featured snippet is always quoted from a specific webpage — possibly yours.

The four formats

The markup column is the operative one: Google extracts structure it can parse. A step sequence written as a wall of prose can't become a list snippet; the same steps in an <ol> can. Paragraph snippets dominate (roughly three-quarters of all snippets in most studies), but list and table snippets are less competitive precisely because fewer pages format for them.

How Google chooses the featured snippet source

Two facts anchor everything else. First, snippet sources come from pages already ranking on page one for the query — overwhelmingly the top five. You can't format your way to a snippet from position 40. Second, within those candidates, Google picks the passage that best answers the question — which is why position 3 regularly takes the snippet from positions 1 and 2. The #1 page ranks on overall authority and relevance; the snippet goes to whoever has the cleanest extractable answer. That's the entire opportunity: among pages that already rank, the snippet is won on passage quality and structure, not on link profiles.

Structuring content to win one

1. Find realistic targets. In Search Console, filter to queries where you rank 1–5 that are phrased as questions or trigger a snippet currently (check the SERP). Existing snippets held by weaker passages are the best targets — snippets change hands constantly.
2. Ask the question, then answer it immediately. The winning pattern is almost mechanical: a heading phrasing the question the way searchers do, followed directly by a 40–60 word self-contained answer. Definition first, elaboration after. Pages that make Google hunt through preamble lose to pages that don't.
3. Match the format to the query. Steps get a real <ol>. Comparisons get a real <table> with header cells. "Types of" gets a <ul>. For list snippets, a small bonus mechanic: if Google truncates your list ("More items..."), users must click through to see the rest.
4. Answer the cluster, not just the query. Pages holding snippets for one question often pick up People Also Ask placements for the neighbors — structure several related Q&As on the same page with the same heading-then-answer pattern. A well-built cornerstone page can hold multiple snippets across its sections.

Structured data, for the record, is not a snippet factor — Google extracts from visible HTML. Though marking up genuine Q&A content has its own separate uses, covered under FAQ schema.

The traffic question: is position zero always a win?

Mostly, but not automatically. Since 2020, a page shown in the snippet is not repeated as a normal result below — the snippet is your listing. For queries where the searcher needs the full explanation, the snippet's prominence raises CTR. For queries fully answered by the extracted sentence ("how many grams in an ounce"), the snippet satisfies without a click. Check before investing: if the answer is irreducibly one line, the snippet mostly buys brand impressions, not sessions. That's rarely worthless — but it's not traffic. If a snippet actively cannibalizes clicks you'd rather have, opt-outs exist at passage granularity: <meta name="robots" content="nosnippet"> kills all snippets for the page, max-snippet:[n] caps extract length, and wrapping specific HTML in a data-nosnippet attribute excludes just that passage. Blunt instruments — most sites should never need them.

Tracking what you hold

Search Console doesn't label snippet impressions separately — a snippet counts as position 1, which quietly inflates your average-position stats for those queries. Practical tracking: rank trackers with SERP-feature detection show which snippets you hold and which competitors hold; a sudden CTR jump at a stable #1–3 ranking usually means you just won the box, and the reverse means you lost it. Losses have mundane causes worth checking in order — a competitor restructured a cleaner answer, your page's ranking slipped out of the candidate pool, or a template change broke the extractable structure. That last one is the silent killer: a redesign that swaps your <ol> steps for styled <div>s can cost every list snippet you hold, which is a good argument for auditing your site's structure after significant template changes rather than assuming the markup survived.