By Mehdi HassanWhat makes a good FAQ section on a website?
A good FAQ section answers the questions that stop people from buying, in words they'd use, with answers short enough to read in one glance. It's not a dumping ground for content that didn't fit elsewhere, and it's not a list of keywords phrased as questions. Each answer should settle a doubt and send the reader on to the next step.
Done well, an FAQ does three jobs at once: it handles objections for human readers, it gives search engines clear question-and-answer passages, and it gives AI engines short, self-contained answers to quote. That last job is why FAQs are one of the core blocks of an AI-search-ready website, alongside answer-first pages and real tables.
Where should FAQ questions come from?
FAQ questions should come from the conversations your team already has with buyers. The questions sales hears on every call, the ones support answers every week and the objections that stall deals are the ones visitors have too. Keyword tools are useful for checking phrasing, but they're a poor source of the questions that actually block a purchase.
Source | What it gives you | Example question |
|---|---|---|
Sales call notes and recordings | Objections and buying-stage worries | Can we cancel if it doesn't work for us? |
Support tickets | Confusion about how things work | Does the price include setup? |
Lost-deal reasons | The doubts that cost you customers | Do you integrate with HubSpot? |
People also ask results | How searchers phrase related questions | How long does onboarding take? |
Live chat and contact forms | Questions people ask before they're ready to talk | Do you work with companies outside the US? |
Aim for four to eight questions per section. Fewer leaves real doubts unanswered; more turns the FAQ into a wall that nobody scans. If you have twenty good questions, split them across the pages where each one comes up.
How do you write FAQ answers that get quoted?
Write each answer so it starts with the answer itself, stands on its own and stays between 40 and 80 words. The first sentence should be a complete reply to the question that would make sense if an engine quoted only that sentence. The rest adds the condition, the exception or the next step.
Phrase the question the way buyers say it
Use their words, not your internal terms. Ask "Can I cancel anytime?" rather than "What is our subscription termination policy?"
Answer in the first sentence
Start with yes, no, a number or a direct statement. "Yes, you can cancel at any time from your account settings."
Add the one thing they need next
The condition, the exception or what happens after. Keep it to one or two more sentences.
Make it standalone
Repeat the subject instead of writing "as mentioned above". Every answer should make sense out of context.
Link once, if it helps
Point to the page that goes deeper, such as pricing or a guide. One link per answer is plenty.
The same principles apply to the whole page, not just the FAQ. Our framework for answer-first page structure shows how to write every section this way.
How should an FAQ section be designed?
An FAQ section should be designed for scanning: questions visible at a glance, answers one click or tap away, and the text in the page's HTML. An accordion is the standard pattern and works well, as long as it's built so the answers exist in the page from the start rather than being fetched when someone clicks.
- Use real buttons or native details elements for each question, so the accordion works with a keyboard and a screen reader.
- Keep answers in the HTML. Visually collapsed text is fine for crawlers; text loaded from an API on click isn't there at all. Our piece on server-side rendering for AI crawlers explains why.
- Show the first answer open on short lists, so visitors see what an answer looks like.
- Make the whole question row clickable, with a clear plus, chevron or arrow that changes state.
- Keep motion subtle. A quick height transition helps; a slow bounce gets in the way. See when animation helps and when it hurts.
Accordion or plain list: which is better?
For four to eight questions on a sales page, an accordion keeps the section compact and lets visitors pick the questions they care about. For a dedicated FAQ or help page with many questions grouped by topic, a plain list with visible answers can be better, because people can scan and use find-in-page.
Both are fine for search engines, as long as the text is in the HTML. Choose by what the reader needs: a quick objection check near a call to action suits an accordion; a reference page suits open answers with headings.
Where should FAQ sections go on a website?
Put FAQ sections on the pages where the questions come up, usually near the bottom just before the final call to action. A pricing page FAQ handles billing and contract worries; a product page FAQ handles how-it-works questions; a landing page FAQ handles the last objections before someone books or signs up.
Page | Questions that belong there |
|---|---|
Pricing | Billing, contracts, cancellation, what's included, discounts |
Product or feature page | How it works, setup, limits, compatibility |
Landing page | The top three objections for that offer |
Integrations page | Which tools, how they sync, what it costs. See SaaS integrations page design |
Homepage | Two or three questions about who it's for and how to start |
Help or FAQ hub | Everything else, grouped by topic with headings |
Does FAQ schema still help SEO?
FAQ schema helps much less than it used to. Google has limited FAQ rich results to a small set of well-known government and health sites, so most businesses no longer get the expanded result in search. And there's no evidence that FAQPage markup makes AI engines cite you: Ahrefs' controlled 2026 test found no significant lift from adding schema.
We still add it, because it costs nothing when the template generates it from the same fields that render the visible FAQ, and it labels the content clearly for any system that reads it. The rule is simple: only mark up questions that are visible on the page, word for word. For the wider evidence, read whether schema markup helps AI citations.
