Most FAQ pages are written for the company, not the customer. They answer questions the marketing team finds comfortable — "What makes us different?", "How do I get started?" — and quietly skip the ones that arrive in the inbox every week. The result is a page that ranks for nothing and persuades nobody.

A useful FAQ page does three jobs at once: it removes a reason not to buy, it gives support a page to link to, and it gives search engines the exact phrasing people use when they are close to a decision. All three depend on the same thing — using real questions.

Find the questions people already ask

You do not need to invent anything. Look in four places and write down the questions verbatim, including the typos.

  • Support inbox. Export the last three months and group messages by intent. Five or six patterns will cover most of the volume.
  • Sales calls. Note every question asked in the final five minutes before a decision. That is where the real barrier sits.
  • Search Console. Open the Queries report and look for question-shaped searches. "How long does delivery take to Ireland" is a page heading waiting to happen.
  • Site search and chat logs. Even a handful of site searches reveals words customers use that your navigation does not.

Rank them by frequency first, risk second. A question asked twice but tied to a refund is more valuable than one asked ten times about opening hours.

Answer in the first sentence

The most common mistake is burying the answer under a paragraph of context. If the question is "Do you offer refunds?", the first line must be "Yes — within 30 days of delivery, no questions asked." Everything after that is detail.

A workable shape for each entry:

  1. Direct answer, one sentence, 15–30 words.
  2. One short paragraph of the condition, exception or process.
  3. A link to the page that handles the details — delivery, returns, pricing, contact.

Keep answers under about 120 words. If an answer needs more, it is not an FAQ entry; it is an article, and the FAQ should link to it with a single-sentence summary.

Write the question the way it is asked

Headings should sound like a person typing into a search box, not like a legal document.

  • Weak: "Shipping Information"
  • Better: "How long does delivery take, and what does it cost?"
  • Weak: "Returns Policy Enquiries"
  • Better: "Can I return an item if it does not fit?"

Use one question per heading and put it in an h2 or h3 — never a bold paragraph. Headings are how people scan, how screen readers navigate, and how search engines understand the structure of the page. A page of bold text is a page with no structure at all.

Group by moment, not by department

Alphabetical order helps nobody. Group questions in the order a customer meets them:

  1. Before buying — fit, price, compatibility, lead time
  2. At checkout — payment methods, invoices, VAT, currencies
  3. After buying — delivery, tracking, changes, cancellations
  4. If something goes wrong — faults, returns, refunds, complaints

Within each group, lead with the highest-volume question. Readers stop scanning after the first three, so the order matters more than the completeness.

What about FAQ schema?

Adding FAQPage structured data is still worth doing for clarity, but do not expect the expandable rich results that used to appear in Google. Since 2023 those are limited to well-known government and health sites. For everyone else the markup is a signal, not a display format — so never write awkward copy to chase it. The visible page is what earns the click.

If you already use structured data elsewhere on the site, keep the FAQ markup consistent with the visible text. Marking up answers that are hidden or worded differently is a fast way to lose trust.

Answer the awkward questions

The questions companies avoid are usually the ones that decide the sale. Include them, and answer plainly:

  • "Why are you more expensive than [competitor]?"
  • "What happens if I cancel halfway through?"
  • "Do you use AI to write the articles?"
  • "Who owns the work once it is paid for?"

A straight answer reads as confidence. Vague reassurance reads as evasion, and evasion is expensive: it moves the doubt into the sales call, where it is harder to resolve.

Keep the page current

An FAQ page rots faster than any other page because policies change quietly. Put it on a quarterly review, and update it the same day you change a price, a delivery partner or a refund window. Add a "last reviewed" date at the top — it is a small signal of care that customers notice.

Checklist

  • Questions taken from support, sales, site search and Search Console — not invented
  • Every answer starts with a direct response in the first sentence
  • One question per heading, marked up as h2 or h3
  • Grouped by customer moment, highest volume first
  • Links out to the pages that carry the detail
  • The awkward questions included and answered plainly
  • Reviewed quarterly and after every policy change

If the answers keep turning into long explanations, the problem is usually upstream: the service page or the product page is leaving gaps. Fix the source and the FAQ gets shorter.