Featured snippets are the short answers that appear above the first organic result. You cannot request one, and there is no markup that guarantees one. What you can do is write pages where a clear answer is easy to extract. That habit improves the page for readers whether or not a snippet ever appears.
What a snippet actually is
A snippet is a search engine quoting or summarising your page to answer a question directly. It usually takes one of four shapes: a paragraph, a numbered list, a bulleted list, or a table. The shape tends to follow the question. Definitions get paragraphs. Processes get numbered steps. Comparisons get tables.
Because the format follows the question, you can improve your odds by matching the format deliberately. A recipe written as one long paragraph is harder to quote than the same recipe written as steps.
Answer in forty to fifty-five words
The most common snippet length for a paragraph answer is roughly forty to fifty-five words. That is not a rule to write to, but it is a useful target for the first paragraph under a question heading. Say the thing, completely, in two or three sentences. Then expand underneath.
Write the answer so it makes sense out of context. Avoid starting with it depends, or with a pronoun that refers to the previous paragraph. A quoted sentence that begins with this means nothing when it appears alone at the top of a results page.
Use headings that match the question
Write an h2 that repeats the question in the words people use: how long does delivery take, what does a minimum order include, how do you store printed stock. Then answer immediately below it. Do not put a paragraph of introduction between the heading and the answer.
If the question has variants, answer the main one and mention the variants inside the answer. One heading per question keeps the structure legible to both readers and machines.
The first sentence under a question heading should be the answer. Everything after it is support.
Lists and tables earn their place
Steps belong in an ordered list, with one action per item and no more than eight items. Comparison criteria belong in a table with a clear first column. Both formats are easier to scan and easier to quote than the same information in prose.
Do not force a list where a sentence would do. A three-item list of vague phrases helps nobody. If the items do not have a parallel structure, they probably belong in a paragraph.
One practical test: read the section aloud to someone who has not seen the page. If they can repeat the answer back, the structure works. If they ask what you mean, the paragraph is doing too many jobs at once.
Do not over-format
Some pages chase snippets by turning every section into a bullet list, which makes the page read like a slide deck. Readers who want nuance leave. Use the format the content needs, and let the rest be prose.
Skip tricks such as hidden text, fake question blocks, or repeating a question five ways in one heading. They make the page worse and are easy to spot.
Measure without obsessing
Search Console does not label snippets directly, but you can infer them. A page whose average position jumps to one or two for a question query while clicks stay modest is often being quoted. Compare the query list against your headings; the phrases people search usually mirror the headings you wrote.
Keep a small note of which pages answer which questions. When you update a page, check that the answer paragraph still says the same thing after the edit.
Checklist for an answer-first page
- Does each question heading use the words a reader would type?
- Is the direct answer in the first two sentences under the heading?
- Is the answer between forty and sixty words and understandable alone?
- Does the format match the question: steps, list, table, or prose?
- Is there no filler between heading and answer?
- Are facts dated and checkable?
- Does the page still read well for someone who never sees a snippet?
Write for the reader who wants the answer in ten seconds. The snippet, if it comes, is a side effect of that discipline.
