How to Write FAQ Sections for Buyer Guides (That Rank in People Also Ask)
The FAQ at the bottom of a buyer guide is usually the least considered section on the page: five questions the writer made up, answered in a paragraph each, with schema markup added because a plugin offered to.
It can be more than that. A FAQ built from real questions and answered directly is the part of a guide most likely to appear in People Also Ask, and it's the section that catches the reader who read the verdict and still has one doubt.
This post covers where the questions come from, the format that wins the People Also Ask slot, how many to include, what FAQ schema does and doesn't do now, the questions that hurt (because they compete with your own posts), and a quick way to write the section in ten minutes. It's the FAQ entry in the buyer guides post, expanded.
The short answer
Take three to five questions from People Also Ask, autocomplete and owner reviews, phrased the way people type them. Answer each one in the first sentence, then add two or three sentences of why. Don't repeat the body, don't answer questions another post on your site targets, and keep the schema markup without expecting a rich result from it. Ten minutes per guide.
Where the questions come from
| Source | What it gives you | How to use it |
|---|---|---|
| People Also Ask | The questions Google already shows for the keyword | Search the keyword, note the first four, click two to expand more |
| Autocomplete | How people phrase questions about the product | Type "is [product]", "can [product]", "do [product]", "[product] vs" |
| Owner reviews | The doubts people had before buying, and after | Read the 3-star reviews of your top pick; the complaints are questions |
| Your own judgement | The question a friend would ask next | "Which one, though?" "Is the expensive one worth it?" |
Mix the sources. A FAQ built only from People Also Ask targets what already ranks, which is competitive; one built only from your judgement may target nothing anyone searches. Two from the first two sources, two from the second two, is a reasonable split.
The format that wins People Also Ask
People Also Ask shows a question and a short passage lifted from a page. The passage Google picks is the one that answers the question directly, in a sentence or two, right after the question. That means:
- The question is the heading, phrased as searched ("Is a 1,000-lumen bike light bright enough for unlit roads?"), not rewritten to sound clever.
- The first sentence is the answer. "Yes, for most riders; 1,000 lumens lights the road 30 to 40 metres ahead at commuting speeds." Not "There are a few things to consider."
- Two or three sentences of why follow, with the specific fact or trade-off.
- Forty to eighty words in total. Shorter gets cut off; longer doesn't get picked.
The same format works for AI assistants and voice search, which pull the same kind of passage. The titles post has the same answer-first logic applied to headings.
How many
Three to five. The reader who reaches the FAQ has read the guide and has one or two doubts left; five questions covers that. Beyond five, questions start to be invented to fill the section, the answers get thinner, and the section reads as what it is.
Fifteen questions with one-line answers is a pattern Google's helpful-content guidance describes as content made for search engines rather than people.
What FAQ schema does now
FAQ structured data used to produce the expanded question-and-answer display under a result. In August 2023 Google limited that display to authoritative government and health sites, so a buyer guide's FAQ markup no longer produces a visible rich result.
The markup is still worth keeping: it tells Google exactly which text is a question and which is its answer, which helps with People Also Ask passage selection and does no harm. Keep it; don't add questions to feed it.
Questions to leave out
- Questions another post on your site targets. "How do I clean a bike light?" in the bike lights guide's FAQ competes with your how-to post for that keyword. Link to the post instead; the internal linking post covers the anchor.
- Questions the body already answered. "Which bike light is best?" when the verdict is at the top. Padding.
- Questions about products not in the guide. They pull the FAQ off-topic and the reader with them.
- Questions nobody asks. "What is the history of the bike light?" Check it exists in one of the four sources before writing it.
- Price questions. "How much does X cost?" needs a number that goes stale and that Amazon's rules say shouldn't be printed.
A ten-minute method
- Search the keyword; copy the first four People Also Ask questions.
- Type "is [top pick]" and "can [top pick]" into Google; note two autocomplete questions.
- Read five 3-star owner reviews of the top pick; note the recurring doubt.
- Pick four of those seven that the body doesn't answer and no other post of yours targets.
- Write each answer: first sentence answers, then the why, 40 to 80 words.
- Keep the question wording as searched; mark it up as FAQ schema.
Doing it with AffSERP
AffSERP's X Best Review tool writes a FAQ section into every guide in the format above: questions phrased as searched, a direct answer in the first sentence, and the schema markup generated with it. The questions come from the keyword and the product data, so they're about the products on the page.
The one step still worth doing by hand is step four: scan the generated questions against the other posts on your site, and swap any that compete with a post you've already published for one from owner reviews.
FAQ
How many questions should a buyer guide FAQ have?
Three to five. Enough to cover the questions a buyer has after reading the guide, few enough that each one gets a real answer. Fifteen questions is a sign the section is being used to stuff keywords, and readers and Google both read it that way.
Does FAQ schema still help with rankings?
It doesn't produce the expanded FAQ display in results any more for most sites; Google limited that in 2023 to government and health sites. The markup is harmless and still helps Google parse the questions, so there's no reason to remove it, and no reason to expect a visual result from adding it.
Where do I find the questions for a FAQ section?
Google's People Also Ask box for the guide's keyword, autocomplete for 'is [product]' and 'can [product]', the questions in owner reviews of the products you picked, and the questions a friend would ask you after you said which one to buy. The last source produces the best ones.
Should the FAQ repeat things already in the guide?
No. Each question should add something the body doesn't cover, or answer a question the body raised. A FAQ that restates the verdict and the top pick's specs is padding. A good test: if deleting the question loses nothing, delete it.
Keep reading
