How to use the Q&A Schema Generator
QAPage is the schema for community Q&A pages — Stack Overflow-style content where a single question has one accepted answer plus optional alternates. Different from FAQPage (single-author Q&A about a topic).
Add the question
Set the question text and the user who asked it. Voting metadata (upvoteCount) is optional but improves rich-result eligibility.
Set the accepted answer
The community-chosen best answer. Must include text, author, and ideally upvoteCount and dateCreated.
Add suggested answers (optional)
Other community answers below the accepted one. Each is a separate Answer object in the suggestedAnswer array.
Paste into and validate
Wrap in <script type="application/ld+json">. Validate with Rich Results Test. QAPage rich results are less common than FAQPage but still surface for community sites.
Why QAPage schema is for community Q&A, not FAQs
QAPage and FAQPage look similar but serve different content. Picking the wrong one disqualifies you from rich results. The distinction is who's asking and answering.
QAPage vs FAQPage — when to use which
- FAQPage — single-author content. The site owner answers frequently asked questions about a product/topic. Stripe FAQ, GitHub docs FAQ.
- QAPage — community-driven. One user asks a question, multiple users answer, one answer is accepted. Stack Overflow, Quora, Reddit-style sites.
- Wrong choice = no rich result. A Stack Overflow page using FAQPage gets rejected; a corporate FAQ using QAPage gets rejected.
Required fields for QAPage
mainEntity— the Question object.nameon the Question — the question text.acceptedAnswer— the chosen best answer (Answer type).texton each Answer — the answer body.authoron Question and each Answer — Person type with name.
Optional fields that lift rich-result eligibility
upvoteCounton Question and Answers — community signal.dateCreated— freshness signal.suggestedAnswerarray — alternate answers below the accepted.answerCounton Question — total number of answers.
Frequently asked questions
What's the difference between QAPage and FAQPage?
FAQPage is for single-author content where the site owner answers questions about a topic (corporate FAQ, product help docs). QAPage is for community-driven Q&A where one user asks and multiple users answer (Stack Overflow, Quora). Using the wrong type disqualifies the page from rich results.
Can I use QAPage on a single-author blog?
No — Google's policy specifies QAPage is only for community-driven Q&A with multiple potential answerers. For single-author Q&A, use FAQPage. Misusing QAPage triggers rich-result rejection and risks structured-data violation flags.
Do I need an accepted answer?
Yes — QAPage requires acceptedAnswer. If your platform has voting but no formal "accepted" concept, mark the highest-voted answer as accepted. If there are no answers yet, don't use QAPage on that page (or only mark up the question without an answer, which limits rich-result eligibility).
Can I have multiple QAPage blocks on one page?
Generally no — QAPage is for a single question with answers, not a list of questions. Use one QAPage per question. For pages listing multiple Q&A threads, mark up each thread on its own URL with a single QAPage each.
Do QAPage rich results still appear in Google?
Yes, especially for community sites and forums. Rich results show the accepted answer's first ~120 characters under the snippet. The visual treatment is similar to FAQ rich results but tied to the accepted answer specifically.