An FAQ built for AI retrieval is not an FAQ built for humans. The difference is structure. A prose answer makes an engine work: it has to parse, infer and assemble. A question with a short, self-contained answer can be lifted as it stands. FAQPage schema is the markup that labels those pairs, and most independent business sites don't use it.
ChatGPT, Perplexity and Google AI Overviews all build answers from retrieved text. When your answer is already formed, quotable and about one thing, it is the easiest text on the page to use accurately. The engine may still paraphrase it, but it has far less to get wrong.
Why Prose Loses to Structure
Take a paragraph answering "How much is an eye exam?":
"Exam pricing depends on the type of exam and whether you're coming in for glasses or contact lenses, and contact lens fittings involve extra measurements, though many insurance plans cover part of the cost, so it's best to check with us."
An engine reading this has to work out which exam is meant, whether a price is given at all, and what the insurance clause applies to. It might cite you. It might blend you with three other practices. It might skip you because there is no clean sentence to quote.
The same content as separate questions and answers, marked up:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How much is a routine eye exam?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A routine eye exam at Example Optical costs $[price]. A contact lens fitting is a separate $[price]."
}
},
{
"@type": "Question",
"name": "Do you take my insurance?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We accept [plan names]. Call with your member ID and we will confirm coverage before your visit."
}
}
]
}
Now the engine has a named question, a pre-formed answer, and no doubt about which sentence answers what.
One Answer Per Question
The most common mistake is nesting several questions into one answer block: "What does it cost? How long does it take? Will insurance cover it?" Don't. One question, one answer, one fact per block.
If the real answer is compound, split it:
- "How much is a routine eye exam?"
- "How long does an eye exam take?"
- "Do you take my insurance?"
Each gets its own entry and can be retrieved on its own. An engine pulls the one that matches the prompt.
The Five Questions Every Service Page Should Answer
Most businesses answer the questions they like answering, not the ones prospects ask. Run each of your main services through five frames:
- Cost: "How much does [service] cost?"
- Access: "Do I need [an appointment, a referral, experience] to [use the service]?"
- Location: "Where is [business name] in [neighborhood]?"
- Differentiation: "How is [your service] different from [the alternative]?"
- Process: "What happens at a [service] appointment?"
Each frame is a prompt pattern people already type into ChatGPT. Most sites have these answers somewhere already, buried in service pages, an about page or footer copy. Surface them as visible questions, then mark them up.
Answer Length and Phrasing
Keep answers between one and four sentences. A sentence here is one complete statement, not a clause wrapped in qualifiers.
"A routine eye exam takes about [length]." That is quotable.
"A routine eye exam, which can include a refraction and a health check depending on your history (and dilation if the doctor recommends it), usually takes [length], though it can run longer." That is one sentence with too many qualifiers. An engine will trim it or hedge it.
The rule: if you would put it in parentheses, delete it or give it its own question.
Write the question the way a person asks it. "What is the cost of a comprehensive ophthalmic examination?" is a label. "How much is an eye exam?" is a question. Specific beats general, too: "What services do you offer?" is weak, while "Do you do same-day glasses?" matches a real prompt.
Placement Rules
- Visible. Only mark up questions and answers that appear on the page. Google's FAQPage guidelines require the content to be visible, and markup describing hidden text is a mismatch any crawler can find.
- Exact match. The question and answer in the markup should match the visible text word for word. No paraphrase.
- Per service page. Put each FAQ block on the page it belongs to. Questions about contact lenses go on the contact lens page, not a catch-all FAQ route. A dedicated FAQ page is fine too, but don't make it your only FAQ layer.
- After the persuasion. Put the FAQ near the bottom of the page, once the prose has done its job.
- Five to ten questions per page. Past that, the block stops being specific to the page.
What FAQ Markup Does and Doesn't Do in Google
Be clear about what you are getting. Since August 2023, Google shows FAQ rich results only for well-known, authoritative government and health websites (Google Search Central). For most local businesses, FAQPage markup will not produce an expandable FAQ in search results.
That is not the reason to add it. The reason is parsing: the markup tells any system reading the page which text is a question and which text is its answer.
Nostrand Optical in Crown Heights launched with LocalBusiness, MedicalBusiness and FAQPage markup, and four rich-result types validated in Google's Rich Results Test on launch day. In a spot check on 8 Sep 2026, ChatGPT cited Nostrand second of four for "optometrist in Crown Heights Brooklyn that takes Medicaid". The same day, ChatGPT did not cite Nostrand for "best optometrist in Brooklyn", and Gemini did not cite it for the Medicaid prompt. The full record, misses included, is on the evidence page. Markup made the answers easy to read. It did not make Nostrand the answer everywhere.
Testing Your Markup
Use Google's Rich Results Test to check that the markup parses without errors, and the Schema Markup Validator to check it against schema.org. A clean result confirms the markup is well formed. It does not guarantee retrieval or citation. Broken markup, though, gives an engine nothing to use, so start there. For the full check, see how to audit your structured data.
The Maintenance Rule
FAQ answers go stale. If a price changes, update the answer the same day. If you stop offering a service, delete the question. A marked-up answer that contradicts your Google Business Profile hours or your homepage is the kind of inconsistency that makes an engine trust both sources less.
Treat the FAQ as data you maintain, not copy you wrote once.
Where to Start
Pick one service page. Write the five questions from the frames above in the words your customers use. Answer each in one to four sentences, put them on the page, mark them up, and test. Then ask ChatGPT and Perplexity those questions yourself and note which sources come back. That tells you more about your category than any tool.