FAQ Pages and Schema for AI: Writing Q&A That Assistants Quote
When someone asks ChatGPT, Claude, or Perplexity a question, the assistant is looking for a clear, quotable answer to that exact question. A well-written FAQ is almost perfectly shaped for this: it pairs a real question with a direct answer. This guide shows how to write Q&A content AI will quote — and gives you the honest, current picture on FAQ schema.
Why Q&A content is so quotable
People ask assistants questions in plain language: “how much does X cost,” “is X safe for Y,” “how do I cancel X.” If your page already contains that question and answers it directly, you’ve handed the AI exactly what it needs. Three things make Q&A work:
- Use the real question. Phrase it the way a customer would type it, not in marketing language.
- Answer it directly in the first sentence. Lead with the answer, then add detail. AI (and people) often quote just the first line.
- Keep each answer self-contained. It should make sense even if it’s the only sentence quoted.
How to structure it on the page
- Put each question in a heading (an
<h2>or<h3>), with the answer in the paragraph right below it. That structure alone — question as heading, answer as text — is what helps a machine pair them. → heading structure · semantic HTML - Keep the real answer in the HTML, not hidden inside a JavaScript accordion that only loads on click. A visible-in-source
<details>/<summary>is fine; a JS-only widget can hide the text from crawlers. - Write genuinely useful answers. Don’t stuff in dozens of fake questions — a handful of real ones beats a wall of filler.
The honest truth about FAQ schema in 2026
You may have read that you should add FAQPage structured data (JSON-LD) to get rich results in Google. That advice is now out of date: Google removed FAQ rich results from Search entirely (the rollout finished in May 2026, and FAQ reporting is leaving Search Console). So adding FAQ schema will not give you a special search appearance anymore.
What’s still true:
- FAQPage is still a valid Schema.org type, and machines can still parse it to understand your Q&A. It just no longer earns a visual feature in Google.
- So treat it as an optional, low-priority bonus — not a growth lever. The real win is the content and structure above, which works whether or not you add the markup.
- If you already have FAQ schema, there’s no urgency to remove it; unused structured data doesn’t hurt. → structured data
The honest part
The durable advantage isn’t markup — it’s writing answers that are genuinely the best, clearest response to a real question. Schema can label your content, but it can’t make a vague answer quotable. Get the words right first; add markup only if it’s cheap.
How to check
Open “View Source” and confirm your questions and answers are in the HTML (not only in a JS accordion). Read each answer’s first sentence on its own — does it stand alone? Then ask an assistant your own top question and see whether it could quote you. Or run your URL through a free AI-visibility check to confirm the page is readable.
The bottom line
Clear Q&A is some of the most quotable content you can write for AI: real questions, answer-first, kept in the HTML. FAQ schema is now just an optional label (Google dropped the rich result in 2026), so spend your effort on the content. Start with the GEO overview and structured data, and see how to appear in ChatGPT for the bigger picture.