Featured snippets: how Google picks them, how to structure answers and how to opt out

What a featured snippet is

A normal organic result shows the title, the URL and then a short description. A featured snippet reverses that order. The extract comes first, in a larger box, and the title and link of the source page sit underneath.

Google's help pages list three places where you can meet one:

• at the top of the search results;
• inside the "People also ask" box, as the answer to an expanded question;
• next to the Knowledge Graph information on the right side of the page.

SEO people often call the top spot position zero, because it sits above the first classic result. That is industry slang, not a Google term, and Google's own documentation does not use it.

The extract itself is just a snippet: text that Google takes from your page. That matters, because it means every rule that applies to ordinary snippets also applies here. If a page cannot have a snippet, it cannot have a featured snippet either.

What Google officially says

Put together, the official position is short: featured snippets are automatic, they come from the visible text of the page, they are chosen for how well they answer the query, and there is no switch on your side that turns them on.

How Google picks a featured snippet

There is no featured snippet markup, no structured data type and no Search Console setting. Adding FAQ or HowTo markup does not create a featured snippet. What Google evaluates is the text itself and how well it answers the query.

Several conditions follow from the documentation and from what practitioners see every day:

1. The page must be indexed and allowed to show a snippet. A page with noindex, or one blocked from showing snippets, is out of the running.
2. The query must call for a short answer. Google shows featured snippets when it “thinks people want answers that can be found in a short piece of a website.” Navigational and many commercial queries never get one.
3. The page usually already ranks well. In practice the source is almost always a page that ranks on the first page for that query. If you rank on page three, work on the page and its relevance before you polish an answer block.
4. The answer must be easy to lift. A self-contained passage, list or table that answers the query without the surrounding page is easier to use than an answer spread over five paragraphs.
5. The answer must be long enough. “Featured snippets will only appear if enough text can be shown to generate a useful featured snippet.”

Snippets are also query-dependent. Google says “Snippets are designed to emphasize and preview the page content that best relates to a user's specific search.” and “This means that Google Search might show different snippets for different searches.” One page can win a featured snippet for one question and show a completely different extract for another.

Policies can remove a featured snippet

Featured snippets have their own policy layer on top of the general Search content policies. Google's help page says “Sometimes, Google takes down a featured snippet if it doesn't follow our policies.” There is one feature-specific rule: “Featured snippets about public interest content shouldn't contradict well-established or expert consensus support.” For a site that keeps breaking the rules the consequence is broad: “Also, if a website has many snippets that break the rules, Google stops showing any featured snippets from that website.” The same help page notes that these policies apply only to what appears as a featured snippet, not to the normal web listing.

Snippet types: paragraph, list, table, video

Google does not publish an official list of formats, but four are seen consistently. Each one tends to come from a particular piece of HTML on the source page.

Paragraph snippets

The most common type. It answers a “what is” or “why” question in a few sentences. The source is usually a short paragraph placed directly after a heading that asks the question. A working target many SEO teams use is about 40–60 words: long enough to be a complete answer, short enough to fit the box without being cut mid-thought. That is a rule of thumb, not a Google number; Google itself says it “does not provide an exact minimum length required to appear as a featured snippet.”

List snippets

Numbered lists appear for steps and processes; bulleted lists for sets of items with no order. Google builds them either from an <ol> or <ul> on the page or from a sequence of subheadings such as “Step 1 … Step 2 …”. When the list is long, Google often shows the first items and a “More items” link to your page. That is not a problem: a list that is too long to fit is one reason people click through.

Table snippets

Table snippets appear for comparisons and data: plan prices, dosage by weight, train times, size charts. Google can only lift what it can read as a table, which means a real HTML <table>. It may show only some of your columns or rows, or rebuild a table from structured content elsewhere on the page, but the reliable source is a clean table with header cells.

Video snippets

For some “how to” queries Google shows a video, usually from YouTube, and sometimes jumps to the segment that answers the question. Getting there is a matter of video SEO rather than page markup; the lesson “Video SEO” covers it.

How to structure an answer so it can be extracted

You cannot ask for a featured snippet, but you can write so that the best answer on your page is obvious and self-contained. The pattern is simple: question, answer, detail.

1. Use the question as the heading. Phrase the H2 or H3 the way people search: “How do you descale a kettle?” is clearer than “Our descaling method”. The lesson “Headings H1–H6” covers heading structure in general.
2. Answer immediately below it. Put the direct answer in the first paragraph under the heading. No introduction, no history, no “great question”.
3. Make the answer self-contained. It should still make sense when shown alone in a box: name the subject instead of writing “it”, and avoid references such as “as we saw above”.
4. Then give the detail. The short answer wins the box; the depth below it is what makes the page rank and makes people click. A page with only one-line answers rarely ranks well enough to be chosen.
5. One question per section. Mixing three questions under one heading makes it harder for Google to match a passage to a query.
6. Keep the answer visible. Google's best practice for “Read more” deep links is: “Make sure content is immediately visible on the page to a human (and not hidden behind an expandable section or tabbed interface, for example).” The same logic applies here: put the key answer in normal, visible text, not only inside a tab or accordion.
7. Use text, not pictures of text. Google's AI features guide lists “Making sure that important content is available in textual form” among the SEO fundamentals. An infographic with the answer baked into the image gives Google nothing to quote.

Lists and tables in HTML, not images

For list and table snippets the markup matters, because Google has to recognise the structure. Use the elements HTML provides for exactly this job: <ol> for ordered steps, <ul> for unordered items, <table> with <th> for tabular data.

<h2>How do you descale a kettle?</h2>
<p>Fill the kettle halfway with equal parts
water and white vinegar, boil it, leave it
for an hour, then rinse twice…</p>
<ol>
  <li>Mix water and vinegar 1:1.</li>
  <li>Boil and leave for an hour.</li>
  <li>Empty and rinse twice.</li>
</ol>
<table>
  <tr><th>Method</th><th>Time</th></tr>
  <tr><td>Vinegar</td><td>1 hour</td></tr>
  <tr><td>Citric acid</td><td>30 min</td></tr>
</table>

<h2>Our method</h2>
<!-- steps baked into an image -->
<img src="/img/steps.png"
     alt="steps">

<!-- a "table" made of divs -->
<div class="grid">
  <div>Method</div><div>Time</div>
  <div>Vinegar</div><div>1 hour</div>
</div>

<!-- answer only inside a closed tab -->
<div class="tab" hidden>…</div>

A few practical rules for lists and tables:

• One item, one idea. Short list items that start with a verb (“Mix…”, “Boil…”) work well for steps.
• Header cells in tables. Mark the first row with <th> so the columns have names. Keep units in the header (“Time, min”) rather than repeating them in every cell.
• Keep tables simple. Merged cells, nested tables and decorative rows make a table harder to read for people and for Google.
• Responsive is fine. You can let a wide table scroll horizontally on mobile with CSS; that does not change its markup.
• Images can support, not replace. A chart or photo next to the table is useful. The data itself should also exist as text.

People also ask

“People also ask” (PAA) is the box of related questions that expand when clicked. Google's featured snippet documentation says featured snippets “can also appear within a related questions group (also known as "People Also Ask").” Each expanded answer is, in effect, a small featured snippet: an extract from one page with its title and link.

For your work, PAA is useful in three ways:

• Research. The questions show how people phrase follow-up needs around your main query. Collect them for your important topics and check which ones your page does not answer yet. The lesson “Search intent and SERP analysis” covers reading the results page more broadly.
• Heading wording. If a PAA question fits your page, use it, or a close variant, as an H2 or H3 and answer it in the answer-first pattern.
• Extra visibility. The same section can appear as an answer in PAA for one query and as the featured snippet for another. Every question you answer well is another chance.

Do not turn a page into a list of every PAA question you can find. Answer the ones that belong to the page's topic and intent; unrelated questions dilute the page.

How to opt out of featured snippets

Some sites prefer not to appear as a featured snippet, for example when the box answers the question so completely that nobody clicks, or when an extract out of context could mislead. Google says “There are two ways that you can opt out of featured snippets:” block all snippets, or block only featured snippets.

Block all snippets: nosnippet

“To block all snippets (including featured snippets and regular snippets) from appearing for a given page, add the nosnippet rule to that page.” This is the reliable way out. The cost is real: your regular result also loses its text description, which usually makes it less attractive to click. Weigh that before using it on pages that earn traffic.

<meta name="robots" content="nosnippet">

Block featured snippets only: max-snippet

If you want to keep a normal snippet, Google suggests experimenting with a lower max-snippet value: “In general, the shorter your max-snippet rule setting, the less likely the page will appear as a featured snippet.” There is no magic number, because “Google does not provide an exact minimum length required to appear as a featured snippet.” Start with a value such as 50 characters, watch the results and keep lowering it if the page still appears. And keep the limit of this method in mind: “Using a low max-snippet setting doesn't guarantee that Google will stop showing featured snippets for your page. If you need a guaranteed solution, use the nosnippet rule.”

<meta name="robots" content="max-snippet:50">

In practice, max-snippet:0 behaves like nosnippet, and max-snippet:-1 means no limit.

Hide specific passages: data-nosnippet

“Text marked by the data-nosnippet HTML attribute won't appear in featured snippets or regular snippets either.” Use it on span, div or section elements that hold text you do not want quoted, such as a disclaimer or a paywalled teaser. If both are present, the page-level rule wins: “If both nosnippet and data-nosnippet rules appear in a page, nosnippet takes priority, and snippets won't be shown for the page.”

<p>Our full test results are below.
  <span data-nosnippet>Prices checked on 1 October 2026.</span>
</p>

All three controls only work if Google can crawl the page and see them. The full list of robots rules is in the lesson “Meta robots and X-Robots-Tag”. After a change, the effect appears only once Google has recrawled the page.

What happens to your regular listing

Google's current featured snippet page documents what happens on the click, not what happens to the rest of the results page. It says: “Clicking a featured snippet takes the user directly to the section of the page that appeared in the featured snippet.” and “Scrolling to the position that appeared in the snippet happens automatically, without any additional annotation by the site.” If the browser does not support this, or Google cannot locate the passage, “clicking a featured snippet will take a user to the top of the source web page.”

The page does not say whether your page also appears again as a regular result on the same page, and that behaviour has changed over the years. Treat it as something to observe, not to assume: search your query, note whether the snippet page also appears lower down, and check it again after updates. Do not plan around a rule Google does not currently document.

The automatic scroll has one practical consequence: avoid scripts that force the scroll position back to the top on load or strip the URL fragment, because they break this jump. Google's snippet documentation lists the same advice for “Read more” deep links.

Featured snippets and AI Overviews

Featured snippets and AI Overviews are different features, but they rest on the same base. Google's AI features guide states: “To be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements.” and “There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary.”

That has two direct consequences for this lesson:

• The controls overlap. “To limit the information shown from your pages in Search, use nosnippet, data-nosnippet, max-snippet, or noindex controls.” A nosnippet you add to keep out of featured snippets also limits how your page can be used in AI features. Decide with both in mind.
• Good structure helps both. Clear headings, self-contained answers and real lists and tables are useful for every feature that quotes or summarises your text, and for readers.

On many queries an AI Overview now sits above or alongside other features, so a featured snippet is not always the top element any more. The lesson “Page-level optimisation for AI Overviews” covers that feature in depth, and “Classic results, AI Overviews, AI Mode, Discover” explains how the different result types fit together.

How to track featured snippets

No single report tells you “you own this featured snippet”. You combine three sources.

1. Search Console Performance report. At the time of writing the Search appearance dimension has no featured snippet filter; check what your own property lists there. Use the Queries and Pages tabs instead: a query where your average position is close to 1 while your page is the snippet source, and where CTR changes sharply after a content edit, is worth a closer look. Clicks from AI features are counted in the same report: “sites appearing in AI features (such as AI Overviews and AI Mode) are included in the overall search traffic in Search Console.” The lesson “Performance report” explains the metrics.
2. Rank trackers. Most commercial rank trackers record SERP features per keyword and show whether your URL is the featured snippet source, and when you gained or lost it. Track the questions you have structured answers for.
3. Manual checks. Search the query in a clean browser session for the country and language you care about. Featured snippets vary by location, device and wording, so check the variants that matter.

Expect movement. Featured snippets change hands when a competitor improves their page, when you edit yours, or when Google changes the layout for that query. A loss is a reason to compare your answer with the new source, not a reason to panic.

Common mistakes

• ✕The answer is buriedThree paragraphs of introduction before the actual answer to the question in the heading.
• ✕Headings that do not match any question“Our approach” instead of “How do you descale a kettle?”.
• ✕Tables and steps as imagesA screenshot of a price table or an infographic of steps gives Google nothing to extract.
• ✕Div grids instead of tablesRows and columns built from <div> elements have no table structure.
• ✕The answer only in a closed tab or accordionKeep the key answer in visible text.
• ✕Adding schema to “get” a snippetThere is no featured snippet markup; FAQ markup does not create one.
• ✕Opting out with robots.txtIt blocks crawling, not snippets, and hides your nosnippet from Google.
• ✕Using nosnippet without weighing the costIt also removes the regular snippet and limits use in AI features.
• ✕One-line pages built only for the boxWithout depth the page does not rank well enough to be chosen.
• ✕Answers that contradict expert consensusOn public interest topics this breaks the featured snippet policy.

FAQ

Sources

• Google Search Central — Featured snippets and your website
• Google Search Help — How Google’s featured snippets work
• Google Search Central — Control your snippets in search results
• Google Search Central — AI features and your website

Quotes checked against the official pages on 30 October 2026.