An FAQ section works for AI systems when each question is one a customer really asks and each answer stands alone in two to four sentences. The bottom line: write the questions from real customer language, answer directly and specifically, keep each answer self contained, and treat schema markup as optional, because the visible question and answer text is what a system reads.
New to the term? What is answer engine optimization covers the basics.
What an FAQ section is good for
Semrush's analysis of ChatGPT usage found that between 65 and 85 percent of prompts do not match any traditional search keyword, and that the average prompt is 23 words long. People ask full, situational questions, and an FAQ that mirrors those questions creates a passage that matches them. Google introduced FAQ rich results in 2019, restricted them to well known government and health sites in August 2023, and stopped showing them on May 7, 2026, so the search feature is gone, but the question and answer format still gives systems a clean unit to extract. Microsoft's Fabrice Canel said in March 2025 that schema markup helps its language models understand content, and there is no published study showing FAQ markup itself raises citations.
How to choose the questions
- Start with what customers actually ask. Sales call notes, support email, chat transcripts, and the questions asked before booking.
- Add the questions AI answers about you. Ask an assistant your category question and note the follow ups it suggests.
- Keep questions specific. "How long does a crown take at a first visit" is better than "Tell me about crowns."
- Include the objection questions. Price, timing, risk, and what happens if something goes wrong.
- Limit each page to the questions relevant to it. Five to eight strong ones beat thirty generic ones.
How to write the answers
| Do | Avoid |
|---|---|
| Answer in the first sentence | Opening with 'Great question' or a warm up |
| Two to four sentences, self contained | A single word, or a wall of text |
| State specifics: numbers, ranges, conditions | Vague reassurance |
| Name the business and place where relevant | Pronouns that only make sense in context |
| Say what you do not do or cannot promise | Guarantees you cannot back |
| Keep the answer consistent with the rest of the page | Contradicting your pricing or policy pages |
Example: a dental practice (invented figures, for illustration only)
Do you take new patients with no insurance? Yes. New patients without insurance pay a flat $95 for a first exam and x rays, and we offer a membership plan that covers two cleanings a year for $29 a month. We accept most major PPO plans and can check your benefits before your visit.
Where and how to place it
- Put each question in a heading, so it is a clear boundary.
- Place the FAQ where it is relevant, on the service page it concerns, not only on a separate FAQ page.
- If you add FAQPage markup, generate it from the same text and keep it identical. Google says you do not need to remove existing markup.
- Keep it in the raw HTML. Accordions that load content only on click may not put the answer in the response.
Keeping it current
An FAQ with an outdated price or policy is worse than none, because it gives an assistant a wrong fact to repeat. Review the answers whenever prices, hours, or policies change, and at least each quarter.
Questions people ask
How many questions should an FAQ section have?
Five to eight strong questions per page, chosen from real customer language, work better than many generic ones.
Does FAQ schema help AI citations?
No published study shows it does. Microsoft says schema helps its language models understand content, but the visible question and answer text does the main work.
How long should an FAQ answer be?
Two to four sentences that answer directly and make sense on their own.
Where should an FAQ go on a page?
On the page it concerns, with each question in a heading and the answer in plain text in the raw HTML.