- Write the answer first: put a self-contained, direct answer of roughly 40 to 60 words directly under a question-style heading, so the passage still makes sense when lifted out of the page.
- Match the format the live box already uses: paragraphs for what-is and why queries, ordered or bulleted lists for steps and sets, and a real HTML table only for side-by-side comparisons.
- Before writing, search your target query and record which format holds the box, which page holds it, and where your page ranks, then build a sharper version of that answer.
Featured snippets have no application form. There is no markup to add, no setting to flip, and no way to ask Google for the box. Google’s own documentation is blunt on this point: a site can’t mark a page as a featured snippet, because Google’s systems decide. Most advice about winning position zero skips that fact and jumps straight to formatting tricks. Formatting matters, but it comes last. The box goes to the passage that answers a question most cleanly, on a page Google already considers relevant enough to show.
So the job is narrower than “optimize for snippets.” You are making one passage on one page easy to find, easy to lift, and hard to misread out of context. That is a writing problem before it is an SEO problem, and it is the same problem AI answer engines face when they quote a source.
Featured snippets: what they are and what you can’t control
A featured snippet is the excerpt Google shows in a box above the first organic result, with the source page’s title and link underneath. People call it position zero because it sits above rank one. The same kind of excerpt can also appear inside the “People also ask” group, so it is worth knowing both places.
When a reader clicks through, the link takes them to the matching section of the page, not just to the top. The section you wrote is the section the reader lands on, so the passage has to work as a destination as well as an answer.
Two constraints follow from how the feature works.
First, you can’t win the box without ranking. Google doesn’t publish a rule about how far down a page can rank and still supply a snippet, but in practice the box is overwhelmingly pulled from results already on page one. Studies disagree on how much comes from positions two through ten, so don’t plan around a precise number. Plan around this instead: a snippet rarely rescues a page that isn’t in the running.
Second, you win at the paragraph level, not the page level. A strong page with one weak passage under the right heading loses the box to a weaker page with a sharp one. Your real unit of work is the section.
How Google decides which passage gets the box
Google doesn’t publish its selection criteria, but its guidance and the boxes themselves show three things doing most of the work.
-
The query has an answer shape. Question-type queries (“what is”, “how to”, “why does”) and comparison or listing queries (“X vs Y”, “best tools for”) produce snippets far more often than navigational or purchase-ready queries. Knowing what the searcher wants before you write is the whole game here. The four search intent types cover how to tell which shape a query expects.
-
A passage answers completely, standing alone. Extraction works on passages, so a passage that depends on the paragraph above it can’t be cleanly lifted. “This is why it matters” is not an answer, because the passage never says what “this” refers to.
-
The page is credible for the topic. Relevance and authority get a page into the candidate set. The passage decides which candidate wins.
Notice what isn’t on that list: schema markup, a special heading tag, a minimum word count. Google’s documentation doesn’t mention paragraphs, lists or tables at all, and it gives no exact minimum length, saying the length depends on the information, the language and the device. Format is a tiebreaker inside a field you have already qualified for. It is not a ticket in.
The three snippet formats, and how each one gets extracted
Before you choose a format, know the base rates. Third-party tracking of U.S. results, including figures STAT Search Analytics has reported, puts paragraphs at roughly 70 percent of snippets, lists at roughly 21 to 25 percent, and tables at about 4 to 5 percent. Those numbers come from outside Google and vary by study and year, so read them as direction. The direction is clear, though. Paragraphs dominate, lists are a strong second, and tables are a niche.
| Snippet format | Queries it suits | What the snippet block contains | Common failure |
|---|---|---|---|
| Paragraph | “what is,” “why does,” “does X” | One self-contained answer of about 40 to 60 words | An opener like “It” or “This” that depends on the previous section |
| List | “steps to,” “types of,” “best X for Y” | A framing sentence, then a parallel list of substantive items | Vague items, or a long list with the answer buried late |
| Table | “X vs Y,” “plan prices,” “specs compared” | A real table with a header row, three to six rows, units in the headers | Prose forced into cells, or merged cells that break the structure |
Paragraph snippets
Paragraph snippets answer “what is” and “why” queries with one compact passage. The mechanism is simple. The opening sentence has to name the subject and answer the question, because that is the sentence most likely to be shown alone. Start with the subject, not a pronoun. A sentence that opens with “It” or “This” makes the passage depend on what came before, and a snippet cannot carry that dependency.
Length is the other variable. A common working target is 40 to 60 words for the core answer. That is long enough to be complete and short enough to display in the box without an awkward cut. Google gives no official number, so treat the range as a convention to test against the boxes you actually see, not a rule to obey blindly.
List snippets
List snippets answer “steps to,” “types of,” and “best X for Y” queries. Google extracts the list itself, and the heading directly above it often becomes the label. Write a heading that names what the list contains, such as “Steps to set up a redirect” or “Five types of duplicate content,” and put one framing sentence before the first item.
Items need to be parallel: the same grammatical form and roughly the same level of specificity. Snippet lists are usually cut off after the first handful of items, so put the most important items first, not the alphabetically convenient ones. Use an ordered list when sequence matters, as with steps, and bullets for a plain set. Each item should carry a real point of one to three sentences, not a three-word label.
Table snippets
Table snippets appear for comparison and specification queries: “X vs Y,” “plan prices,” “compare tools by feature.” The table has to be a real table with a header row, and its cells need to hold data a reader scans, not sentences. Keep it to roughly three to six rows, put units in the headers, and avoid merged cells, which make the structure harder to parse.
Tables are rare, which cuts both ways. Competition for them is thinner, but the query has to be genuinely tabular. Forcing a table onto a “what is” question wastes the section and gives you a weaker answer than a paragraph would.
Build the answer block: the four parts of a liftable section
Every snippet-ready section, whatever its format, has the same four parts. Think of it as a unit you could cut out of the page and still have something useful.
-
The heading. Write it in the searcher’s words: a question or a plain “how to” phrase. “Why canonical tags matter” beats “The canonical situation” every time. Clever headings are a common reason a good section never matches a query, because the match leans on the heading first.
-
The direct answer. The first passage under the heading answers the question in full, in 40 to 60 words, with no preamble. Everything after it is support. If a reader stops after that paragraph, they should still walk away with the answer.
-
The support. Lists, tables, examples, numbers and caveats go here. This is where you earn the depth that makes the answer trustworthy, and where a reader who wants more finds a reason to keep going.
-
The end point. The next heading tells both the reader and Google where one answer stops and another begins. A section that wanders across two questions is hard to extract cleanly, so keep each one to a single question.
The two-sentence test: read only the first two sentences under each heading. If they answer the heading's question, you have a snippet candidate. If you need the third paragraph to make sense, rewrite the first two.
A worked example: rewriting one section for position zero
Take a query that shows up constantly in technical SEO: what is a canonical tag. A typical first draft opens like this.
Before: Canonical tags are one of the more misunderstood parts of technical SEO, and they come up a lot once a site starts to grow. There are a few things worth knowing before you start using them, and the details matter. Let’s look at how they work.
Nothing in that passage can be quoted. It is an introduction to an answer that never arrives. Here is the same section with the answer moved to the front.
After: A canonical tag tells search engines which URL is the preferred version of a page that can be reached at more than one address. You add a <link rel="canonical"> element to the head of each duplicate, pointing at the version you want indexed. Google treats it as a strong hint rather than a command.
The rewrite runs about 55 words. Its first sentence names the subject in full and makes a claim a reader can check. The second gives the one action the reader can take. The third adds the caveat that prevents the most common misreading.
Now the support can do its job. Redirects, cross-domain canonicals, and what to do when Google ignores your tag all go below the answer, as separate sub-points. The reader who wanted a definition already has it. The reader who needs the edge cases finds them where they expect to look.
A repeatable process for one target query
Run this sequence for each query you want to win. Once you have done it a few times, a section takes about an hour.
-
Pick one query and look at the live results. Search it in a private window, or use a rank tracker’s SERP view. Note whether a box appears, which format it uses, and which page holds it. If no box appears at all, check whether the query is snippet-eligible before you invest in it.
-
Match the format the box already uses. If Google shows a paragraph, write a paragraph. Writing a list where Google shows prose is the most common mismatch, and it is the easiest one to avoid.
-
Write the heading in the query’s words. Stay as close to the searcher’s phrasing as your editorial voice allows.
-
Write the direct answer first. One self-contained passage of 40 to 60 words, with the subject named in the opening sentence.
-
Build support that beats the current holder. Add the list, table, example or caveat the reader needs next, and make it more precise than the existing version: a worked number, a named standard, a specific failure mode.
-
Check the boundary. Confirm the next heading opens a genuinely different question. Two adjacent sections that answer the same thing confuse both readers and extraction.
-
Measure, then revise. After a few weeks, check whether the box appears and whether clicks and rankings moved. If the holder changes or the format shifts, revise the answer to match.
Why snippet structure is also AI-answer structure
Featured snippets and AI answers are not separate systems, and that is the real reason to care. Google’s documentation for AI Overviews and AI Mode says there are no additional requirements to appear in them beyond standard SEO. A page has to be indexed and eligible to show with a snippet. The systems also use query fan-out, issuing several related sub-queries, to assemble a wider set of supporting links. A section that answers one sub-question cleanly has a better chance of being selected for it.
The more useful overlap is in the shape of the text. An answer engine that retrieves a passage and quotes it needs what a featured snippet needs: a self-contained answer, a named subject, and specific claims. A vague paragraph that only makes sense inside the article gives the engine nothing to quote. That is why I would treat the answer block as the unit of AI visibility, not the page. For how answer engines choose and attribute sources, see how to get cited by AI engines.
Now the uncomfortable part. Snippets are shrinking as a share of results. One Ahrefs analysis of U.S. desktop searches reported that the share of queries showing a featured snippet fell from about 15 percent in January 2025 to about 5.5 percent by June 2025. Other trackers report different figures, so read exact numbers with caution. The direction is the lesson. Don’t build a strategy on the box alone. The answer-block discipline pays off on the plain organic listing, in AI answers, and in the next SERP format you haven’t seen yet.
Measuring the win, and the mistakes that cost it
Search Console doesn’t give you a clean featured snippet report, so you have to assemble the picture yourself. Track whether you hold the box over time with a rank tracker that records SERP features per keyword. Then compare each query’s click-through rate before and after you take the box. Published CTR figures conflict badly across studies. Some suggest snippets lift clicks, while others suggest the answer on the results page satisfies the question and clicks fall. Your own before-and-after numbers are the only ones that will settle it for your site.
When the box doesn’t come, the cause is usually one of these.
- A buried answer. Two hundred words of introduction before the first answer makes the passage hard for readers and extraction alike. Move the answer to the top of its section.
- A clever heading. “The secret to clean URLs” tells no one what the section answers. Headings are what a reader scans and what a query match leans on first.
- A passage that leans on its neighbors. A first sentence like “This is why it matters” can’t stand alone. Read it by itself. If it fails, rewrite it.
- A forced format. A table built from prose, or a fourteen-item list with the answer hidden in item twelve.
- Structured data as a shortcut. Schema markup helps Google understand a page, but Google doesn’t require it for snippets. It also limited FAQ rich results in 2023 to well-known government and health sites, so FAQ markup on a typical SaaS blog buys you little.
Don't block to protect: the nosnippet directive removes a page from every snippet, featured or regular, and Google says AI Overviews and AI Mode require snippet eligibility, so the same block takes you out of those too. Lowering max-snippet only makes a snippet less likely; it doesn't guarantee one stops. Reserve these controls for content you truly need to restrict.
The honest wrap-up
The box is a byproduct of doing the unglamorous work well. The page has to rank. The query has to have an answer shape. The section has to open with an answer that holds up when lifted out of the page. You can’t request the box, and the share of queries that display one is falling. What you can control is whether each section is liftable, and that discipline travels to plain organic results, to AI answers, and to whatever SERP feature comes next.
That discipline is what AutoSEO Stack builds into every article it publishes: research the query first, lead with the answer, and hold each page to the same quality bar. You can see how the product handles that in the features overview, and the AI visibility section covers the answer-engine side. If you want to see the approach running on your own site, that is the best place to start.