Writing for featured snippets and People Also Ask

A featured snippet is the highlighted answer Google sometimes shows above or among the top organic results: a paragraph, a list or a table taken from one page, with a link to it. People Also Ask (PAA) is the expandable box of related questions, each of which reveals a short extracted answer and its source when opened. Both are drawn from ordinary web pages, both reward clear writing, and both are worth understanding even as AI-generated answers take up more of the results page, because the same qualities make content easy for AI systems to quote.

How the extraction works, as far as is public

Google has not published the details of snippet selection, but its documentation and long observation agree on the basics:

• The source almost always already ranks on the first page for the query, usually in the top few positions. Snippets are not a shortcut from page three.
• The text is extracted, not written. Google picks a passage, list or table that directly answers the query and displays it, sometimes trimmed.
• Format follows the question. "What is" questions tend to get paragraphs; "how to" and "steps" questions get numbered lists; "best", "types of" and "examples" get bulleted lists; comparisons and specifications get tables.
• It changes often. The chosen source and passage can change from week to week, and a snippet may appear for some searchers and not others.

Find the opportunities

The best targets are queries where you already rank in the top five and a snippet or PAA box exists, but the snippet goes to someone else. In Search Console, list queries where your average position is between roughly 1 and 6, then check the results page for each one manually. Questions phrased as questions ("how", "what", "why", "can", "does") are the most common snippet triggers.

For PAA, search your main topics and expand the boxes; each expansion loads more questions. Note the questions that appear repeatedly across related searches. They are the questions your pages should answer explicitly, whether or not you win the box.

Writing paragraph answers

For "what is", "why" and "does" questions, the snippet is usually a paragraph of around 40–60 words. Write it like this:

1. Put the question, or a close variation, in a heading (<h2> or <h3>).
2. Answer it in the first sentence directly below, in a way that makes sense on its own.
3. Complete the answer in two or three more sentences.
4. Expand with detail, examples and caveats after that.

Compare two openings for "what is a canonical tag":

Weak: "Canonical tags are something that many site owners have heard of, but there is a lot of confusion about them. In this section we will explore..."

Strong: "A canonical tag is a line of HTML in a page's head that tells search engines which URL is the main version of that page when the same content is available at several addresses. It is a hint rather than a command."

The strong version is extractable as it stands. It is also better for readers, who get the answer immediately.

Avoid starting the answer with a pronoun that depends on the heading ("It is a line of HTML…"), with "Yes" or "No" alone when the full sentence matters, or with a hedge that delays the answer. Definitions work best in the classic form: the term, a short category ("a line of HTML", "a type of redirect"), then what makes it distinct. Keep promotional language out of the answer itself; a passage that reads like an advertisement is a poor candidate for a neutral answer box.

Writing list answers

For steps and lists, use real HTML lists: <ol> for steps in order, <ul> for unordered items. Keep each item short at the start (the snippet may show only the first few words of each), and put detail in following sentences or sub-paragraphs.

• Put the list directly under the heading that matches the question.
• Start each step with a verb for how-to content: "Remove", "Measure", "Apply".
• If there are many steps, keep the list complete; Google may show the first several with a "more items" link, which encourages clicks.

Lists built from styled paragraphs or divs, or steps hidden in images, are much harder to extract.

Writing table answers

For comparisons, prices, specifications and "X vs Y" questions, a real HTML <table> with a header row is the clearest format. Keep it simple: a few columns, short cells, units in the header. Tables rendered as images or built with CSS grids rarely become snippets. Tables also help readers scan and help AI systems quote figures accurately.

People Also Ask: cover the neighbours

PAA questions show what searchers ask next. A page that answers its main question and the three or four most common follow-up questions serves readers better and has more chances to be pulled into a PAA box. Practical approach:

• Collect PAA questions for the page's main query.
• Answer the most relevant ones inside the body, each under its own heading where they fit the flow.
• Add a short questions section at the end for the rest, each with a direct two- or three-sentence answer.

Do not try to answer every PAA question on one page. Questions with a different intent belong on a different page; see search intent.

About FAQ markup and HowTo markup

FAQPage structured data once produced expandable question rich results for many sites. Since 2023 Google limits FAQ rich results to a small set of well-known government and health sites, and HowTo rich results have been removed from search results. The markup is not harmful, but for most sites it no longer changes how results look. Keep FAQ sections for readers; they are still read and quoted. The structured data guide covers which markup still matters.

Why you lost a snippet you had

Snippets move. When one disappears, the cause is usually one of these:

• Your ranking slipped below the positions snippets are typically drawn from. Fix the ranking first; the snippet follows.
• A redesign changed the structure. A new template that turns lists into styled divs, moves the answer below a large hero image, or collapses headings into accordions can make extraction harder.
• Someone edited the answer into a longer, vaguer introduction. Check the page history.
• A competitor wrote a more direct answer, or a table where you have prose.
• The results page changed. An AI-generated summary or a different feature now occupies the space where the snippet used to be, and the query no longer shows a snippet for anyone.

Checking the live results for the query and comparing the current snippet's passage with your own usually reveals which one it is within a minute.

Snippets, clicks and AI answers

A featured snippet can raise or lower clicks. For a query whose full answer fits in the snippet ("how many ounces in a cup"), many searchers will not click. For queries where the snippet is a teaser to a longer process, being the snippet usually brings more clicks than ranking first without it. Check in Search Console: compare CTR for the query before and after you gained or lost the snippet.

AI-generated summaries in search and AI assistants draw on similar qualities: clear, self-contained statements, well-structured lists and tables, and pages that already rank well. Writing for snippets is good preparation for being cited in AI answers; the guide to content AI assistants quote goes further.

A checklist for one page

1. The page already ranks on page one for the target question.
2. The question appears as a heading.
3. The first sentence under it answers it directly and stands alone.
4. Steps use <ol>; options use <ul>; comparisons use a real table.
5. The top PAA questions are answered on the page.
6. No snippet-blocking directives (nosnippet, restrictive max-snippet) unless intended. The SEO checker reports the robots directives a page sends.

If after a few weeks another page still holds the snippet, compare its passage with yours: it is often shorter, more direct, or in a more suitable format.