Featured Snippets Optimization: Structure Answers Google Can Quote

Search for "how long does it take to boil an egg" and the first thing you may see is not a list of websites but a box with the answer in it, with the source page named underneath. That box is a featured snippet. Site owners often want one, because the page it quotes gets a prominent place on the results page.

The honest starting point is that you cannot ask for a featured snippet. Google's documentation says its systems decide whether a page would make a good one for a given search, and it offers no markup or setting to claim one. What you can do is write pages whose answers are easy to find, easy to quote and correct, which is also good writing for readers. This guide is for site owners and writers who want to structure content that way, check that nothing on the site blocks snippets, and keep expectations realistic. You will finish with a method for choosing questions, a format for each type of answer and a list of the controls that switch snippets off.

Short answer: Featured snippets are boxes at the top of Google results that show an excerpt from a page answering the query. You cannot mark a page to get one. Google's systems choose. To be a good candidate, put a clear question as a heading, answer it directly in the text below, and use a list or table where the content calls for one.

Before you begin

You need edit access to the pages you want to improve, a way to look at your page source (browser "view source" is enough) and access to Search Console. If you do not yet have it, set it up with Set Up Google Search Console: Complete Website Owner Checklist. Allow an hour per page.

Be ready to change visible text only. Do not change meta robots rules, templates or URLs for this goal. If you use caching or a CDN, clear it after editing so Google fetches the current page. Save a copy of the old text first.

What is a featured snippet, and how does Google choose one?

Google describes featured snippets as special boxes where the format of a normal search result is reversed: the descriptive text comes first. They can also appear within a "People also ask" group. Google's help page adds that they appear at the top of results, in People also ask and next to Knowledge Graph information, that they are especially useful on phones and with voice assistants, and that they are chosen from sites Google finds, based on how well they answer the query and how helpful they are.

Four facts to keep in mind:

You cannot mark a page as a featured snippet. Google's systems decide whether a page makes a good one for a search.
It can differ by search. A page may produce a featured snippet for one question and not for another.
There are content rules. Google's help page says it blocks snippets that violate its policies, and that on public-interest topics (civic, historical, medical and scientific) a snippet should not contradict well-established or expert consensus.
Clicks go to the matching section. Google says a click on a featured snippet takes the reader to the relevant part of the page, with no extra markup from you, or to the top of the page when it cannot find that part with confidence.

Google also says that it does not promise to crawl, index or show any page. Nothing below changes that.

Which formats do featured snippets take?

Google's documentation does not publish a list of formats or a template, so none of the structures below is an official requirement. In everyday searching you will see short text answers, steps in a numbered list, items in a bulleted list and rows from a table. Use them as a practical guide to presenting content clearly, matched to the question:

Type of question	Natural answer shape	How to mark it up in HTML
"What is ...?"	One short paragraph that defines the term	A `<p>` directly under the question heading
"How do I ...?"	Steps in order	A numbered list, `<ol>`, with one step per item
"What are the types of ...?"	Items with no order	A bulleted list, `<ul>`
"X vs Y", "how much ...?"	Values compared on the same attributes	A real `<table>` with header cells
"Why does ...?"	A short reason, then detail	A paragraph, then supporting sections

The principle is to choose the shape the reader needs. Do not force a list onto an explanation or hide a comparison in prose.

Step-by-step instructions

Step 1: Pick questions your page can truly answer

Start with questions you already answer better than most pages: those from customer emails, support chats and the queries in Search Console. The performance report lists the words people typed (see Read the Search Console Performance Report: Clicks, CTR and Position). Search the question yourself and read what comes up, since the results and their layout vary by device, language and location. Match the page to the intent behind the question, as in Search Intent: How to Match Each Page to What Searchers Want. If the best answer needs a whole page, give it a whole page; do not squeeze it into a box.

What success looks like: A short list of questions, each tied to one page that already deserves to answer it.

Step 2: Put the question in a heading, in the words people use

Write a heading that is the question itself, for example <h2>How long should you rest a steak?</h2>. Use the phrasing a person would type or say aloud. Do not stuff extra keywords into it. The heading gives the answer below it a clear label for readers, for assistive technology and for crawlers. Follow the outline rules in Heading Structure for SEO: Use H1 to H6 for Meaning, Not Style.

What success looks like: The heading reads like a question a real person asked.

Step 3: Answer in the first sentences below the heading

Give the direct answer immediately, as a stand-alone paragraph, then add the detail. A practical length is a few sentences, roughly 40 to 60 words; that is a writing habit, not a Google number. Google says featured snippets appear only when enough text can be shown, and that the minimum varies by content, language and platform. A tight first answer gives Google a clear passage to work with, though it cannot decide what Google picks. Example:

<h2>How long should you rest a steak?</h2>
<p>Rest a steak for about five minutes after cooking, longer for thick
cuts. Resting lets the juices settle so they stay in the meat when you
cut it. Cover it loosely with foil to keep it warm.</p>
<p>Thicker cuts and whole roasts hold heat longer, so ...</p>

State only what you can stand behind. If the true answer is "it depends", say what it depends on in the first sentence.

What success looks like: The first paragraph under the heading answers the question without needing the rest of the page.

Step 4: Use a list or table when the answer is a list or table

For a procedure, use a real ordered list, not paragraphs that start with "First" and "Second". For comparisons, use an actual table with a header row, not an image of one:

<h2>How do you bleed a radiator?</h2>
<ol>
  <li>Turn the heating off and let the radiator cool.</li>
  <li>Fit the radiator key into the bleed valve.</li>
  <li>Turn the key slowly until air hisses out.</li>
  <li>Close the valve when water appears.</li>
</ol>

Keep each item short and complete. After the list, add the details people need: what to do if water sprays, how to check the pressure. Do not turn a page into a series of unrelated lists simply to look like a snippet.

What success looks like: The markup matches the content: ordered steps are an <ol>, comparisons are a <table>.

Step 5: Support the answer with depth and evidence

A snippet quotes a short passage, but the page still has to deserve it. Add the explanation, edge cases, a source and, where it applies, your own first-hand detail. Google's ranking systems guide describes a passage ranking system that can identify individual sections of a page and use them to judge relevance, which is one more reason to give each section a clear heading and a self-contained answer. Check facts against an official source, especially on health, money and safety topics, where Google's policies and quality guidance set a high bar. Helpful Content Checklist: Review Your Pages Against Google's Advice is a good review to run after editing.

What success looks like: The page is useful even to a reader who ignores the snippet and reads on.

Step 6: Check that nothing blocks snippets

Google gives page owners several controls over snippets. They work as follows:

nosnippet as a robots rule stops Google showing a snippet for the page, including a featured one.
data-nosnippet on an element excludes that text from featured and regular snippets. If a page has both rules, nosnippet takes priority.
max-snippet:[number] limits the length of a snippet. Google notes that featured snippets need enough text to show, but gives no minimum, and that a low value may not stop a featured snippet, so nosnippet is the only option that reliably does.

<meta name="robots" content="max-snippet:160">
<p data-nosnippet>This text will not appear in any snippet.</p>

Open the page source and search for nosnippet, max-snippet and data-nosnippet. If a template or SEO plugin added a low max-snippet value or a site-wide nosnippet, decide whether you really want it. The rules for meta robots are covered in Meta Robots Directives Explained: noindex, nofollow, nosnippet. Also confirm the page can be crawled and is indexed; see How do I check if a page is indexed by Google?.

What success looks like: No unintended snippet rule is present, and the page is indexed.

Step 7: Review after Google has recrawled, and keep expectations modest

After a few weeks, search the target question a few times from different devices and note what appears. Compare the clicks and impressions for the page in Search Console. Do not treat one check as proof, since results vary and may change at any time. If your page does not appear in a featured snippet, that is normal and not an error. Improve the page for the reader and move on. If you do appear and lose the spot later, do not undo your work; another page may now be a better candidate for that search.

What success looks like: You have a dated note on what you saw, with no conclusions drawn from a single search.

Do I need FAQ schema or other markup to get a featured snippet?

No. Google says you cannot mark a page for one, and its page on featured snippets describes no special markup. FAQ markup is a separate topic, and Google has stopped showing the FAQ rich result; FAQ Schema in 2026: What FAQPage Markup Still Does and Does Not Do explains the current position. Write visible, accurate question-and-answer content first. Markup can describe that content but does not create a snippet.

Final verification checklist

Each target question has one page that fully answers it.
The question appears as a heading in the words readers use, and you have accepted that Google, not you, decides about featured snippets.
A direct answer sits in the first paragraph under the heading.
Lists use <ol> or <ul> and comparisons use a real <table>.
The page has depth and sources beyond the short answer.
No unintended nosnippet, data-nosnippet or low max-snippet rule is present.
The page is crawlable and indexed.
You have recorded what you saw in results, with the date, device and location.

Common mistakes to avoid

Chasing the box instead of the reader. A page written only to be quoted usually reads poorly. Write the answer first, then the substance.
Answering a different question. A heading that promises one thing and an answer that delivers another does not help anyone. Match intent.
Faking structure. A table drawn as an image or a list built from line breaks cannot be parsed as one. Use proper HTML.
Leaving a global nosnippet or tiny max-snippet in a template. Check the source before concluding the content is the problem.
Padding the answer. Long preambles push the useful sentence down. Lead with it.
Copying another page's answer. Google's guidance warns against rewording others' content without adding value. Add your own detail.
Treating a snippet as a result you own. It can change or disappear. Keep the page healthy either way.

Frequently asked questions

How do I get a featured snippet?

You cannot request one. Write a clear question heading, a direct answer, supporting detail and sensible lists or tables, and make sure nothing blocks snippets. Google then decides, and appearing is never certain.

How long should a featured snippet answer be?

Google gives no required length. A few sentences, roughly 40 to 60 words for a text answer, is a sensible writing target, and the first paragraph should stand alone.

Do featured snippets always take clicks away from my site?

Google's documentation does not say either way. A click on a featured snippet leads to the matching section of the page, so a clear structure helps readers get to the detail.

How do I stop a page from appearing as a featured snippet?

Add nosnippet to block all snippets for the page, or data-nosnippet to hide part of it. A lower max-snippet may reduce the text, but Google says it might not stop a featured snippet.

Does the meta description appear in a featured snippet?

Not reliably. Google builds snippets mainly from page content and only sometimes uses the meta description. See Write SEO Title Tags and Meta Descriptions That Match Search Intent.

Official references

Next step: Try the free website sample to see how your own site does on a few of these checks. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.