How to Win a Featured Snippet: A Practical Guide to Google's Position Zero

Search a question on Google and you will often see a short answer box above every other result, with a website name underneath. That box, in short, is a featured snippet. SEO people also call it "position zero", because it sits above the first organic listing. In this guide I walk you through the snippet formats, how to structure your content, how to find realistic opportunities and how to opt out when you need to.

What is a featured snippet and how do you win one?

A featured snippet is a box at the top of Google's results that shows an extract from the page Google considers the best answer, with the description first and the link second. To win one, you ask the question clearly in a heading, answer it in 40 to 60 words right below, and already rank on page one.

Google's Search Central documentation describes the box as a regular result in reverse order. The descriptive text comes first. The page title and link then come after it. In addition, the same box can appear inside the "People also ask" section when a user expands a question.

I want to be honest about one point here. In the same document, Google says there is no way to mark a page as a featured snippet. Instead, its systems decide whether a page would make a good answer for a given search. So your real lever is presentation: you make the answer easy for Google to lift and display. The rest of this article is about exactly that formatting work.

Why do people call the featured snippet position zero?

The name comes from the location of the box. For example, in a classic results page, position one is the top blue link. The snippet sits above that link, so the industry started calling it position zero.

However, the name is a little misleading today. In January 2020, Google's Search Liaison Danny Sullivan announced that a page promoted to the featured snippet would no longer repeat as a regular listing on page one. According to Search Engine Journal, he also said the snippet counts as one of the ten first page listings. In other words, the snippet owner no longer gets the box plus a separate result right below it.

In practice, winning the snippet replaces your first organic position. It also does not add a bonus slot on top of it. That is why I suggest you treat position zero as a different presentation of position one, not as free extra visibility. This framing will help later when you interpret your click data.

Which featured snippet formats will you run into?

Google does not list the formats one by one in its documentation. In the field, though, I see four formats again and again. Each one responds to a different question pattern and expects a different content structure.

• Paragraph snippet: appears for "what is", "why" and "what does it mean" questions. It shows a short block of text.
• Numbered list snippet: appears for "how to" questions with a sequence of steps.
• Bulleted list snippet: appears for "types of", "examples of" or "best" queries where order does not matter.
• Table snippet: appears for prices, sizes, dates and comparisons. It condenses rows and columns.

On some queries, Google can also highlight a relevant part of a video. Still, most site owners do their real work in the first four formats. To see which one dominates your niche, open your target searches one by one in a private window and take notes. In practice, that small observation tells you which pattern to write in.

How should you write for a paragraph snippet?

The paragraph snippet is the most common format, and its logic is simple. The question goes in the heading and the answer goes in the first paragraph below it. Here is the pattern I use.

1. Write the question as an H2 or H3 that mirrors how people actually search.
2. Start the first sentence with a definition, such as "X is a ... that ...".
3. Keep the answer between 40 and 60 words. Note that this is a starting range from field experience, not a Google rule, so treat it as a guide.
4. Skip the warm up, the greeting and the "in this article we will" line.
5. Move details, exceptions and examples to the following paragraphs.

Why so short? Because Google shows a limited amount of text in the box. As a result, an answer that stops mid sentence does not satisfy the reader. A paragraph that stands on its own, and still makes sense when trimmed, is a much better candidate.

For example, imagine you answer "what is click through rate" with "This is a very important metric that many people wonder about." That first sentence carries no information at all. On the other hand, "Click through rate is the percentage of impressions that turn into clicks" gives Google a clean answer to quote. You can check the clarity of your paragraphs with my readability checker.

What structure does a list snippet expect?

For list snippets, Google moves the ordered structure of your page into the box. That is why writing steps as a real HTML list makes a big difference. Google can sometimes turn "first do this, then do that" sentences into a list too. A clean ol or ul element makes the job far easier, though.

These are the rules I have seen work in practice:

• Use a numbered list for a process and a bulleted list for an unordered set.
• Start each item with a short action, such as "Open the account" or "Fill in the field".
• Keep items parallel. Do not mix full sentences with single words.
• You can also write steps as subheadings. Google then sometimes compiles H3 headings into a list.
• Put a short lead sentence above the list that restates the question.

One more detail. If your list is longer than Google can show, a "More items" style link appears below the box. That actually creates a curiosity gap that can pull people to your site. So you do not need to cut a thorough process short. What matters is that each item is clear and easy to scan.

When does a table snippet show up?

Table snippets usually appear for comparisons, prices, sizes, limits and schedules. When the searcher wants to see several values side by side, Google may choose the table format.

The key rule is to build the table as real HTML, not as an image. After all, Google cannot read a screenshot of a table as text. I also recommend the following:

• Give the first row clear column headers, such as "Plan", "Monthly fee" and "Scope".
• Keep cell values short and comparable.
• Avoid merged cells and nested tables.
• Add a sentence right above the table that says what it compares.

That said, forcing every piece of content into a table is a mistake. Specifically, a table makes sense when the data really has more than one dimension. Putting a single definition in a table helps neither the reader nor Google. Later in this article you will find a table that compares snippet formats, which is a simple example of this logic.

How does Google choose a featured snippet?

Google's own wording is direct. Its systems determine whether a page would make a good featured snippet for a search, and if so, they elevate it. The Google Search Help page adds that Google picks snippets based on how well they answer the question and how helpful they are.

This sounds vague, but it gives you a few practical hints. First, the snippet almost always comes from a page that already ranks on page one. In my experience, it is very rare to see a page from outside the top ten promoted into the box. So snippet work does not replace ranking work. It is a layer on top of it.

Second, Google clearly wants an answer it can lift. A page that answers indirectly, through a long story, loses to a page that answers in its first sentence. Finally, overall page quality and trust matter too. In health, finance and legal topics in particular, Google does not want to promote content that contradicts expert consensus.

In short, the formula has three parts: a page that deserves to rank, a clear answer block and the right format. If one part is missing, the other two rarely carry the result alone.

Does structured data help you win a featured snippet?

No, it does not. Google states clearly that there is no special markup for featured snippets and no way to mark a page for the box. So I suggest you stay skeptical of any advice that says "add this schema code and you will get the snippet".

Still, this does not mean structured data is useless. Put simply, schema markup helps Google understand your page, and some types make you eligible for rich results. For example, correct markup for products, events or your organization can enrich how you appear in search. Still, those rich results are not the same thing as a featured snippet.

Let me clear up one more confusion. FAQPage markup once showed expandable questions and answers in the results. Google has since restricted that display heavily. So do not treat FAQ markup as a shortcut to the snippet either. If you need markup, you can build clean JSON-LD with my schema generator and then validate it in Google's Rich Results Test. For the snippet itself, the visible text on the page does the real work.

How do you find featured snippet opportunities?

The most efficient starting point is a query where you already rank on page one while another site owns the box. You have mostly solved the ranking part there. What remains is improving the answer format.

This is the order I follow:

1. Open the Performance report in Search Console and filter for queries with an average position between 1 and 10.
2. Pull out the queries that contain question patterns, such as what, how, why, how much and which.
3. Search each query in a private window and note whether a box appears and who owns it.
4. Record the format (paragraph, list or table) and the length of the text in the box.
5. Add the questions from the "People also ask" section to your list. They are great subheading ideas.

You should also know that Search Console does not offer a separate filter for featured snippets. So you track ownership either by manual checks or with an SEO tool that reports it. To pick the questions closest to a sale, you can use the intent split from my article on finding keywords that drive sales.

Which queries tend to trigger snippets?

From what I see in the field, informational queries with a single clear answer trigger the box most often. Definitions, processes, comparisons and measurements lead the list.

On the other hand, some queries rarely produce a box. Brand searches, local searches and searches with strong purchase intent usually fill up with map packs, shopping results or ads. For example, a search like "emergency plumber Brooklyn" is far more likely to show a map than an answer box.

Also, Google may avoid highlighting a single answer when the question calls for personal opinion or depends on the person. It is hard to answer "which phone should I buy" in one definitive paragraph. So ask yourself one question while building your opportunity list. Does this query really have a short, verifiable answer that holds for everyone? If yes, it is worth targeting. If not, your effort may pay off better in a different kind of visibility.

How can you take a snippet from the current owner?

If another site holds the box, start by studying its answer closely. How many words does it use? Which sentence does it open with? Which format does it follow? This tells you what Google currently considers good enough for that query.

Then make your own answer clearer, fresher and more complete. I am not talking about copying. Rewording a competitor's sentence gives you no real advantage. Instead, try to create one of these differences:

• If they answer indirectly, you answer directly in the first sentence.
• If their facts are outdated, you give current facts with a clear source.
• If they use a paragraph for a step based question, you offer a proper list.
• Where they stay general, you add a concrete example calculation or measurement.

After the change, patience matters. Google needs time to recrawl and reassess the page. Requesting indexing through the URL Inspection tool in Search Console can speed things up, but it guarantees nothing. In my experience, ownership sometimes changes within a few weeks and sometimes never changes at all. That is why I recommend logging every edit with its date and tracking the outcome.

Does a featured snippet increase your clicks?

The answer depends on the query, and I want to be upfront about that. In a 2018 blog post, Google stated that featured snippets do drive traffic to publishers. On the other hand, the box answers the question on the results page, so some users leave without clicking at all.

In general, I see a clear split. On queries with a one number or one sentence answer, such as a date or a unit conversion, users take the answer and leave. In contrast, on queries where the answer needs detail, application or context, the box can bring you more qualified visitors.

So look at the nature of the question before you chase the snippet. For a one line answer, the box delivers brand visibility more than clicks. I cover this in a wider frame in my article on zero click searches. Remember too that since the 2020 change, the snippet owner no longer gets a separate first position. Losing the box and losing position one are practically the same event. Read your click data with that in mind.

What should you do if you want to opt out of a snippet?

Sometimes you may not want to appear in the box. For instance, you might not want a summary of paid content shown on the results page, or the extract may lose its context. Google offers three controls, and its robots meta tag documentation explains them in detail.

• nosnippet: asks Google to show no text snippet for the page. It removes both the regular snippet and the featured snippet.
• data-nosnippet: an HTML attribute you add to span, div and section elements. It keeps the marked text out of snippets.
• max-snippet: sets a maximum character count for the snippet. A low value may leave Google without enough text for a useful featured snippet.

There is an important caveat. Google says a low max-snippet value does not guarantee that featured snippets will stop. Also, nosnippet removes your regular description too, which can lower your click through rate. So instead of applying these rules sitewide for one problem, limit them to the pages or sections that truly need them.

How does a nosnippet decision affect AI Overviews?

This question matters much more today than it did a few years ago. According to Google's robots meta tag documentation, the nosnippet rule applies to all forms of search results. That includes web search, Google Images, Discover, AI Overviews and AI Mode. The rule also prevents the content from serving as a direct input for AI Overviews and AI Mode.

The same document says the max-snippet rule also limits how much content may serve as a direct input for those AI features. In other words, a step you take to avoid the featured snippet can quietly shrink your visibility in AI summaries as well.

Therefore, make this decision for every search surface, not for one box. My recommendation is simple. If there is a specific section you truly do not want summarized, mark only that section with data-nosnippet. Let the rest of the page keep working as a source in classic results and in AI summaries. I cover writing for AI summaries separately in my guide to content for AI Overviews.

Which content does Google keep out of featured snippets?

Google has separate content policies for featured snippets. According to its Search Help page, extracts with dangerous content, deceptive practices, harassment, hateful content, manipulated media, sexually explicit material, violence or profanity should not appear in the box. On public interest topics such as civic, historical, medical and scientific issues, the answer also should not contradict well established expert consensus.

These policies have a side effect. According to Google, if a site has multiple featured snippets that break the policies, Google may remove all of that site's featured snippets. So a single problematic page can put the snippet visibility of your good pages at risk too.

Users can also report a wrong or inappropriate answer through the "Feedback" link below the box. That is why, especially in health, finance and legal topics, I recommend that you source your claims, avoid exaggerated promises and review your content regularly. A trustworthy answer protects both your place in the box and your brand reputation.

How do the snippet formats compare side by side?

The table below summarizes the four formats I meet most often, with the typical question pattern, the suggested structure and the main thing to watch. The length suggestions are starting ranges from field experience, not guarantees.

You can use this table as a checklist in your content plan. When you plan a new article, ask of every main question which format it triggers. Then build that section in the right structure from the start. That way you create the content in the right shape instead of fixing it afterwards.

How do you measure featured snippet results?

Measurement is the most neglected part of snippet work. As I mentioned, Search Console does not report featured snippets as a separate row. So you need your own tracking routine.

Here is the simple method I use. I list the target queries in a sheet. Every month, on the same day, I check them in a private window. I record who owns the box, the format and the text inside it. Next to that, I add impressions, clicks, click through rate and average position for each query from Search Console.

Then I compare the numbers with my edit dates. For example, I note the day I rewrote a page's answer paragraph. In the following weeks I check how that query's click through rate and position moved. This method is not perfect, since results vary by person, location and device. Still, it is good enough to show the direction over time.

Finally, you can preview how your title and description look on the results page with my Google SERP preview tool. To edit your meta tags, use the meta tag generator. Looking good in the regular result outside the box protects your total clicks.

What are the most common snippet mistakes I see?

The mistakes I find on client sites look remarkably alike. Here they are as a short list:

• Hiding the answer in the third paragraph and spending the first one on a general intro.
• Turning every heading into a question and then writing unrelated text below it.
• Giving the steps only inside an image or infographic, never as text.
• Cutting the whole page short for the snippet and destroying its depth.
• Believing that structured data alone will bring the box.
• Using nosnippet sitewide because of one issue and losing every description.

These mistakes share one root cause. People try to write for the algorithm instead of the user. Yet the answers Google promotes usually sound like an expert giving a client a short, clear reply. When I work with teams, I use one test. If I read this paragraph to a client on the phone, would it answer the question? If yes, you are on the right track.

A 30 day featured snippet action plan

For those who want to put this into practice, here is a short starting plan. I built it for a site that already ranks on page one. A brand new site needs a solid SEO foundation first.

1. Week 1: Export the question queries on page one from Search Console. Note the box owner and format for each.
2. Week 2: Pick the ten queries closest to a conversion. For each, locate the current answer block on your page.
3. Week 3: Rewrite answer paragraphs, lists and tables using the patterns in this article. Log the edit dates.
4. Week 4: Request indexing through URL Inspection. Then start tracking the results every week.

This plan does not guarantee the box. However, it gives your content a shape Google can quote. The same edits also help users find what they need on your page faster. If you have crawling or indexing problems, I suggest you first run the checks from my article on technical SEO after AI.

How does featured snippet work relate to AEO?

The featured snippet is the oldest and best known surface of answer engine optimization (AEO). AEO is the wider frame. It also covers question boxes, knowledge panels, voice assistant answers and AI summaries.

In this article I focused only on the box itself: its formats, its formatting, finding opportunities and opting out. For building question clusters, designing content architecture around questions and planning visibility across answer engines, read my guide to what AEO is and how to do it. Together, the two articles give you the tactics for a single box and the strategy for every answer surface.

One last note. Winning a snippet is an outcome, not the goal. The goal is that you give your customer the clearest answer to their question. That answer may reach them in the box, in an AI summary or in a classic result. If you want to map those questions for your own site and rework your answer blocks, we can do that together as part of my SEO consulting work.