Do your community Q&A pages identify themselves correctly to AI?
Confirms each single-question community page uses QAPage markup, not FAQPage.
What this signal tests
We check whether community Q&A pages (each containing one user-submitted question and one or more answers) emit QAPage structured data, not FAQPage. The markup includes the question text, the answer count, and at least one acceptedAnswer or suggestedAnswer with the full answer text and ideally author information.
Why it matters for your visibility in AI
Q&A content from real users is highly valuable to AI direct-answer engines because it reflects how people actually phrase questions. QAPage markup distinguishes this content from editorial FAQs (FAQPage) and forum threads (DiscussionForumPosting), letting AI tools weight and present it appropriately. Using FAQPage on user-submitted Q&A pages is a common mistake that causes those pages to be downweighted or filtered. Google specifically warns against this in its structured data guidance because FAQPage carries an implicit claim that the content is editorial and authoritative; QAPage signals that answers come from the community and may vary in quality. Marking your community Q&A correctly increases AI trust in your editorial FAQ content too, because the distinction tells the AI you understand your own content types.
Pass criteria at a glance
| Criterion | Passes when |
|---|---|
| Valid QAPage with one Question and at least one answer. |
How we test it
We crawl pages that match a community Q&A pattern (single question with answers from multiple users) and look for QAPage structured data. We confirm the mainEntity is a Question with name, answerCount, and either acceptedAnswer (singular, the accepted one) or suggestedAnswer (multiple, any non-accepted answers). The Answer object should include text and ideally author. Missing required fields fail the signal.
Show technical detection method
@type QAPage with mainEntity Question with required fields.
If your site fails: how to fix it
- Audit your community Q&A or help center templates. If any are currently using FAQPage but the content is user-submitted Q&A, switch them to QAPage.
- Update the template to emit @type QAPage with mainEntity as a single Question (not an array, unlike FAQPage). Include name, answerCount, and the answer objects.
- If your platform supports accepted answers (one answer marked correct or best), emit it as acceptedAnswer. Other answers go in suggestedAnswer as an array.
- Include author information on each Answer (and on the Question). Person objects with name and ideally url to the author's profile help AI tools attribute the answer correctly.
- Validate one URL in Google's Rich Results Test under the Q&A Page test type.
Quick facts
| Maturity | ESTABLISHED |
|---|---|
| Weight | medium |
| Category | Structured Data |
Primary sources
Related signals
Frequently asked questions
What is the difference between QAPage and FAQPage?
FAQPage is for editorial FAQs you wrote yourself, where each question has a single authoritative answer. QAPage is for community Q&A pages with one user-submitted question and one or more user answers. Mixing them up signals to AI that you do not understand your content, and reduces trust in both.
Do I need QAPage if I do not have a community forum?
Only if you have pages where users submit questions and other users answer them. If your only Q&A content is editorial, you do not need QAPage at all. Stack Overflow, Quora, and Reddit-style pages are the canonical use case; static FAQ sections are not.
Can a QAPage have multiple questions?
No. By definition QAPage is for one question. A page with several user-submitted questions and answers is better modeled as multiple QAPages (one per question, each on its own URL) or, if they are organised as discussion threads, as DiscussionForumPosting markup instead.
Run your own scan
Run a free scan and see how your site grades across all 155 AI-readiness signals.