Content Strategy
How to Write FAQ Content That Helps Customers and Search
Collect real questions, write direct answers and decide where FAQs belong on your site.
By the Seozumi editorial team · · about 5 min read
Customers ask the same questions again and again: how much, how long, what is included, what if something goes wrong. Answering those questions clearly on your website helps visitors decide, reduces repetitive calls, and gives search engines direct answers to match with real searches.
Collect real questions
- Ask your team for the top ten questions they hear on calls, emails and chats.
- Read your reviews and competitors’ reviews for confusion or concerns.
- Check Google’s “People also ask” and autocomplete for your main services.
- Look at Search Console queries that contain “how”, “what”, “can”, “does”.
Keep each question in the customer’s own words. See how to find SEO blog topics for more sources.
Where FAQs belong
| Type of question | Best place |
|---|---|
| About a specific service or product | An FAQ section on that service or product page |
| About ordering, shipping, payment, returns | A help or policies page, linked from checkout |
| Needs a long, detailed answer | Its own article, linked from the short FAQ answer |
| About your company in general | About or contact page |
A single giant FAQ page with fifty unrelated questions is hard to use. Short, relevant FAQ sections on the pages people are already reading usually work better.
How to write a good answer
- Answer in the first sentence. “Most standard installs take one day” before any explanation.
- Add the detail that matters: conditions, exceptions, typical ranges.
- Keep it accurate and current. If prices change, label ranges as typical and date them.
- Link to the page with full details or the next step.
- Use plain language and avoid marketing claims.
Example (illustrative): How long does a tankless water heater install take? “Most replacements of an existing gas unit take one working day. If we need to upgrade the gas line or venting, it may take a second day; we will tell you before we start.”
Structure and markup
- Use the question as a heading (H2 or H3) or in an accessible accordion. Content in collapsed accordions can still be indexed if it is in the HTML.
- Keep answers visible in the page’s HTML, not loaded only after clicks from another server.
- FAQ structured data rich results are now shown only for a limited set of authoritative government and health sites, according to Google’s FAQ structured data documentation. Valid markup does no harm, but do not expect extra result features from it.
Mistakes to avoid
- Invented questions nobody asks, written only to include keywords.
- The same FAQ block copied onto every page.
- Answers that dodge the question (“Contact us for details”) when you could give a typical answer.
- Outdated answers about prices, hours or policies.
Keep it alive
Review FAQs every few months. Add new questions from support, remove ones nobody asks anymore, and update answers when things change. Our guide to updating old content covers how to refresh pages honestly.
