FAQ schema and answer boxes: how to win featured snippets
A page wins a featured snippet or a voice answer because one passage on it is easy to lift out and read aloud, not because it ranks first. This guide covers the specific mechanics: a question-form heading, a 40-60 word self-contained answer directly beneath it, list formatting for how-to content, and FAQPage JSON-LD written correctly.
Two pages can rank in the same position and get completely different outcomes. One shows up as a plain blue link. The other gets pulled into the box above the results, gets read out by a voice assistant, and gets the click from anyone who wants more than the summary. The difference is almost never domain authority. It's structure.
This guide is not about schema.org basics, that's covered in the JSON-LD explainer. It's about the specific tactics that make a passage extractable: what to write in the first sentence after a heading, how to format a how-to so Google pulls it as a list, and how to mark up FAQs so the markup actually matches what Google expects, not what you assume it expects.
Step 1: pick a question your page can answer in one breath
Start from a real query, not a topic. 'Permit costs' is a topic. 'How much does the TIMS card cost?' is a query, and that's the phrasing to turn into a heading.
Pull questions from 'People also ask' boxes, Search Console's query report, and autocomplete. Give each one its own H2 or H3. Don't merge three related questions under one heading, Google usually grabs the whole block or picks badly.
- One question per heading, phrased the way people actually type or say it.
- Use the exact interrogative: 'how much', 'how long', 'is it safe', not a rephrased noun phrase.
- Check what snippet currently shows for the query, and match its format. Google rarely swaps formats for a query it has already resolved.
Step 2: answer inside the first 40-60 words, before anything else
This is the part most pages get wrong. The sentence right after the heading needs to be the answer, not a lead-in. Compare the two:
Weak: 'There are several factors that affect the cost of a TIMS card, and pricing has changed a few times in recent years, so let's look at what you'll actually pay.'
Strong: 'A TIMS card costs NPR 2,000 for independent trekkers and NPR 1,000 with a registered agency. Both are one-time fees valid for the whole trek, payable in cash at the TIMS counter in Kathmandu or Pokhara.'
The strong version is self-contained: read it with no other context and it still makes sense, which is the test Google's extraction is running. It also front-loads the number, since 'how much' queries get lifted from the first figure on the page, not the third paragraph.
- Answer in sentence one. Background, caveats and exceptions come after, not before.
- Target 40-60 words for the core answer, roughly the length Google displays; longer answers get truncated mid-sentence.
- Repeat the heading's key terms in the answer naturally, so the question-answer match is unambiguous.
- Cut every 'as mentioned above', 'this' or 'the following' that only resolves if the reader has seen earlier text. A snippet is read in isolation.
Step 3: format how-to content as an actual list, not prose
Google pulls list snippets from real HTML lists, ordered <ol> for sequences, unordered <ul> for unordered sets. It's far more reliable at extracting a clean numbered list than at reverse-engineering steps buried in a paragraph.
For 'how to renew a Nepali passport online', don't write four sentences describing the process. Write four numbered steps, each starting with an imperative verb, each short enough to read as one line.
- 1. Create an account on the MoFA passport portal and verify your email.
- 2. Fill in the application form with your citizenship and travel details.
- 3. Upload a passport photo and your citizenship certificate scan.
- 4. Pay the fee online and book an appointment at your nearest passport office.
- Each step should be one clear action. If a step needs three sentences, it's really two steps.
- For 'best' or 'types of' queries, use a bulleted list of named items with a short description each, not a paragraph that happens to contain commas.
Step 4: mark it up with FAQPage JSON-LD, exactly
FAQPage structured data doesn't force a rich result, but it removes ambiguity about which text is the question and which is the answer, and it's a prerequisite for the FAQ rich result where Google shows one. As of 2023 Google restricted that rich result mostly to authoritative government and health sites for most queries, so treat the markup as an extraction aid, not a guaranteed rich result.
The rule that trips people up: every Question and its acceptedAnswer must match text actually visible on the rendered page, in essentially the same wording. Marking up FAQs that don't appear on the page, or that sit only inside a collapsed accordion nobody expands by default, is exactly what Google's guidelines prohibit, and it can cost you rich-result eligibility site-wide if caught.
A minimal, correct two-question example:
- { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How much does a TIMS card cost?", "acceptedAnswer": { "@type": "Answer", "text": "A TIMS card costs NPR 2,000 for independent trekkers and NPR 1,000 for those trekking with a registered agency, payable once in cash at the counter in Kathmandu or Pokhara." } }, { "@type": "Question", "name": "Is a TIMS card required for all treks?", "acceptedAnswer": { "@type": "Answer", "text": "No. Routes inside restricted areas such as Upper Mustang or Manaslu require a separate restricted-area permit instead, and a handful of routes require neither." } } ] }
- Keep the 'name' field identical, or near-identical, to the visible heading text. Don't paraphrase it into something more keyword-stuffed for the schema than what's on the page.
- Put the JSON-LD in a single script block per page. If you have twelve FAQs, list all twelve as separate Question entries in one mainEntity array, don't split them across multiple FAQPage blocks.
Step 5: check what you actually won, then keep it
Search Console's Performance report lets you filter by search appearance for 'FAQ rich results' where applicable, and you can just search the query in an incognito window to see what shows. That's the fastest way to know if you got picked, with no reporting delay.
Snippets churn. Google re-selects the source continuously as pages update or competitors improve their structure, it isn't a one-time award. Revisit your top snippet-holding pages every few months: check the answer is still accurate, still under the word count, and still the tightest version competing for that query.
One failure mode to watch for: a page wins a snippet, then someone edits the intro during a redesign and the crisp 40-60 word answer gets diluted with marketing language. Guard the answer paragraph the way you'd guard a title tag.
Key takeaways
- ✓Turn each real search query into its own question-form heading, one question per heading, not several merged together.
- ✓Answer in the first sentence, in roughly 40-60 self-contained words, before any background or caveats.
- ✓Use real ordered lists for how-to steps and real bulleted lists for 'best' or 'types of' content, Google extracts list markup far more reliably than prose.
- ✓FAQPage JSON-LD must mirror text genuinely visible on the page; invisible or paraphrased markup risks losing rich-result eligibility.
- ✓A snippet is not permanent. Recheck the query periodically and protect the answer paragraph from being diluted by later edits.
Explore the data behind this guide
FAQ Schema & Answer Boxes, FAQ
How long should a featured snippet answer be?+
Roughly 40 to 60 words for a paragraph-style answer, which is about what Google displays before truncating. Put it as the first sentence or two under the heading, state the direct answer, then expand with detail afterward for readers who click through.
Does FAQPage schema guarantee a rich result?+
No. It makes your question-and-answer pairs unambiguous to Google and is a prerequisite for the FAQ rich result, but eligibility for the visible rich result itself is decided by Google and has been restricted mostly to authoritative sites for most queries since 2023. Treat it as an extraction aid, not a guarantee.
Why does Google pull a list snippet instead of a paragraph for the same topic?+
Google matches the snippet format to the query's implied shape and to what it can reliably extract. 'How to' queries favor real ordered-list HTML because a numbered sequence extracts cleanly. If your steps are written as prose sentences instead of an actual list element, you are giving Google worse raw material to pull from.
Can FAQ markup hurt my site?+
Yes, if the marked-up questions and answers don't match text visible on the page, or if you mark up FAQs hidden inside an accordion that isn't expanded. Google's structured data guidelines treat that as misleading markup, and violations can cost you rich-result eligibility across the site, not just on one page.
Where do I find the exact questions people are asking?+
'People also ask' boxes on the live search results for your target query, the Performance report in Search Console filtered to your page to see the actual query strings driving impressions, and autocomplete suggestions when you type the start of the question. Use the exact phrasing you find there as your heading.
Related guides
Sources & data note
This guide describes documented, widely-accepted practice as published by Google Search Central and schema.org, which are cited above. Google's rules for which sites qualify for FAQ rich results have changed before and may change again; verify current eligibility against the official documentation rather than relying on this guide alone. The Nepal-specific examples (TIMS card pricing, passport renewal steps) illustrate formatting technique and are not a substitute for checking current fees and procedures on the relevant official site. Guides are written from primary sources, Nepali government departments, operators, park authorities and standards bodies, and each guide lists the sources used for its own facts. Rules, fees and prices in Nepal change; treat figures as current at the review date shown on each guide and verify anything money- or visa-critical with the issuing authority before you rely on it.