An FAQ page is the single best source you can give a website chatbot, because it is already written in the format people ask in. It is also, on most sites, the worst-written page: a dozen vague questions, answers that say "it depends" and link elsewhere, and nothing updated since launch.
Fixing it helps three audiences at once: your chatbot, ordinary search, and the AI assistants that now answer questions by quoting pages. Here is how to write one that works for all three.
Start with real questions
Do not brainstorm questions. Collect them. Your support inbox, your chatbot's unanswered-questions list, your sales calls, the search box on your site. Write down the exact phrasing customers use, not the tidy version your team would write.
Then group them. You will get a short list of clusters, and the FAQ should have one question per cluster in the words customers actually use. "Can I send it back if it doesn't fit?" belongs on the page, not "What is your return policy?", because the first is what people type.
One question, one complete answer
Each answer should stand alone. Someone landing on it from a search result, or a chatbot retrieving just that passage, should get the full answer without clicking anywhere.
Weak: "Returns are accepted within our standard window. See our returns policy for details."
Complete: "You can return most items within 30 days of delivery for a full refund. Items must be unused and in their original packaging. Sale items can be exchanged but not refunded. Start a return from your account page or email us at the address below."
The second answer is longer, and that is the point. A chatbot answering from the first one has nothing to say; from the second it can answer five different phrasings correctly.
Put the facts in the sentence
Numbers, names, and conditions should appear in the text of the answer, not in a table elsewhere or an image. "30 days", "unused", "original packaging", "sale items exchange only" are all quotable facts. A chatbot and an AI assistant can both lift them. A screenshot of a policy table is invisible to both.
Write the exceptions
Most FAQ answers describe the happy path and stop. The questions people actually ask are about the exceptions: sale items, gift cards, international orders, damaged goods. Write the exception into the answer or as its own question. This is where confident wrong answers come from when the exception is missing.
Keep one topic per page section
Group related questions under a heading: Shipping, Returns, Payments, Account. A chatbot retrieving a passage benefits from the surrounding context, and a reader skimming finds the section faster. Do not interleave shipping and billing questions in one long list.
Mark it up as FAQ structured data
FAQPage schema tells search engines that the page is a list of questions and answers, and can produce rich results. Most CMS platforms have a plugin or block for it; on a custom site it is a small JSON-LD script. The FAQ sections on this site's landing pages are marked up this way. The GEO guide covers why this also helps with AI assistants.
Date it and maintain it
Put a visible "last updated" date on the page and mean it. When a policy changes, the FAQ changes the same day, and if a chatbot is trained on it, the page is re-added the same day. An FAQ that contradicts the returns policy is the fastest way to create a dispute. The training guide covers the re-adding routine.
Test it as a customer
Take ten real customer questions, phrased as they were sent, and check the page answers each one fully in a single passage. Then feed the page to your chatbot and ask the same ten. Where the chatbot's answer is thin, the page is thin. Fix the page, not the chatbot.
A template for each answer
- The direct answer in the first sentence, with the key fact.
- The conditions that change it.
- What to do next, with a link or a contact.
- Nothing else. No marketing, no "we're proud to offer".
Frequently asked questions
How many questions should an FAQ have? As many as you have real question clusters, usually fifteen to forty. Fewer than ten means you have not collected enough; more than sixty means several should be their own pages.
Should the FAQ replace policy pages? No. Policy pages are the authoritative full text; the FAQ is the plain-language answer with the same facts. Feed both to a chatbot; they reinforce each other.
Can I generate the FAQ with AI? Use it to draft from your real questions and your real policies, then check every fact. An FAQ that confidently states a policy you do not have is worse than no FAQ, and a chatbot trained on it will repeat the error. The small business guide shows how the FAQ becomes the chatbot's first source.