# How to write an FAQ page people actually read

The questions come from support, from sales calls and from the results page, never from a keyword tool. Each answer runs two to four sentences and commits to something. Most of them belong on the page where the question arises rather than on a separate FAQ page, and the markup earns no rich result on a product site any more, though assistants still read it.

Updated 2026-09-15 · Source: https://porteur.ai/guides/how-to-write-an-faq-page

## Where the questions come from

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. **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. **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. **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. **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.

> A question worth publishing has been asked by a person in words you did not choose. That is the whole selection rule.

## The shape of a good 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.

| Weak answer | Answer that does the job |
| --- | --- |
| “Can I cancel? We understand that circumstances change and we aim to be flexible with our customers.” | “Yes, from /settings/billing, and the plan runs to the end of the period you paid for. We do not ask why and there is no retention call.” |
| “Is my data secure? We take security very seriously.” | “Your data is encrypted in transit and at rest, stored in the EU, and deleted within thirty days of you closing the account. The detail is on our security page.” |
| “Do you offer a free trial? Please see our pricing page for more information.” | “There is a free check that needs no card. The report itself is bought once, from 99 euros, with no subscription.” |

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.

## What belongs on the FAQ page, and what belongs elsewhere

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.

## The markup, and what it earns now

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.

## The anti-pattern: questions written for a keyword tool

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.

## A worked example: a pricing FAQ

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.

## Keeping it honest

- 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.

## Questions

### Does FAQ schema still get a rich result?

Not on a product site. Since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health sites. The markup remains valid and is still read by assistants, so keep it if you have it, but do not add it expecting stars in the results.

### Should I have one FAQ page or FAQ sections on each page?

Sections on each page, for anything that belongs to that page: pricing questions on the pricing page, setup questions in the docs. Keep a single FAQ page only for questions that belong nowhere else, such as who you are and how support works.

### How many questions should an FAQ have?

As many as have actually been asked, which for a small product is usually between five and fifteen. Twenty questions where you can only name the source of three means the other seventeen were invented.

### Can an FAQ page rank on its own?

Rarely as a page, often as passages. A question phrased the way people ask it, with a two to four sentence answer under it, is the shape featured snippets and AI assistants lift, and it can be lifted from anywhere on your site.

### Where do I find the questions if I have no support inbox yet?

The People also ask questions on your main query, the questions in the communities where your buyers are, and the ones you answer in demos. Write down every question anyone asks you about the product for two weeks; the list writes itself.

## Read next

- [FAQ schema in 2026: valid, readable by assistants, no rich result](https://porteur.ai/guides/faq-schema): FAQ rich results are gone for most sites, but valid FAQ schema still helps assistants read your answers. Here is the shape, rules and tests.
- [People also ask: turning Google’s questions into sections](https://porteur.ai/guides/people-also-ask): See what People also ask is, where questions come from, how to collect them, write two-sentence answers, add FAQ markup, and track results.
- [The SaaS pricing page: what it must say for the buyer and for search](https://porteur.ai/guides/saas-pricing-page): Your SaaS pricing page must sell to buyers and rank for pricing searches. Here is what to include, how to mark it up, and what to track.
- [How to write for featured snippets and AI answers](https://porteur.ai/guides/how-to-write-for-featured-snippets): Three snippet shapes, the patterns that win them, and why the same patterns get a page quoted by assistants. No markup required.
- [Trust signals on a product site: what a stranger checks before paying](https://porteur.ai/guides/trust-signals-on-a-product-site): What a stranger checks in the first minute, the pages that answer each doubt, how to show proof without noise, and a checklist you can ship today.
- [Featured snippet](https://porteur.ai/glossary/featured-snippet): What a featured snippet is, how to earn and measure it, and how AI Overviews change clicks and priorities for a small site.
- [Writing titles that get the click, without a tease](https://porteur.ai/guides/writing-titles-that-get-clicked): The title is a promise, not a tease. The words people search near the front, sixty characters, and ten before-and-after examples that show the difference.

Paste your URL and the free check reads the questions the search results ask around your product, and which of your pages answer them, in about thirty seconds. Free check: https://porteur.ai/