Do your FAQ pages give AI tools a clean question-and-answer structure?
Confirms your FAQ pages publish structured questions and accepted answers AI can lift directly into responses.
What this signal tests
We check whether your FAQ pages publish FAQPage structured data with each question and its accepted answer marked up explicitly. The markup includes the question text and the full answer text for every entry on the page, so AI tools can extract clean question-answer pairs without trying to parse your visible HTML.
Why it matters for your visibility in AI
Google sunset the FAQ rich result for most sites in mid-2026, but the underlying markup is more valuable than ever to AI tools. ChatGPT, Perplexity, and Google's AI Overviews actively extract question-answer pairs from FAQPage markup to populate direct answers. Your FAQs become a high-leverage source of citable content, because each entry is a self-contained answer the AI can quote. Without the markup, your FAQ content still exists but it competes with thousands of less structured pages for the same answer slot, and it loses. The point of FAQPage markup is not the visual rich result Google has retired; it is being preferred as a clean, machine-readable source over equivalent prose. The ROI on adding FAQPage markup to a well-written FAQ has actually increased since the rich result was deprecated.
Pass criteria at a glance
| Criterion | Passes when |
|---|---|
| >=1 valid Question/acceptedAnswer pair on FAQ pages. |
How we test it
We crawl your FAQ pages (typically at paths like /faq, /faqs, or under support sections) and look for FAQPage structured data. We confirm the mainEntity is an array of Question objects, each with a name (the question) and an acceptedAnswer (the answer text). At least one valid question and answer must be present. Empty answers or missing question text fails the signal.
Show technical detection method
@type FAQPage with mainEntity[] of Question with name and acceptedAnswer.text.
If your site fails: how to fix it
- Identify your FAQ pages. If you have multiple, including product-specific FAQs and general support FAQs, each needs the markup.
- Update your FAQ template to emit FAQPage JSON-LD with mainEntity as an array. Each item should be @type Question with name (the question text) and acceptedAnswer of @type Answer with text (the answer text).
- Make sure the markup matches what users see. Adding hidden questions in the JSON-LD that do not appear visibly is a violation of Google's structured data policies and will be penalised.
- Keep answers self-contained. Each answer should make sense without reading the rest of the FAQ. This is also good writing practice; the markup just rewards it explicitly.
- If your FAQs are user-submitted Q&A rather than editorial FAQs, use QAPage instead. The two schemas are deliberately separate.
- Validate the URL in Google's Rich Results Test under the FAQ test type to catch any malformed entries.
Quick facts
| Maturity | ESTABLISHED |
|---|---|
| Weight | medium |
| Category | Structured Data |
Primary sources
Related signals
Frequently asked questions
Should I add FAQPage markup to product pages or article pages?
Only if the page is genuinely a FAQ. Embedding a small FAQ section at the bottom of a product page with FAQPage markup is technically allowed but increasingly frowned upon. Reserve FAQPage for pages whose primary purpose is FAQ content; use a dedicated FAQ URL where possible.
How long should the answers be?
Long enough to be useful as a self-contained answer, short enough that an AI tool can quote them in a single citation. Roughly 30 to 80 words per answer is a good range. Multi-paragraph answers are allowed but reduce the chance of being lifted intact into an AI response.
Is FAQPage still worth doing now that Google removed the rich result?
Yes, more than ever. The rich result was a visual snippet in classic search; AI tools still use the same markup as a primary source for direct answers. The ROI shifted from search snippets to AI citations, and the latter is where discovery is growing fastest.
Can I have more than one FAQPage per site?
Yes. Each FAQ URL should have its own FAQPage block. A general FAQ, a billing FAQ, and a product-specific FAQ are three separate FAQPages with three separate markups. Do not try to combine them into a single mega-FAQ; smaller, topic-focused FAQs perform better in AI extraction.
Run your own scan
Run a free scan and see how your site grades across all 155 AI-readiness signals.