What a featured snippet really is
Strip away the marketing language and a featured snippet is a single answer block Google places above the ten organic results, built by extracting text, a list or a table from a page it already trusts on that query. The label « position zero » is useful shorthand but misleading: there is no zeroth ranking slot you compete for. Google decides a query deserves a direct answer, then scans the pages already ranking, usually inside the top ten, and lifts the passage that best resolves the intent. The page keeps its normal organic position underneath, or sometimes the snippet replaces its blue link entirely.
That distinction drives everything operational. You cannot « target a featured snippet » for a query where your URL ranks fourteenth. The snippet is a formatting layer applied on top of an existing ranking, which means the prerequisite is the same as for any organic visibility: be on page one first, then make your answer the easiest to extract. This is also why snippet work belongs in your on-page and content workflow, not in a separate « position zero campaign » bucket that some agencies still sell.
Here is a short visual primer on what these blocks look like across query types before we get into the mechanics.
How it actually works in 2026
Google extracts snippets in a handful of formats, and the format is dictated by the query, not by your preference. Paragraph snippets answer « what is » and « why » questions with a short block of prose. List snippets, ordered or unordered, answer « how to », « best », « steps » and « types of » queries. Table snippets surface comparison or pricing data that already lives in an HTML table on the source page. Video snippets pull a timestamped clip, increasingly for procedural queries. The practical takeaway: look at what format Google currently shows for your target query on the wider results page you are competing on, then build your passage in that exact shape.
Measurement is where most teams get sloppy. You do not assess snippet ownership by glancing at a logged-in, personalized browser. You track it in Google Search Central performance data, where a query showing average position close to 1 with high impressions and an unusually low click-through rate often signals a snippet that answers fully without earning the click. For coverage at scale, the SERP-features filter in Ahrefs or Semrush flags which of your keywords trigger a snippet and who currently owns it. Ahrefs research has consistently found that featured snippets appear for only a minority of searches and that the snippet URL is almost always already ranking in the top ten, which confirms the « rank first, format second » logic rather than contradicting it.
There is no special markup that forces a snippet. Schema does not award one, and no plugin grants one. What Google rewards is a clean, self-contained answer near the relevant heading, written so the extraction algorithm can lift it without surrounding noise. The query understanding stack, the same system behind the related questions box, decides which passage on the page maps to the searcher's intent.
Featured snippet vs AI Overview
The honest 2026 read: AI Overviews are cannibalizing the surface featured snippets used to own. Since the generative answer rollout across 2024 and 2025, informational queries that once reliably produced a paragraph snippet now often render an AI-generated summary first, pushing the classic snippet down or removing it. A featured snippet quotes one source verbatim and links to it. An AI Overview synthesizes several sources into new text and cites them as a cluster, which dilutes the single-source visibility that made snippets valuable.
So « are featured snippets still a thing »? Yes, but with a shrinking footprint, and the trend line matters more than the current count. On transactional and navigational queries, and on many local searches, classic snippets remain common because Google is cautious about generating answers there. On broad informational queries, expect the Overview to win the top slot. The strategic implication is that the same content discipline that earns a snippet, a tight extractable answer mapped to intent, is also what gets a passage cited inside a generative answer. Teams that want durable visibility now work both surfaces together, which is exactly the brief behind showing up inside generative answers, not just blue links. Betting your roadmap on snippet count alone is fighting last cycle's war.
Formatting a page to earn the snippet
Optimization here is unglamorous and mechanical. First, answer the question directly and early. For paragraph snippets, place a self-contained answer of roughly 40 to 60 words immediately under a heading that mirrors the question. Do not bury it after three paragraphs of context. Second, match the format to the query: if Google shows a list snippet, give it a real ordered or unordered list with parallel, scannable items. If it shows a table, ship an actual HTML table, not an image of one. Third, target the question and long-tail variants explicitly in your headings, because question-shaped queries trigger snippets far more often than head terms.
The tooling step most people skip is opportunity discovery: finding the queries where you already rank in the top ten but do not own the snippet. That is the cheapest win available, and this walkthrough shows the workflow.
Once you have the target list, the on-page execution is repeatable: a clear H2 or H3 phrased as the query, a concise extractable answer directly beneath it, supporting depth below for the reader who clicks through, and structured formatting where the SERP calls for it. The same passage discipline that wins a snippet is what lets engines lift your content elsewhere, which is why we treat it as part of how you structure content so search and answer engines can quote it. This practical, repeatable routine is laid out clearly here.
None of this works without the ranking prerequisite. If the page is not on page one, formatting is theatre. Getting there on competitive informational queries usually still needs referring-domain authority, which is the slow part of the job and where a calibrated effort to earn the links that lift a page into the top ten in the first place pays off before any snippet work begins. At Stringer we operate the editorial side and the link side in-house for our own media precisely because the snippet only becomes reachable once the page already ranks.
Where it goes wrong
The recurring failure is chasing snippets that cost clicks. If Google answers the query completely inside the box, the no-click rate climbs and you have donated your content to the SERP for zero traffic. The Ahrefs analysis of click distribution showed the snippet position often captures fewer clicks than you would expect, because the answer is already on screen. Fight for snippets where the lifted answer still leaves a clear reason to visit: a tool, a deeper comparison, pricing, a next step. Where it does not, you may prefer to keep the answer out of the box.
That is what nosnippet and data-nosnippet, both documented in Google Search Central, are for. The page-level nosnippet meta directive removes the page from snippet eligibility, and the data-nosnippet HTML attribute excludes a specific passage while keeping the rest available. Use them deliberately when a snippet would cannibalize a conversion page rather than feed it.
Two persistent myths waste time. The first is that only the number-one organic result can be snippeted: in reality any top-ten page is eligible, which is why a page ranking sixth can leapfrog into the box with better formatting. The second is that a specific plugin or schema type grants the snippet: it does not, and vendors who sell « position zero » as a product are selling formatting hygiene with a markup. The last common mistake is letting snippet content go stale. Google re-evaluates the source continuously, so an outdated answer, a changed price, a superseded process, quietly loses the box to a fresher competitor. Treat your snippet-owning passages as living content and revisit them on the same cadence as your priority rankings.