How do I write a good FAQ page?

Get the questions from reality, not from imagination

The failure that defines most FAQ pages is that the questions were invented in a meeting. "Why should I choose you?" is not a question anyone has ever typed. It is a marketing prompt wearing a question mark.

The real ones are already written down. Go and get them:

• Your inbox and messages. Search for question marks. The same five will appear over and over.
• Whoever answers the phone. Ask them what they are tired of explaining. They will tell you immediately and it will be a better list than anything you would have guessed.
• Your reviews, especially the annoyed ones. Every complaint about a surprise — a fee, a wait, a policy — is a question you failed to answer in advance.
• Google's own suggestions. Type your service and your city into the search box and read the autocompletes and the "people also ask" panel. Those are literal recorded questions.

If a question on your page did not come from one of those four places, take it off.

The format that gets quoted

This matters more than it used to, and it is the reason FAQ pages are worth doing well now.

Search engines and AI assistants lift a complete answer that sits immediately under a clearly-phrased question. Not "we offer a range of flexible options tailored to your needs" — an actual answer, in the first sentence, that would still make sense if somebody read it out loud with no other context.

So the shape is:

Question, phrased the way a person would say it. "Do you take card?" not "Payment methods accepted."

The answer in the first line. Yes, no, the number, the time. Then the nuance if there is any. The single most common mistake is a paragraph of context before the answer, which means an assistant lifting the opening sentence quotes something useless.

One question, one answer. Do not bundle three related things under one heading, because then no part of it can be quoted cleanly.

Written this way an FAQ entry can become the answer somebody's phone reads out loud. Written the other way it is invisible — see will AI assistants recommend my restaurant and voice search and your business.

Answer the uncomfortable ones

This is what separates a page that builds trust from a page that fills space.

The questions customers actually want answered are the awkward ones: what does it cost, why are you more expensive, what happens if it goes wrong, how long is the wait, what is not included, can I cancel.

A FAQ page that answers only the easy questions signals that the hard answers are bad. Answering them plainly does the opposite — and it removes the enquiry where somebody asks a question you were never going to win on, which saves you the call and them the time.

If the honest answer is unflattering, say it and explain why. "We are not the cheapest, and here is what the difference buys you" outperforms silence every time.

Where the questions should live

One page or spread across the site? Both, and the distinction is worth getting right.

Questions about a specific service belong on that service's page, right under the description. That is where the person is when the question occurs to them, and it helps the page rank for that question.

A single FAQ page collects the general ones — hours, payment, delivery, cancellation, access — and is the page you link when somebody asks by message.

What does not work is a FAQ page as a dumping ground for everything the site failed to say elsewhere. If a question is genuinely important, its answer belongs on the page where the decision is being made, not filed three clicks away.

Keep it short and keep it true

Ten well-chosen questions beat forty. A long FAQ page reads as an obstacle course and the important answers get buried in it.

And put it in the review cycle, because FAQ pages go stale invisibly. Prices change, policies change, the thing everyone used to ask about stops mattering and a new question takes its place. A FAQ page confidently giving last year's cancellation policy is worse than not having one — see how often should I update my website.

What this looks like in Helm

The whole practice above depends on one thing: adding a question has to take two minutes.

That is the mechanism, and it is why most FAQ pages are frozen at whatever was written on launch day. The best time to add an entry is the moment somebody asks it for the third time this week — and if that means emailing a developer and waiting, it does not happen, and the page ossifies while the questions move on.

On Helm the FAQ entries are content you edit: add a question, write the answer, press Go Live, in both languages if you run in both. So the page tracks what customers are actually asking rather than what they were asking two years ago. Each entry renders as a real question and answer in the page's own HTML — the answer text is in the page rather than fetched in by a script after it loads, so it is there to be read and quoted rather than locked behind a click.

The short version

Take the questions from your inbox, your phone and your reviews — never from a meeting. Answer in the first line, one question per answer, in the customer's own words. Include the uncomfortable ones, because those are the ones being asked. Keep it to ten. And add to it the week somebody asks, which only happens if adding takes two minutes rather than a fortnight.