Writing guide
How to write an FAQ page
Most FAQ pages are written backwards: someone in marketing invents ten questions the company wishes people asked — "What makes Acme different?" — and answers each with a paragraph of positioning. Real FAQ pages start in the support inbox. The questions customers actually ask are blunter, more specific, and less flattering: does it work with X, what happens to my data if I cancel, why was I charged twice. A page that answers those honestly does the work of a support agent, around the clock.
The format has also become disproportionately valuable in search. An FAQ page is a set of question-answer pairs — exactly the shape search engines and AI answer engines are built to extract. Mark the pairs up with FAQPage structured data and each becomes machine-readable; write each answer so its first sentence stands alone and it becomes quotable. When someone asks an AI assistant whether your product does X, a well-built FAQ page is often the exact text the answer is assembled from.
This guide covers the full craft: where to source questions so the page reflects reality, how to group and order them, the direct-answer pattern that makes each entry work in search and on the page, and the schema markup that makes the whole thing extractable.
What it is
An FAQ page is a structured collection of the questions customers actually ask — sourced from support tickets, sales calls, and search data — each answered directly in a few sentences. Done well, it deflects repetitive support volume, removes purchase objections, and provides machine-readable question-answer pairs that search engines and AI assistants can quote.
When to use it
Build an FAQ page once the same questions recur — a useful threshold is any question support has answered three or more times. The format fits products with real pre-purchase doubts: pricing mechanics, integrations, security, cancellation terms. Skip it when the honest answer is a product page (do not bury your pricing explanation in an FAQ), when you have no recurring questions yet (invented ones read as padding), and when documentation is the right depth — an FAQ answer is 50-100 words, not a tutorial.
The structure that works
Question sourcing
The page is only as useful as its questions are real. Sourcing is what separates an FAQ from a marketing page wearing a question format.
- Export the last 90 days of support tickets and tag recurring questions — anything asked three or more times earns a slot.
- Mine sales and onboarding calls for pre-purchase doubts; these are the questions blocking revenue, not just tickets.
- Check your site-search logs and the People Also Ask box for your main keywords — both are verbatim question language.
- Keep the customer’s phrasing. "Can I export my data?" outperforms "What are Acme’s data portability capabilities?" in search and on the page.
Grouping and order
Past eight questions, a flat list stops being scannable. Structure decides whether a visitor finds their question in five seconds or leaves.
- Group by topic in journey order: getting started, pricing and billing, security and data, troubleshooting.
- Order questions within each group by frequency — the most-asked question sits first.
- Add jump links at the top once the page passes ten questions.
- Keep one page until it clearly overloads; a single strong FAQ beats five thin ones.
The answer pattern
Every answer follows the same shape: the direct answer in the first sentence, the essential qualification in the next two or three, a link for depth. That shape is what makes answers quotable by humans and machines alike.
- If the question is yes/no, the first word of the answer is Yes or No. If it is a number, lead with the number.
- Keep answers between 50 and 100 words; if the honest answer needs 300, write a doc and link it.
- One link per answer, maximum — an FAQ is an exit ramp, not a hub.
- Write in your support team’s voice, not your homepage’s. Plain beats polished here.
FAQPage schema
Structured data turns your visible question-answer pairs into machine-readable ones. Google restricted the visible rich result to a small set of authoritative sites in 2023, but the markup still helps engines and AI assistants parse and quote the page.
- Add FAQPage JSON-LD listing every question and answer that appears on the page.
- The markup must match the visible text exactly — never mark up content that is not rendered.
- Generate the JSON-LD from the same source that renders the page, so markup and text cannot drift apart.
The escalation path
Some visitors will not find their question. Where they go next decides whether the page ends in a ticket, a sale, or a bounce.
- End the page with a clear route to a human — contact form, chat, or support email — with a stated response time.
- Add a "still stuck?" link at the end of each group, not only at the page bottom.
- Log the questions that arrive through that route — they are next quarter’s new entries.
Step by step
- 01
Pull questions from the places customers already ask them
Start with a 90-day export from your support tool and tag every question that appears more than twice. Add the questions sales hears on calls — the ones that stall deals — and whatever visitors type into your site search. These three sources produce a list no brainstorm will.
Record the phrasing verbatim. Customers ask "will I lose my data if I downgrade", not "what is your data retention policy" — and search engines match the phrasing people actually use, not your internal vocabulary.
- 02
Cut the list to questions that earn their slot
Apply a frequency threshold: asked three or more times, it stays; asked once, it goes to a parking lot for next quarter. Merge duplicates and keep the most common wording as the visible question.
Delete every planted question. "What makes Acme different?" was asked by nobody; its presence tells readers the rest of the page may be fiction too.
- 03
Write the direct answer before anything else
For each question, write the one-sentence answer first — the sentence a support agent would say on the phone. If the question is yes/no, start with Yes or No. If it is a number, lead with the number: "Plans start at $19 per month."
Then add only the qualification the reader predictably needs next: the exception, the timeline, the fee. Two to four sentences total. Resist the urge to continue — length is where FAQ answers go to die.
- 04
Handle the uncomfortable questions honestly
The questions you are tempted to omit — refunds, downtime, lock-in, what happens to data on cancellation — do the most pre-purchase work. An evasive answer reads instantly as evasive and costs more trust than the honest one would.
If the honest answer is unflattering, state it and give the mitigation: "Annual plans are non-refundable after 30 days. If you are unsure, start monthly — you can switch to annual anytime and keep the discount."
- 05
Group, order, and add navigation
Sort questions into three to six topic groups in journey order, then order by frequency inside each group. The page should read like triage: the newest visitor’s most common concern comes first.
Once the page passes ten questions, add jump links at the top. Past thirty, split by audience or topic into separate pages — but not before.
- 06
Add FAQPage structured data
Generate JSON-LD containing every visible question-answer pair. Most frameworks and CMS SEO plugins can emit it from the same content that renders the page — use that path so the markup never disagrees with the text.
Validate with Google’s Rich Results Test. The visible dropdown result is now restricted to a small set of sites, but correctly parsed question-answer pairs still feed AI answers and search understanding.
- 07
Wire the escalation path
Close the page — and ideally each section — with the route to a human, including a response-time promise you actually keep. The FAQ’s job is deflecting the repetitive 80 percent, not hiding the door.
Instrument it. A one-question "did this answer help?" widget or a logged contact form tells you which answers fail, which is the data the next revision runs on.
- 08
Review quarterly against new tickets
Every quarter, rerun the ticket export. Add questions that newly crossed the threshold, retire ones nobody asks anymore, and reverify every number on the page: prices, limits, timelines.
A stale FAQ answer generates the exact ticket it was meant to prevent — filed by a customer who is now also annoyed that the page misled them.
Before and after: what good looks like
Before
Q: Can I change or cancel my plan? — At Acme, customer flexibility is one of our core values. We understand that business needs evolve, and we want to be a partner in your growth journey. Our team has designed a range of flexible plans to accommodate organizations of every size, and our friendly support staff is always standing by to help you find the perfect fit for your changing needs. Please don’t hesitate to reach out to discuss your options.
After
Q: Can I change or cancel my plan? — Yes. You can upgrade, downgrade, or cancel anytime from Settings → Billing, with no cancellation fee. Upgrades apply immediately and we prorate the difference. Downgrades and cancellations take effect at the end of the current billing period, and you keep full access until then. Annual plans are refundable for unused full months within the first 30 days. If you pay by invoice rather than card, email billing@acme.com and we’ll process the change within one business day.
The before answers nothing: after 80 words the reader still does not know whether cancelling is possible, instant, or free — so they file a ticket, which is the outcome the page existed to prevent. The after opens with Yes, then covers the three predictable follow-ups (fees, timing, the invoice edge case) in support-agent language. It is also the version an AI answer engine can quote verbatim, because the first sentence stands alone.
Mistakes that sink an FAQ page
| Mistake | The fix |
|---|---|
| Inventing questions nobody asked | Source every question from tickets, calls, or search logs. If you cannot name where a question came from, cut it. |
| Burying the answer under preamble | The first sentence is the answer — Yes, No, or the number. Qualifications come after, never before. |
| Using the FAQ to dodge uncomfortable topics | Answer refunds, lock-in, and cancellation plainly, with the mitigation. Evasion is visible and reads as a warning. |
| One wall of thirty unsorted questions | Group by topic, order by frequency within each group, add jump links past ten questions. |
| Schema that does not match the visible page | Generate JSON-LD from the same content that renders. Marked-up text that is not on the page violates Google’s guidelines. |
| Publishing once and never returning | Rerun the ticket export quarterly. Add what crossed the threshold, retire what nobody asks, reverify every price and limit. |
Pre-publish checklist
- Every question traces to a real source — a ticket, a call, or a search log.
- Questions use the customer’s wording, not internal jargon.
- The first sentence of every answer is the answer.
- Yes/no questions open with Yes or No; number questions open with the number.
- Answers run 50-100 words; anything deeper links out to one doc.
- Uncomfortable questions — refunds, cancellation, data — are answered plainly.
- Questions are grouped by topic and ordered by frequency within each group.
- Jump links exist if the page has more than ten questions.
- FAQPage JSON-LD matches the visible text exactly and validates.
- Every price, limit, and timeline on the page is verified current.
- The page ends with a route to a human and a response-time promise.
- A quarterly review is scheduled with a named owner.
Free tools for this work
Check your FAQ page before it ships.
Frequently asked questions
- How many questions should an FAQ page have?
- 8 to 15 for most product FAQ pages — enough to cover the real recurring questions without becoming a wall. Support hubs can carry 25 to 30 if grouped with jump links. Below 5 real questions, fold the answers into the page they support instead of building a separate FAQ.
- How long should each FAQ answer be?
- 50 to 100 words. The first sentence carries the direct answer, the next two or three carry the qualification the reader predictably needs, and anything longer moves to a linked doc. If most answers on your page pass 150 words, the content belongs in documentation.
- Is FAQ schema still worth adding?
- Yes. Since August 2023 Google shows the FAQ rich result only for a small set of authoritative sites, so most pages will not get the dropdown — but FAQPage markup still hands engines and AI assistants clean question-answer pairs to parse and quote, for roughly 15 minutes of setup.
- How often should an FAQ page be updated?
- Quarterly, plus immediately when any price, limit, or policy it mentions changes. A 90-day cycle matches the support-ticket export you should source new questions from; a stale answer generates the exact ticket it was built to prevent.
Free download
The Pre-Publish Checklist
This guide covers one format. The checklist covers every article. 47 checks WriteZu runs before an article ships — as a checklist you can run by hand.
No spam. The checklist, then only what's worth knowing.
Or let WriteZu handle the writing for you
It follows this exact structure — researched, drafted, scored against quality gates, and published to your CMS — while you approve from your inbox.
Start free