Featured Snippets and People Also Ask in 2026
Most advice about the featured snippet tells you to add markup and win position zero. You cannot do that. Google's own documentation answers the question. The answer is two words: "You can't."
So let us drop that goal and concentrate on what you control. That means whether your page is eligible and easy to extract from. You also control whether you participate in snippets at all. That second lever is real, documented, and more expensive than most teams expect.
What is a featured snippet, and how does Google choose one?
A featured snippet is a block of text that Google extracts from a page and elevates to the top of a results page. You do not submit it anywhere, and Google Search Central states that Google systems determine whether a page would make a good featured snippet for a user's search request, and if so, elevates it. Selection sits with them.
Read that sentence again. It names two things you can act on, and the first is "a page". That means the unit of selection is a page rather than a tag or a block of code. The second is "for a user's search request". The fit between your answer and the question does a great deal of the work.
The practical understanding is plain enough. Publish a page that answers one specific question properly. Make the answer readable on its own, and match the language a real searcher types into the box. That is not glamorous, and it does not fit neatly into a markup checklist, but it remains the work.
In my view the tag-first framing has done real damage. Teams burn entire quarters on code and skip the part that matters, which is the sentence a reader wants. If you need a starting point for matching questions to page types, our breakdown of search intent and the micro intents behind each query is the place to begin. Intent comes first and format follows from it.
Can you mark up a page to win position zero?
No, and the term itself is misleading. "Position zero" is a nickname the industry invented rather than a placement you can claim. Asked whether you can mark a page to be a featured snippet, Google's featured snippets documentation answers "You can't." There is no tag, no property and no schema type that hands you the placement. Any vendor claiming otherwise is selling something.
This trips up experienced practitioners, because we are trained to think of search results as things you request. You request indexing, you request a canonical, and you can even request a shorter preview length. Selection is different, because the answer box is not a request at all but a decision made about your page.
Here is what nobody tells you: that distinction should change how you plan the work. You cannot put "win the answer box for term X" into a sprint and expect it to close. You can put "publish a clean 45-word answer to term X underneath a matching heading" into that same sprint, and this version closes every time.
So set goals you can finish, then ship the answer, track the query, and let Google handle the part that belongs to Google. If your team argues about how much text a page needs before it earns that chance, our guide to how long a page really needs to be settles most of the argument.
If you cannot win it, what can you actually control?
You control three things, and the list is shorter than most guides suggest. First, eligibility: the page must be crawled, indexed and permitted to display a snippet. Second, extractability: the answer must be short, clear and able to stand alone. Third, participation: you can disable snippets for a page, or cap how much text Google may use.
Everything else is influence rather than control, which is worth stating plainly, because so much snippet advice blurs those two categories together.
Here is the short version of the levers that belong to you:
- Crawl and index status. A page that Google cannot fetch or index cannot be extracted from in the first place.
- Answer shape. A question-style heading with a direct answer positioned underneath it, before any background material.
- Self-contained wording. The answer has to make complete sense even when the paragraph above it disappears.
- The nosnippet directive. It blocks every snippet for that page, including the top answer block and the regular result snippet.
- The max-snippet directive. It caps the number of characters Google may apply as a textual snippet for that result.
- The data-nosnippet attribute. It designates specific textual parts of the page as unavailable for snippet extraction.
Notice what is missing from that list: there is no markup for winning, no schema type and no file you upload. The directives available to you are all about limits rather than requests, and once that understanding lands, snippet work becomes simpler and much less stressful. Pair it with a solid on-page SEO checklist for 2026 and you have covered the ground that is yours.
How does the featured snippet connect to People Also Ask?
The answer block and People Also Ask are more closely related than most guides admit. Google's documentation says a featured snippet can also appear within a related questions group. People Also Ask is the name most practitioners use for that group. So the same extracted answer can appear at the top of the page or inside a stack of questions further down. One mechanism, two placements.
That single sentence should reshape your planning. Treat the answer box and People Also Ask as two separate projects and you will build two sets of pages, and you will split your own topic in half. Treat them as one surface instead, and write one strong answer for each real question, and let placement fall wherever it falls.
It also explains a pattern many practitioners notice. A page appears inside a related questions group for a phrasing nobody ever targeted. That is not a bug, and it is not something the documentation explains. Placement inside that group is Google's call, not a target you set.
I would not chase single People Also Ask entries. The set shifts often and you cannot pin it down. List the ten real questions your buyers ask instead, and answer each one cleanly on the page that already owns that subject. Our guide to building content clusters around pillar pages shows how to lay those questions out without splitting the topic across thin pages.
How do you write an answer block Google can lift?
Put a question-shaped heading on the page, then underneath it answer the question in 40 to 60 words. Keep that answer self-contained, so it reads well with nothing above it. Use the question's own nouns in the opening sentence. Then develop the idea below in plain prose. That is the whole method, and it works on almost any page type.
The most common failure is the throat-clearing paragraph. A writer places a question heading and then opens with "Before we get into this, it helps to know the history." That material holds no answer for anything to lift, and no reader wants it, so cut it and begin with the answer instead.
The second failure is the dangling pronoun. An answer beginning with "It depends on this setting" cannot travel on its own. Name the thing and write "snippet length depends on the max-snippet value" instead, because that version survives separation from its surroundings.
Some practical habits hold up well across page types:
- One question for each heading, never two, because a doubled heading gives the extraction nothing clean to take.
- Numbers written as digits whenever the answer is itself a number, a measurement or a duration.
- Steps presented as a short list whenever the answer is a process rather than a definition.
- No links inside the answer block itself, since those belong in the paragraph following it.
- Repeat the key noun once for clarity rather than five times for an imaginary keyword quota.
Do this on every page and you build a library of extractable answers, and that library also makes a page useful to a reader in a hurry, which is the real payoff. If you want the wider argument about writing for answer surfaces, see our piece on how answer engines choose which content to feature.
How do you stop snippets from showing on a page?
Apply the nosnippet directive, which is the only documented page-wide switch. Google's documentation is direct: to block all snippets, including featured snippets and regular snippets, from appearing for a given page, add the nosnippet rule to that page. You can set it in a robots meta tag in the head section, or as an X-Robots-Tag in the HTTP response header. Both routes work.
The exact wording matters, because the directive means do not show a text snippet or video preview in the search results for this page. So it is not a scalpel, because you are not disabling one placement but removing snippet text everywhere for that page.
When is that the correct call? A few honest categories exist, and one is paid content where the preview gives away the product. Another is legal or medical pages where a stripped-down sentence could mislead a reader. A third is pages under a license that limits reuse of the text.
When is it the wrong call? Almost every other time. A result with no snippet is a bare link, and I would not do that to a page I want people to click. Read the exact directives on Google Search Central's robots meta tag page before shipping anything sitewide, and test on a single URL first, because the X-Robots-Tag route is easy to apply too broadly at the server level.
Can you avoid the featured snippet and still keep normal snippets?
Sort of, and this is the most misread passage in Google's guidance. Google suggests that if you want to retain snippets in regularly-formatted search results, but you do not want to appear in featured snippets, you can experiment with setting the max-snippet rule to lower lengths. Note the word "experiment", because Google also states that a low setting does not guarantee it will stop showing the block for your page.
So this is a dial rather than a switch, and the max-snippet directive tells Google to use a maximum of a set number of characters as a textual snippet for that result. The accepted values include zero, a positive character count, and negative one. It belongs in the same two places as nosnippet, meaning a robots meta tag or an X-Robots-Tag header.
My read is simple: if somebody tells you a clean opt-out exists for the featured snippet alone, they have not read the documentation. There is a lever Google suggests you experiment with, and Google attaches a documented warning to it. Describe it that way in every meeting.
If you do run this experiment, change one page and keep the value stable, and give the change real time before judging it. Log it as well, because snippet-level tests are easy to forget and hard to unpick six months later.
What does blocking snippets cost you in AI Overviews and AI Mode?
More than the single search result you were thinking about. The nosnippet directive applies to all forms of search results at Google. That includes web search, Google Images, Google Discover, AI Overviews and AI Mode, and it will also prevent the content from being used as a direct input for AI Overviews and AI Mode. The trade is your whole presence in Google's answer layer.
This is the sharpest practical point in the article. A team decides the answer box is stealing clicks and adds nosnippet across a template. Six months later they wonder why the brand never appears as an input to AI answers. They opted out and then forgot about it.
The max-snippet directive carries a comparable reach, and it applies across Google web search, Google Images, Discover, Assistant, AI Overviews and AI Mode. There is no search-only version of either directive.
So before anyone touches these settings, ask a blunt question. Are we willing to leave the answer layer for this page? If the answer is no, the snippet debate is over. Our overview of how Google AI Mode changes the results page is worth reading first. Then what an llms.txt file does and does not control covers the neighboring question of AI access.
How do you hide one part of a page from snippets?
Use the data-nosnippet attribute, which is the precise instrument in this toolkit. Google's documentation says you can designate textual parts of an HTML page not to be used as a snippet. Marked text will not appear in the featured snippet or in regular snippets either. You place the attribute on a span, a div or a section element. The rest of the page stays eligible.
This is the surgical option, and it is the one I reach for first, because it resolves the real complaint behind most snippet arguments. That complaint is never "we appear" but "the wrong sentence appears."
Good candidates for marking a block unavailable include the following:
- Price lines that go stale between content updates and then mislead people who never open the page.
- Boilerplate legal text that reads badly whenever it is separated from its surrounding context.
- A short disclaimer that could otherwise be extracted and presented as though it were the answer.
- Author biographies, repeated calls to action and other template furniture that carries no answer value.
One warning applies here, because if you mark too much you starve the page of anything worth extracting. The instinct to wrap entire templates ends with a page that earns no snippet at all. Mark the specific block instead, then review the page again a few weeks later.
Fold this into your normal page review, because a quarterly pass over your top twenty pages catches most of these problems. Check what Google could reasonably extract from each one, before any reader sees a bad line.
Does the featured snippet work the same in the US, Europe and Korea?
The directives are the same everywhere. The content is not. Selection happens per page and per search request, and in practice language decides who is even in the running. A clean US English answer block rarely fits a Korean-language query, and it rarely fits a German or French one either. The same mechanism operates over a different pool of pages.
That carries a real cost for teams working across the United States, Europe and South Korea. Many of us publish one English page and hope it travels. It does not travel into a query typed in Korean. If Korean demand matters to your business, the answer block has to exist in Korean, on a page built for that market.
Europe adds a further wrinkle, because it is one market containing many languages, with phrasing that shifts between them. The German phrasing of a question is often longer and more exact than the US English version. So mirror the local phrasing rather than translate your US heading word for word.
My honest opinion is that most teams should pick two markets and serve them properly rather than five badly. Depth beats spread here, because extraction rewards the page that answers one question best in one language, and selection is decided at that level.
How do you check the parts you control without a rank tracker?
Check the page rather than the box. Confirm that the page is indexed and permitted to display a snippet. Confirm the answer sits beneath a question heading. Confirm that no directive is capping your snippet by accident. Then watch the query in Google Search Console for impressions and average position. Those two are what you watch once the parts inside your control are in place.
Two of our free tools help with the page-level checks. The Meta Tag Analyzer takes a single domain and reports the meta tags already present on that page. That is how you catch a robots meta tag nobody remembers adding. It reads the page's markup, so an X-Robots-Tag sent in the HTTP header still has to be checked by hand. The Website SEO Score Checker takes one URL and scores that page. The limit deserves stating clearly: it scores a page and is not a crawler, so it will not audit an entire site for you.
Building a new page? The meta tag generator for titles, descriptions and robots directives writes tags you paste into the head section, with index and follow choices included. It does not write nosnippet or max-snippet, so you add those by hand. If the page will also be shared socially, the Open Graph tag generator for social previews handles title, site name, url, description, type, image and video fields.
We do not offer a rank tracker or a SERP feature tracker, so I will not pretend you can automate the final mile of this. Manual checks plus Search Console is the honest setup, and it is enough to tell you whether the parts you control are in place.
What should you actually do about all this next week?
Pick your five best pages and add a question-shaped heading to each one. Place a 40 to 60 word self-contained answer below it. Then audit those same pages for robots directives you never intended to set. That is roughly two hours of work, it sits inside your control, and it is worth more than a month spent chasing the block itself.
After that, work steadily down a priority list:
- Write one clean answer for each real question, on the page that owns that subject.
- Mark stale or misleading blocks as unavailable using the data-nosnippet attribute rather than blocking the entire page.
- Leave nosnippet alone unless you accept leaving AI Overviews and AI Mode behind at the same time.
- Treat max-snippet as an experiment carrying a documented warning rather than a reliable switch.
- Build the local-language version before you expect any results inside a local-language market.
Here is my prediction, offered as opinion and nothing more. The teams that do well over the next few years will be the ones that stopped trying to control selection, and started making their answers easy to extract instead. That skill pays across every surface Google operates, not the block at the top alone.
To keep going, our guide to winning attention when searchers do not click covers the business side of this. Next, the difference between AEO, GEO and classic SEO sorts out the vocabulary. Then our guide to earning mentions inside generated answers takes the idea further. For the trust side, read how to build the experience and trust signals Google looks for and how topical depth compounds over time. Which of your pages has an answer buried three paragraphs too deep?
Frequently asked questions
Can you make Google pick your page for the answer box?
No, and the documentation is blunt about it. Google answers the question of whether you can mark a page as a featured snippet with "You can't." Google systems determine whether a page suits a search request and elevate it. You control eligibility and clarity, never the selection itself.
Does schema markup help you win the answer box?
Google's documentation does not say that any markup wins the placement. I will not claim otherwise here. Structured data serves other purposes on a page. For the answer block, write a clear self-contained answer underneath a question heading. Treat markup as a separate piece of work.
What does the nosnippet rule actually do?
It blocks every snippet for that page, including the top answer block and the regular result snippet. The directive means do not show a text snippet or video preview in the search results for this page. So it works page-wide rather than targeting one placement.
Will blocking snippets hurt me in AI Overviews and AI Mode?
Yes. The nosnippet directive applies to web search, Google Images, Discover, AI Overviews and AI Mode. It also prevents your content being used as a direct input for AI Overviews and AI Mode. That reach is the real price of opting out.
What is the difference between a featured snippet and People Also Ask?
Placement, mostly. Google's documentation notes that the block can also appear within a related questions group. That group is the People Also Ask stack most practitioners recognize. So the same extracted answer can sit at the top of the results or inside that question group.
Can I opt out of the top block but keep my normal snippet?
Google suggests you can experiment with a lower max-snippet length to retain regular snippets while avoiding the elevated block. That is a documented suggestion rather than a promise. Treat it as an experiment on one page, keep the value stable, and give it real time.
Does a low max-snippet value guarantee the top block goes away?
No, and Google states this plainly. Using a low max-snippet setting does not guarantee that Google will stop showing the block for your page. Plan around that uncertainty. The only documented page-wide lever is nosnippet, and it carries every cost described above.
Do short answer blocks hurt long-form rankings?
In my view they do the opposite. A tight opening answer serves the reader in a hurry, while all the depth still sits below it. Write the 45-word answer first. Then build the full argument underneath it on the same page.
Where do you put the nosnippet rule?
Two places work equally well. Add it as a robots meta tag inside the head section of the page. Or send it as an X-Robots-Tag in the HTTP response header. The header route applies fast at the server level. Test a single URL before any wider rollout.
Can I hide one part of a page instead of the whole thing?
Yes, and this is usually the better move. The data-nosnippet HTML attribute lets you designate textual parts of a page as unavailable. You place it on a span, div or section element. Marked text will not appear in snippets of either kind.