Short answer
A good FAQ page uses the questions customers really ask, in their own words, as headings, and every answer begins with the answer. Questions come from sales, support, site search and Search Console; each answer has an owner and a check date. Google has not shown the FAQ rich result since 7 May 2026.
Picture this: a small air-conditioning maintenance firm has a “Frequently asked questions” page with three questions on it: “When was your company founded?”, “Why should we choose you?” and “What is your quality policy?” The customers who ring in keep asking the same thing: “Once I’ve booked, when does the technician arrive, and how long does a service take?” The page is there, but the customer’s question is not on it. How to write an FAQ (frequently asked questions) page starts with collecting the questions in the customer’s words, not the firm’s. This article covers where to collect the questions, which ones belong on the FAQ and which on their own page, and how to write the question and the answer. It also covers how to build the show-and-hide pattern and what Google says today about the FAQ rich result. Every example here is for this invented, generic air-conditioning firm; none of it comes from a real customer or real data.
1. Collect the questions from four places
An FAQ’s list of questions is not made up at a desk; it is collected. The table below says what to look at in each source. The first three rows are our suggestion; the fourth rests on how Google’s Search Console help page describes the Performance report.
| Source | Where to look | What to look for |
|---|---|---|
| Sales conversations | Phone notes, emails before a quote | Things asked again and again before you can quote |
| Support messages | Email, messaging, forms | Answers you keep writing out afresh |
| Site search | The terms people type, if your site has a search box | Searches that return nothing |
| Search Console | Performance report, Queries | Queries written as questions |
According to Google’s help page, the Performance report shows the search queries most likely to show your site, and the “Queries” dimension groups the data by the query users typed. The same page says results depend on the searcher’s time, place, device and recent history, so even when a query is in your list, you might not see your site in the results if you run the same query yourself. To read what is behind a query, use the method in what search intent is and how to find it.
Put every question into one table: as the customer wrote it, how often it comes up and where it is answered today. That method is our suggestion. Ask the people in sales and support to pull a first list from the correspondence they already have; they know the real wording best.
2. Decide what belongs on the FAQ and what belongs on its own page
Not every question goes on the FAQ. The figure reaches three outcomes with two questions.
If the answer is the subject of a single page, it should stay on that page. “What does the service package include?” belongs to the service page; one line on the FAQ and a link to that page is enough. Short questions that do not belong to any single page (how to change an appointment, which payment methods are accepted, opening hours) go on the FAQ. Topics that need a long explanation become a separate guide, and the FAQ links to it. “Two or three sentences” is our suggestion; do not read it as a rule. For how to build the page copy itself, see how to write website copy.
3. Write the question as the customer says it
The heading should carry the words the customer uses on the phone. “How does the appointment process work?” becomes “Once I’ve booked, when does the technician arrive?”; “Information about service duration” becomes “How long does a service take?” Write the question as a full sentence that asks one thing; if you squeeze two questions into one heading, the first sentence of the answer cannot reach both.
If the same question arrives in different words, make the most common form the heading and use the other in the answer. Questions the customer never asks, such as “Why should we choose you?”, turn an FAQ into a marketing page. Someone who does not ask will not look for that heading either. That is our suggestion.
4. Write answers whose first sentence is the answer
Readers often open the page not to read it through but to find a single answer. So the first sentence of each answer should answer the question, with the detail after it.
- Weak: “Our team, which puts customer satisfaction first, will schedule your appointment as soon as possible.”
- Strong: “The technician arrives within the time slot you chose and calls you before setting off.”
In this invented example the second half of the sentence completes the first, but the first half answers the question even when read alone. Keep the length of the answer to what the question needs; we give no number. If an answer has to point to another answer, put the link inside the sentence. We covered the same principle for page copy in general in how to write SEO-friendly content.
5. Group, order, and decide between one page and several
Build the headings around the customer’s steps: “Booking”, “Service day”, “Payment”, “After the service”. Within a group, put the most frequent question first; you read the frequency from the table in step 1. Choose the group names in the customer’s words too; nobody looks for their own question under a heading like “Operational processes”.
For one page or several, our suggestion is this: if there are few questions and the topics are close, one page is enough. If one topic’s questions multiply and answers that belong to that topic’s own page start to dominate, move them under the relevant service page and leave only the general ones on the FAQ.
6. Build the show-and-hide pattern so it is accessible
Questions that open on a click are a common choice. W3C’s WAI-ARIA Authoring Practices Guide calls this pattern a “disclosure”: a widget that lets content be collapsed or expanded, with two parts, a button and the section of content whose visibility the button controls. According to the guide, Enter and Space on the focused button toggle the content; the button has the role “button”, and aria-expanded is true while the content is visible and false while it is hidden. The same guide lists an example titled “Disclosure (Show/Hide) of Answers to Frequently Asked Questions”.
You do not have to write that behaviour yourself. According to MDN, the HTML <details> element creates a disclosure widget whose information is visible only when it is open, and it needs a <summary> element to provide the label. The open attribute starts the section open; <details> elements that share the same name are grouped, and only one of them stays open at a time.
<details>
<summary>Once I’ve booked, when does the technician arrive?</summary>
<p>The technician arrives within the time slot you chose and calls you before setting off.</p>
</details>
Two suggestions here are ours: write the question as a full sentence inside <summary>, and use name grouping only where you really want a single choice, so that readers can compare two answers side by side. If there are few questions, leaving the answers open is also reasonable.
7. Give every answer an owner and a check date
A correct answer becomes wrong when the opening hours or a booking rule change. To prevent that, keep three things for each answer, in a record that is not shown on the page: the person responsible for it, the date it was last checked and the date of the next check. Let the owner be the person who really knows the matter: the booking coordinator for opening hours, the head of the technician team for what a service covers. Choose the interval to suit how fast your business changes; our suggestion is to look at least every three months.
The date shown on the page is a separate matter. One of the self-assessment questions in Google’s helpful-content guidance is this: “Are you changing the date of pages to make them seem fresh when the content has not substantially changed?” The guidance says that answering yes to some or all of those questions is a warning sign that you should re-evaluate how you are creating content. Do not move the publication date just because you checked an answer and left it alone; change the date only when an answer really changes. If you later plan to make the FAQ the source for an AI assistant, the same record would, in our reading, also be the basis of the documents the assistant reads; see how to set up an AI assistant (chatbot).
Where FAQ structured data stands today
Many older guides still recommend adding FAQ markup to an FAQ page. Google Search Central’s documentation updates page has two entries on this:
- 8 May 2026: a deprecation notice was added to the FAQ rich result documentation. The stated reason: the feature will no longer appear in Google Search starting 7 May 2026.
- 15 June 2026: the FAQ rich result documentation was removed. The stated reason: the feature is no longer shown in Google Search results, and Google says it announced this in its May 2026 entry.
We did not read a statement in these two entries saying the markup is harmful or must be removed. Our interpretation: write the FAQ page for the reader; we cover the rest of the markup in what schema (structured data) is and how to add it.
Common mistakes
- Writing the same answer in three different wordings on three pages. One day one is updated, two stay old, and the customer reads two conflicting answers. Keep the answer in one place and link to it from the other pages.
- Leaving no way out when the answer is missing. If a customer cannot find what they need, they should know where to write. Put a sentence such as “Didn’t find the answer to your question?” and a way to get in touch at the end of the page; new questions that arrive go into the table from step 1 on the next round.
- Writing a referral instead of an answer. An answer that ends “Contact us for information” brings back the burden an FAQ is there to remove: answering the same question again and again. If the answer depends on the person or the case, say what it depends on; for example: “The duration depends on the number and location of the units and is confirmed after a survey.”
Common questions
How many questions should an FAQ page have?
We do not recommend a number. Our suggestion is to write as many as your collection table shows repeating: a question asked only once has no reason to be on the FAQ. If the list grows, group it and, if needed, split it across pages as in step 5.
Should I add FAQ markup to my FAQ page?
According to Google’s changelog, the FAQ rich result has not appeared in Search since 7 May 2026 and its documentation was removed in June 2026. There is no reason to add this markup only for a rich result; that is our interpretation. These entries contain no statement saying you must delete existing markup.
Should answers collapse, or always be open?
For show-and-hide there is W3C’s pattern and the <details> element on MDN; no separate pattern is needed to write the answers out in the open. Our suggestion: if there are few questions and the answers are short, write them all open; if there are many, close them with <details> so readers can scan the headings.
One thing you can do today
Open your inbox and find a question that has been asked in the same words at least twice in the last month. Write the question as the customer wrote it on one line and the first sentence of the answer on the line below. With those two lines in hand, the first real entry of your FAQ is ready. If you would rather not write it yourself, in our content service every text is read by an editor other than its writer.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 14 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.