Featured snippets: what they are and how to get them

What you’ll learn

This article explains what featured snippets are, the common formats Google uses, and a practical, testable workflow you can follow to increase the chance your content is used as a featured snippet. It includes formatting examples, verification steps using modern tools, and common mistakes to avoid.

What is a featured snippet?

A featured snippet is a short excerpt Google may show at the top of a search results page that directly answers a user query. Snippets are selected algorithmically from pages that already rank for the query. They can appear as short paragraphs, lists, tables or video clips, and they aim to give an immediate answer without requiring a click.

Keep in mind the distinction between crawling, indexing, and ranking: Google crawls pages to discover content, indexes the content it chooses to keep, and then decides ranking and SERP features. Mobile-first indexing is how Google crawls and indexes today; since July 2024 Googlebot Smartphone is used by default. That affects which HTML Google sees when choosing snippets.

Featured snippet types

Paragraph snippets

Paragraph snippets are single answers that directly respond to a question or definition-style query. They often show the first clear answer on a page. To make your content eligible, put a concise answer near the top of the page and use a clear heading that matches the query.

List snippets

Lists (bulleted or numbered) are common for step-by-step or ranked answers such as instructions, tips, or top-N lists. Use semantic HTML lists (<ul>, <ol>) and break steps into short, scannable lines so the search engine can extract the sequence cleanly.

Table snippets

Tables surface for comparison, conversion, and lookup queries (for example size charts or price comparisons). Use semantic <table> markup with clear headers (<th>) and well-structured rows so Google can interpret the columns and labels.

Video snippets

Google may show a video clip (often from YouTube) and jump to a timestamp relevant to the query. For how-to queries, add clear chaptering, timestamps in the video description, and an on-page transcript so crawlers can associate specific segments with queries.

A practical optimization workflow

Follow this sequence to identify snippet opportunities and produce testable content changes.

1) Find candidate queries

Use your Google Search Console Performance report to surface queries where you already rank in the top results or have impressions. Candidate queries are often question-form queries or short informational phrases where a direct answer fits the SERP.

2) Match intent and snippet type

Analyze the live SERP for the query: is Google showing a paragraph, list, table, video, or an AI-generated overview (Search Generative Experience)? Write your answer in the format the SERP prefers.

3) Format the answer correctly

Use a clear heading (h2/h3) that contains the question or close variant.

Follow the heading immediately with the concise answer in semantic HTML: paragraph, list (<ul>/<ol>), or table (<table>). Example paragraph answer: <p>Short direct answer that succinctly answers the query.</p>

For lists and steps, use real <ol>/<ul> elements—not visually styled divs—so crawlers can extract items.

4) Add supporting detail below the answer

After the concise answer, provide a short explanation, links to sources, and relevant examples. Google often prefers pages that combine a direct answer with useful context that encourages a click.

Technical checks and verification

After publishing changes, verify what Google actually sees and whether your content is eligible.

Check the HTML served to Google

Because Google uses the mobile version by default, fetch the page as a smartphone user-agent. Example command to retrieve the rendered HTML (follows redirects and sets a mobile UA):

curl -A "Mozilla/5.0 (Linux; Android 11; Mobile) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0 Mobile Safari/537.36" -L "https://example.com/page"

Note: use curl without -I if you need the HTML body. Use -I only when you want headers. The -A flag sets the User-Agent string.

Rendered DOM and JavaScript

Inspect the page with Chrome DevTools (Elements panel) on a mobile viewport to confirm the concise answer is present in the rendered DOM and not injected client-side in a way Google may not execute reliably.

Indexing and Search Console signals

For pages you own, use Google Search Console's URL Inspection to confirm the page is indexed and to view the rendered HTML Google saw. Use the Performance report to find queries that already show impressions and to see average position; those queries are the best snippet opportunities.

If a page is not indexed, it is unlikely to be used as a featured snippet until Google indexes it. The site: operator can be a quick public indicator that a page is known to Google, but it is not definitive.

Troubleshooting: common reasons you don’t get a snippet

Your page isn’t indexed or was recently de-indexed — verify in Search Console.

The SERP has a different dominant feature (for example, an AI overview or a video) that changes what Google chooses to display.

Your answer is buried under heavy navigation or requires JavaScript rendering that may not run consistently for crawlers.

A more authoritative page already provides a better-formatted or clearer answer for that exact query.

Practical tips and best practices

Match query phrasing — use natural question headings and synonyms users employ.

Be concise at the top: a short answer directly under the heading, followed by supporting detail.

Use semantic HTML for lists and tables so Google can extract structure reliably.

Avoid cloaking or serving different content to crawlers versus users. Mobile-first indexing makes parity between device content important.

Structured data: add relevant Schema.org markup where it makes sense (for example HowTo, FAQ, VideoObject). Structured data can help with other rich results but does not guarantee a featured snippet.

Example HTML patterns

Question heading with a direct answer (paragraph):

<h2>How do I change my browser homepage?</h2>
<p>Open your browser settings, locate the "On startup" or "Homepage" section, and set your preferred page or pages.</p>

Ordered list pattern for step-by-step answers:

<h2>How to reset a router</h2>
<ol>
<li>Locate the reset button on the device.</li>
<li>Hold it down for the manufacturer-recommended duration.</li>
<li>Wait for the router to restart and restore default settings.</li>
</ol>

When to prioritize featured snippet optimization

Prioritize queries where you already rank in or near the top positions, where the intent is informational, and where a concise answer will satisfy the user. Use Search Console and your analytics to confirm these queries drive meaningful impressions or relevant traffic.

Keep in mind that Google experiments with SERP features and AI overviews; a featured snippet for a query today may be replaced by a different feature tomorrow. Treat snippet optimization as part of a broader content strategy rather than a one-off tactic.

Further reading

If you want a deeper reference on rendering, indexing and other technical checks, read the technical guide:

Read the Technical SEO Guide

FAQ