FAQ Section SEO: How to Pick and Write the Questions
An FAQ section helps SEO when it answers the short follow-up questions people search around your topic, each in two to four sentences that start with the answer. It won’t rank a page by itself, and FAQ rich results are now limited to a small set of sites, so write it for readers first.
Here’s how to pick the questions, how to write the answers, what changed in Google’s results, and when an FAQ isn’t worth adding.
Does an FAQ section still help SEO?
It can, in a narrower way than it used to. In August 2023, Google limited FAQ rich results to well-known government and health sites. For most blogs, adding FAQPage markup no longer produces the expandable questions under the search result.
What an FAQ still does is cover questions your main sections don’t. Someone searching “how long should a sales page be” may land on a sales page guide whose FAQ answers exactly that in three sentences. The FAQ also gives AI assistants short, self-contained answers they can quote. Neither of those is guaranteed, but both depend on the same thing: real questions with direct answers.
Which questions belong in a post’s FAQ?
Questions that are related to the topic, short to answer, and not already answered by an H2. If a question needs a table or several paragraphs, it deserves its own section, or its own post.
| Source | Where to look | Good sign |
|---|---|---|
| Search suggestions | Autocomplete and “People also ask” for your query | The question repeats across several searches |
| Customer questions | Sales calls, support tickets, replies to your emails | You’ve answered it more than once |
| Comments | Your posts, forums, community threads | People ask it in their own words |
| The post itself | Places you wrote “it depends” and moved on | A reader would want the condition spelled out |
Pick four or five. Fewer looks like an afterthought. More turns the FAQ into a second article, and the questions start overlapping with your sections.
Leave out questions that exist only to repeat the keyword. “What is the best FAQ section SEO strategy?” is a phrase built for a search engine, not a question anyone asks.
How should you write FAQ answers?
Start with the answer itself, in the first few words. “Usually no” or “Four to five questions” is a better opening than a restated question. Then give the condition or reason in one or two more sentences.
Each answer should stand alone. A reader who jumps straight to it, or an assistant that quotes only that answer, shouldn’t need the rest of the post to understand it. That means no “as mentioned above” and no pronouns that point back to an earlier section.
Keep the tone of the rest of the post. FAQ answers often slide into a stiff, legal voice. Write them the way you’d answer the question in an email.
Questions go in H3 headings under one “FAQ” H2, written exactly as someone would ask them. Our blog post structure for SEO guide shows where the FAQ sits in the full template.
Should you add FAQ schema markup?
FAQPage markup is still valid structured data, and adding it doesn’t hurt. For most sites it won’t trigger a rich result anymore, so it’s a low priority. If your templates already add it to pages that have a real FAQ, keep it. If you’d have to build it, spend the time on the answers instead.
Never mark up questions that aren’t visible on the page, and don’t use FAQ markup for advertising. Google’s structured data guidelines require that marked-up content matches what users see.
When should you skip the FAQ?
When nobody has questions left. A short how-to that answers one narrow question completely may not have four honest follow-ups, and padding it with invented ones makes the page worse.
Skip it, too, on pages where the questions belong somewhere else. A sales page has objections, which work better answered in the flow of the page or in an objection section. A product page may need a spec table more than an FAQ.
On this blog every post has an FAQ because each one targets a question that has natural follow-ups. That’s a house rule for articles, and our draft checks skip it for landing pages.
How do you check the FAQ before publishing?
Run through the list:
- Four or five questions, each an H3 under one FAQ heading.
- None of them repeats an H2.
- Each answer starts with the answer and stands alone.
- No answer needs more than four sentences.
- Every fact in an answer has a source or comes from your own experience.
Copix Complete can run part of this check for you. The seo tool’s check_draft action confirms the draft has an FAQ with four or five questions, alongside the title, description, direct answer, table, question H2s and internal links. It also scores the draft for honesty and hype, and runs an on-page audit. It doesn’t judge whether your questions are the right ones; that part is yours. For one post a month, the checklist above is enough. If you publish often, see what the SEO engine checks, compare the plans, or read how to choose target keywords for the step before the draft. The rest of the product is on the home page.
FAQ
How many questions should an FAQ section have?
Four or five works for most blog posts. That’s enough to cover the common follow-ups without repeating the main sections. A dedicated FAQ page can have more.
Should FAQ questions include the target keyword?
Only where it fits naturally. Write questions the way people ask them. One or two may contain the keyword, and forcing it into every question reads badly.
Will FAQ schema give me rich results?
For most sites, not anymore. Since August 2023, Google shows FAQ rich results mainly for well-known government and health sites. The markup is still valid but rarely changes how your result looks.
Where should the FAQ go on the page?
Near the end of the post, after the main sections and before or after a short product mention. Readers who need the main answer get it first, and those with follow-ups find them in one place.
Can AI write my FAQ questions?
It can suggest them, but check each against real sources like search suggestions and customer questions. Models tend to produce questions that sound plausible and that nobody asks.