Most FAQ sections are a missed opportunity. They're written by the brand, for the brand — questions like "Why should I choose you?" that no one actually types into Google. A good FAQ section does the opposite: it answers the questions real people are already searching for, in language they already use.
Here's how to build one that earns traffic.
Why FAQs Matter for SEO
FAQ sections target two different search behaviors:
People Also Ask (PAA) boxes. When Google displays those expandable "People also ask" questions in search results, they're pulling from pages that have clear, concise answers to common questions. A well-written FAQ section is one of the most reliable ways to get your content featured there.
Long-tail and conversational queries. FAQs naturally match how people phrase search queries — complete questions rather than keywords. "How long does it take to get approved for a mortgage?" is a question users type verbatim. A page that answers it directly has a strong chance of ranking for that exact phrase.
FAQPage schema. Adding structured data (FAQPage JSON-LD) to your page tells search engines exactly what your FAQ section contains. This can trigger rich results in Google search — expanded question/answer previews that take up significantly more SERP real estate than a regular link.
All three of these benefits compound. The same FAQ section can rank as a traditional result, appear in a PAA box, and show rich results from schema markup simultaneously.
Finding Questions People Are Actually Asking
The biggest mistake in FAQ writing is inventing questions. Don't ask yourself "what would a customer want to know?" — ask yourself "what has someone already typed into a search bar or posted in a forum?"
Google's People Also Ask. Search your topic and look at the PAA box that appears in results. These questions are pulled directly from Google's understanding of search behavior. They're not guesses — they're data. The related questions that expand when you click on one are valuable too.
Reddit. Search your topic in Reddit. Questions that appear repeatedly across multiple threads — "is X worth it?", "how long does X take?", "what's the difference between X and Y?" — are real questions from real users. The language people use in their posts is often exactly how they'd phrase a Google search. The subreddit finder can help you identify which communities your audience actually uses, so you're not just searching the obvious ones.
Quora. Quora questions are typically more detailed than Reddit titles, which makes them useful for understanding the full scope of what someone wants to know when they ask a question. One Quora question often contains multiple sub-questions worth addressing.
Your own support inbox. If you have customers, look at what they're emailing you about before they become customers. Pre-sales questions are FAQ gold — they're the exact friction points between "browsing" and "buying."
If you want to do this research at scale, the pain point research tool surfaces recurring questions and complaints across Reddit and Quora in a single pass.
Writing Answers That Actually Help
Keep answers short. 2–4 sentences is almost always enough. Google's featured snippet box holds about 40–60 words. If your answer is 400 words, it won't get featured and it won't be read.
Answer the question in the first sentence. Don't wind up to the answer — state it immediately. "Yes, you can cancel anytime from your account settings." Then add context in the following sentences if needed.
Be specific. Vague answers ("it depends on your situation") are useless. If something genuinely varies, explain what it varies based on: "It depends on your plan — Starter plans have a 30-day free trial, Pro plans have 14 days."
Match the user's language. If people ask "how do I get rid of X," your answer should use the word "get rid of X," not the technically correct but less familiar term you use internally. This isn't about dumbing things down — it's about actually being found.
Adding FAQPage JSON-LD Schema
Once you've written your FAQ section, adding schema markup is straightforward. Here's the structure:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the refund policy?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We offer a 30-day money-back guarantee on all plans. No questions asked."
}
},
{
"@type": "Question",
"name": "Can I change my plan later?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. You can upgrade or downgrade your plan at any time from your account settings. Changes take effect on your next billing cycle."
}
}
]
}
</script>
Place this script tag in the <head> of the page or anywhere in the <body>. The "Copy JSON-LD" button above generates this structure automatically from your results.
Once it's live, you can verify it with Google's Rich Results Test to confirm Google is reading it correctly.
How Many FAQs to Include, and Where
5–8 FAQs is the right range for most pages. Fewer than 5 doesn't give the schema enough substance. More than 10 and you're diluting the most important questions with less important ones.
Where to put them:
- Dedicated FAQ pages work well if you have a broad product with many distinct question categories (billing, technical, policy, etc.)
- Bottom of article pages is the most common placement — after the main content, before the footer. This captures users who scrolled to the end but didn't find their specific answer in the article
- Product and landing pages benefit from FAQs that address purchase objections specifically: pricing, refunds, setup time, compatibility
Don't put FAQs at the top of an article unless they serve as a table of contents. The main content should answer the primary search intent first.
Common Mistakes to Avoid
Writing questions in third person. "What does our company offer?" is not a question anyone types. Write questions in first person ("How do I…") or second person ("Can you…"), which is how real people phrase searches.
Duplicating your main content. The FAQ section should answer questions that aren't already covered in the main body of the page. If your article explains how the onboarding works, your FAQ shouldn't have "How does onboarding work?" — that's already covered.
Forgetting to update them. FAQs go stale. If your pricing changes, your refund policy changes, or a feature gets renamed, your FAQ section will start sending people wrong information. Build a habit of reviewing FAQ sections whenever product details change.
What to Do After You Publish
After the page is live with schema markup, submit it to Google Search Console for indexing. Check back after a week or two to see if the rich results are appearing in the Coverage or Performance report.
If you want to go further than a one-page FAQ — tracking what questions come up across multiple communities, monitoring new questions that emerge over time, or building an ongoing content strategy around real search intent — Reddinbox pulls live conversations from Reddit, YouTube, X, and more and surfaces the recurring questions worth answering.