How to write an FAQ page people actually read

Three sources, in order of how much they are worth. A question invented to carry a keyword belongs to none of them and is the reason most FAQ pages are ignored.

1. 1

   Your support inbox

   Search the last three months for question marks. The questions that repeat are the ones costing you time, and the ones a buyer is asking silently before they pay.

2. 2

   Your sales calls and demos

   The objection raised in minute twelve of every call is an FAQ entry. So is the thing you find yourself explaining with your hands.

3. 3

   The results page

   The People also ask questions on your main query, which are the questions Google associates with it, phrased as people type them.

4. 4

   What people type into your own search box

   If your site or your docs have search, the empty-result queries are a list of questions your pages do not answer.

Two to four sentences. The first answers the question outright; the rest carry the qualification or the next step. No throat-clearing, no repeating the question back.

Notice what the right-hand column does: it commits. An answer that will not commit is worse than no answer, because the reader now knows you are avoiding the question.

The mistake that makes FAQ pages useless is sweeping every question onto one page, away from the moment it is asked.

• Pricing, billing, refunds and what happens at the end of a trial: on the pricing page, under the plans.
• Setup and limits of one feature: on that feature's page or in its documentation.
• Security, data location and deletion: on the security or privacy page, where a buyer looks for them.
• Questions about a subject you have a guide for: at the foot of that guide.
• The FAQ page itself: only the questions that belong to no single page, such as who you are, how support works, and what happens if you disappear.

A short FAQ section at the end of a page is worth more than a long FAQ page, because the reader is already there with the question in mind.

FAQPage structured data marks up a list of questions and their answers. Since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health sites, so a product site earns no rich result from it.

• It is still valid markup, and it is still read by assistants and other machines that parse a page.
• It costs a few minutes if your pages are generated from data, and it never earns a penalty when it matches the visible content.
• The rule that matters: every marked-up question and answer must be visible on the page. Marking up content a reader cannot see is a policy violation.
• Do not add it for a rich result you will not get, and do not remove it in a panic either.

The part of an FAQ that earns visibility is the writing: a question phrased as people ask it, with the answer in two to four sentences under it, is exactly the shape a featured snippet and an assistant both lift.

You have seen these. “What is the best invoicing software for small businesses in 2026?” followed by a paragraph about how the best invoicing software depends on your needs.

• Nobody asked it. It is a keyword with a question mark.
• The answer cannot commit, because the question exists to hold the phrase rather than to be answered.
• Twenty of them on one page is a page of nothing, and a family of such pages is what Google's guidance on content made at scale describes.
• They crowd out the three real questions your buyers ask, which are now below the fold.

The test before adding a question: can you name the person who asked it, or the place you saw it asked? If not, it does not go on the page.

For a fictional scheduling tool at yourproduct.com, the support inbox produced these five in an afternoon. Each one had been asked by a person that month.

1. What happens when my trial ends? The account keeps working in read-only mode and your links stop taking bookings. Nothing is deleted for ninety days.
2. Can I change plan mid-month? Yes, from /settings/billing. We charge the difference pro rata and the change takes effect immediately.
3. Do I need a card to start? No. The card is asked for when you first take a booking on a paid plan.
4. What counts as a booking? A confirmed slot on your calendar. Cancellations inside an hour do not count.
5. Can I get an invoice with my company details? Yes, add them on /settings/billing and every invoice is reissued with them.

Five answers, all committing, all on the pricing page under the plans. Support volume on those five questions drops, which is how you know the page worked.

• Review it when the product or the prices change, not on a calendar. A wrong answer on a pricing FAQ is a promise you did not mean to make.
• Add a question when support answers the same thing three times in a month.
• Remove a question when it stops being asked, rather than letting the page grow forever.
• Keep the date on the page honest: change it when the answers change, not to look fresh.

An FAQ is a support artefact that happens to be public. Treat it as part of support, and it stays true; treat it as a content page, and it drifts within a quarter.