How to Win Featured Snippets and People Also Ask

Featured snippets and People Also Ask answers nearly always go to pages that already rank on page one. On top of that ranking, you need a short answer that makes sense on its own, sitting directly under a heading that repeats the question. Google lifts whichever passage answers the question most clearly, so most of the work is structure and precision, and matching the format Google already shows for that search, whether that is a paragraph, a list or a table.

Below we cover how both features work, which queries are worth chasing, and how to write and format answers that Google can extract cleanly. The same techniques also help you turn up in AI-generated answers.

What featured snippets and People Also Ask are

A featured snippet is the highlighted answer box that sometimes appears at or near the top of Google’s results. It shows a passage of text, a list or a table from one web page, with a link to that page. Google picks the passage automatically, and there is no way to apply for one or mark up your page to request it.

People Also Ask (PAA) is the expandable box of related questions. Click a question and it opens to show a short answer from a web page, again with a link. Opening one question often loads more below it, so PAA doubles as a map of what searchers want to know next.

The two are closely related. Both are built from passages that answer a question directly, and one page can appear in both. The difference is in numbers. A query has at most one featured snippet, while a PAA box can pull answers from many different sites.

The common snippet formats

Answer in whatever format Google already prefers for the query. If the current snippet is a table, a beautifully written paragraph is unlikely to replace it.

Why snippets still matter now AI Overviews are here

With AI Overviews showing for so many informational searches, it is fair to ask whether snippets are still worth the effort. We think they are, though for a slightly different reason than before.

Whatever wins a snippet also makes content easy for other systems to quote. That means a clear question with a direct answer, tidy structure and accurate detail. AI Overviews, ChatGPT and similar tools all prefer passages they can lift and attribute with confidence, so a page built to win a snippet is usually easy to cite as well. AI search optimisation builds on that overlap.

There are trade-offs, though.

• Some snippets reduce clicks. If the snippet fully answers a simple question, such as a date or a conversion, the searcher may not need to visit. These “zero-click” answers still build brand familiarity, but they rarely drive enquiries.
• Some snippets increase clicks. Where the answer is a teaser for a bigger task, such as a process with several steps or a comparison that needs context, the snippet acts as a shop window.
• Snippets change. Google tests and rotates them, so no snippet is yours for good. Treat one as a side effect of good content rather than something you own.

So put questions first where the answer leads naturally to a next step on your site, such as a quote form or a service page.

How Google chooses which page to feature

Google does not publish a formula, but its documentation and years of watching results point to a few patterns that hold up.

• You generally need to rank on page one already. Snippets nearly always come from pages that rank organically for the query. Snippet work is therefore mostly about improving pages that already perform. It will not shortcut a new page to the top.
• The answer must be easy to isolate. A passage that stands on its own under a relevant heading is far easier to extract than an answer buried halfway through a long paragraph.
• Wording matters. Pages whose headings and opening sentences closely echo the question tend to be favoured.
• Trust counts. Google is more cautious about featuring answers on health, finance and legal topics, and leans towards sources that show expertise. Named authors and evidence of real experience help here.

You do not need structured data for featured snippets. Schema markup helps search engines understand a page and powers other rich results, but no markup exists for snippets specifically. Google also restricted FAQ rich results to a small set of authoritative government and health sites and has retired HowTo rich results, so adding that markup will not produce the expandable FAQ or step-by-step displays most businesses used to see.

How to find snippet and PAA opportunities

The best targets are queries where you already rank reasonably well and Google already shows a snippet or PAA box. Any business can work through the steps below with free tools.

1. Export your queries from Google Search Console. In the Performance report, filter to queries where your average position is roughly in the top ten. Those are the ones you have a real chance with.
2. Filter for question-style queries. Use the query filter with words such as how, what, why, when, can, should, cost, vs and best. Questions are far more likely to trigger snippets.
3. Check each query in a private browser window. Note whether a snippet appears, what format it uses, which site holds it, and which PAA questions show up.
4. Record the PAA questions. Expand two or three of them to reveal more. Group related ones together, as they often belong on the same page as supporting sections.
5. Score each opportunity. Favour queries where you rank on page one, the current answer is weak or out of date, and the topic connects to something you sell.
6. Map each query to one page. Do not create a thin new page for every question. Most belong as sections on an existing, stronger page.

Your sales and support conversations will turn up questions Search Console does not show yet. What customers ask by phone or email is often exactly what they type into Google.

How to write an answer Google can lift

Most of the gains come from this part. You want a passage that still reads well when it is lifted out of your page and shown on its own.

Use the question as a heading

Put the question, or a close variant, in an H2 or H3. “How long does a boiler service take?” is far easier to extract than “Our servicing process”, because the heading tells Google exactly which question the next passage answers.

Answer immediately, in the first sentence

Open the paragraph under the heading with the answer itself and leave the context for later. Compare these two openings.

• Weak: “There are lots of things to consider when it comes to boilers, and every home is different, so it is hard to say.”
• Strong: “A standard annual boiler service usually takes between 30 minutes and an hour, depending on the boiler type and whether any parts need cleaning or replacing.”

The second version can be quoted on its own. The timings are only an illustration, so use figures that are true for your own service.

Keep the core answer short, then expand

Paragraph snippets are usually brief, so aim for a core answer of two or three sentences and add depth afterwards. Answering first and explaining second works for the snippet, for people skimming and for readers who want the detail.

Define terms in a recognisable pattern

For “what is” queries, a definition that follows the shape “X is a [category] that [does what / for whom]” is easy to extract. For example: “A mortgage in principle is a statement from a lender showing how much it would be willing to lend you, based on an initial check of your finances.”

Be specific and accurate

Vague answers lose to precise ones. Include the actual numbers, conditions and exceptions, and keep them up to date. If the answer varies, say what it varies with rather than hiding behind “it depends”.

Write in plain language

Short sentences, everyday words and the active voice make a passage easier to follow out of context, which helps readers and makes it more likely to be picked up by Google or an AI tool. Good semantic content writing follows the same principles.

Formatting lists, steps and tables for extraction

When the existing snippet is a list or table, match it with clean HTML.

Lists and steps

• Use a real ordered list for sequential steps and an unordered list for items with no order. Avoid faking lists with line breaks or images.
• Start each step with a verb and keep each item to a single clear action.
• Put the list directly under a heading that matches the query, such as “How to bleed a radiator”.
• Having more steps than Google shows is fine. Google will often cut the list short and add a “more items” link, which can encourage the click.
• For longer guides, using each step as its own H3 can work well. Google sometimes builds a list snippet from a page’s sequence of headings.

Tables

• Use a proper HTML table with a header row, not an image of a table or a layout built from boxes.
• Keep it to a handful of columns with short cell values.
• Put the most useful comparison in the first columns, as Google may show only part of the table.
• Label units in the header (for example “Price per month” rather than repeating the currency in every cell).

Tables work especially well for price ranges, product comparisons, specifications and opening times, and small business sites rarely use them as much as they could.

Targeting People Also Ask

PAA boxes are often easier to get into than the main snippet, because each one holds several answers from different sources. They also show you the wider set of questions behind a search, which is useful when planning content.

Build PAA questions into your page structure

Take the PAA questions you collected and add the relevant ones as H2 or H3 sections on the most suitable page. Answer each in the first two sentences, then expand. The page also becomes more complete on its main topic, which can help its wider rankings.

Use a short FAQ section where it helps

A short FAQ at the end of a page suits smaller questions that do not need a full section. Write the answers for people rather than for markup, in two to four specific, accurate sentences. FAQ markup will not produce expandable FAQ results for most businesses, so any benefit comes from the content itself.

Watch how the questions branch

Each PAA question you expand reveals more related questions. Following those branches is a quick way to find sub-topics your competitors have missed, and it shows which of your pages should link to each other.

Improving an existing page step by step

Most snippet wins come from editing pages you already have. This is the workflow we use for a single page.

1. Pick one page and its main question. Choose a page ranking on page one for a question that shows a snippet.
2. Study the current snippet. Note its format, its length and exactly what it says. Is it complete and up to date? Could it be written more clearly? The approach in our guide to running a competitor analysis works well here.
3. Add or rewrite the heading. Make it reflect the question in natural wording.
4. Write a better answer directly beneath it. Match the format, be more precise than the current holder and put the answer in the first sentence.
5. Tidy the surrounding page. Cut the waffle before the answer, fix broken formatting, and check the page loads quickly and reads well on a phone.
6. Add supporting PAA sections. Answer two or three related questions further down.
7. Strengthen internal links. Link to the page from related articles and service pages with descriptive anchor text.
8. Request indexing and wait. Use the URL Inspection tool in Search Console, then check the results over the following weeks rather than days.

Common mistakes that cost snippets

• Burying the answer. Long introductions, company history or sales copy before the answer make extraction harder.
• Writing for a keyword rather than a question. Headings stuffed with phrases read badly and do not match how people ask.
• Mismatching the format. Answering a “steps” query with a paragraph, or a comparison query with prose.
• Answers locked in images, accordions that do not load content, or PDFs. If the text is not readily available in the page’s HTML, it is harder for Google to use. Content inside a standard collapsible section is usually fine, provided it is present in the page source.
• Outdated details. Old prices, rules or product names undermine trust and make it easier for a competitor to replace you.
• Creating dozens of thin question pages. One strong, well-organised page usually beats many weak ones.
• Accidentally blocking snippets. A nosnippet or very low max-snippet robots setting, sometimes added by a plugin or a developer, will stop Google showing your text. Check your page source if you never appear.

Measuring results

Search Console does not label featured snippet appearances separately, so measurement needs a little manual work.

• Keep a tracking sheet. List each target query, the page, the snippet format and who currently holds it. Recheck monthly in a private window.
• Watch impressions, clicks and click-through rate for each target query in Search Console. A change in click-through rate after you edit a page can hint at a snippet gain or loss, though other factors, such as AI Overviews appearing, can also move it.
• Use a rank tracker that records SERP features if you track many queries. Most paid tools show which features appear and which of them you hold.
• Judge success by business outcomes. Holding the box is nice, but the real test is whether the pages you improved bring in more enquiries, sign-ups or sales.

Expect snippets to move between sites and sometimes vanish altogether. The clearer answers and better structure you put in place keep paying off either way.

A first month of snippet work

Most of this is careful editing. Pick the questions you have a fair chance of winning, answer them clearly in the format Google already shows, and keep those answers accurate. With Search Console and a few hours a month, you could rework three or four pages in the first month and have a tracking sheet running by the end of it.

When there are more pages than time, we can help. Our answer engine optimisation and content optimisation work starts with an audit of where you already rank, then rewrites the pages most likely to be quoted by Google and AI tools.

Share:LinkedInXEmail