QAPage Schema Generator
Generate QAPage JSON-LD with a question, accepted answer and suggested answers for forum and Q&A rich results. Not the same as FAQ schema. Free tool.
Missing fields Google checks for:
- mainEntity.name — the question title is required.
- acceptedAnswer or suggestedAnswer — at least one answer is required.
QAPage JSON-LD
What is the QAPage Schema Generator?
The QAPage Schema Generator creates structured data for pages where one question has user-submitted answers — forum threads, support communities and Q&A sites.
- Valid schema.org QAPage JSON-LD with Question mainEntity
- Accepted answer plus repeatable suggested answers
- answerCount computed automatically
- Upvote counts, authors and per-answer URLs
- Clear distinction from FAQPage markup
- 100% client-side — nothing is uploaded
How to use the QAPage Schema Generator
- 1
Enter the question title, and optionally its full text, author and date.
- 2
Add the accepted answer with its author, upvotes and direct URL.
- 3
Add any further suggested answers.
- 4
Review the warning list for missing required fields.
- 5
Copy or download the generated script tag into the thread's page.
About the QAPage Schema Generator
The QAPage Schema Generator creates structured data for pages where one question has user-submitted answers — forum threads, support communities and Q&A sites. Enter the question, the accepted answer and any suggested answers, and it builds the Question and Answer JSON-LD tree with answerCount calculated automatically.
QAPage is deliberately different from FAQ schema. An FAQPage is one page listing many questions the site itself answers; a QAPage is a single question answered by users, with upvotes and an accepted answer. Google treats them as different rich results with different rules, which is why this is a separate tool.
Everything runs 100% locally in your browser — nothing you type is uploaded. It suits forum owners, community managers and developers marking up user-generated Q&A threads.
Frequently asked questions
What is the difference between QAPage and FAQPage schema?
FAQPage is for a page of frequently asked questions written and answered by the site itself. QAPage is for a single question with answers from multiple users, like a forum thread, including upvotes and an accepted answer. They are separate rich results and must not be mixed on one page.
When should I use QAPage markup?
Use it on pages where users can submit answers to a question — forums, support communities, Stack-Overflow-style sites. If your page is editorial content with no user answers, FAQPage or plain Article markup is the correct choice instead.
What is an accepted answer?
The acceptedAnswer is the response marked as best by the question asker or by moderators. Google can highlight it in the rich result. Other community responses go in suggestedAnswer; both count toward the answerCount this tool computes for you.
Are upvote counts required?
No, upvoteCount is optional on both questions and answers, but include it if your platform has voting — it mirrors what users see on the page and Google's guidelines expect markup to match visible content.
Will my forum thread get a rich result from this?
The markup makes the page eligible for Q&A rich treatment, but Google decides per query and requires the markup to reflect real user-generated content. Threads that answer a genuine question well are the ones most likely to benefit.
Related tools
FAQ Schema Generator
Free FAQ schema generator: turn question-and-answer pairs into valid FAQPage JSON-LD, then check the markup before pasting the script into your page.
Article Schema Generator
Free article schema generator: build Article, NewsArticle or BlogPosting JSON-LD with headline, author, publisher, dates and image, ready to copy.
Breadcrumb Schema Generator
Free breadcrumb schema generator: build BreadcrumbList JSON-LD from simple name and URL rows, with positions numbered automatically. Copy the script and go.
JSON-LD Validator
Validate JSON-LD structured data in your browser: syntax errors with line numbers plus required and recommended property checks for 20 schema types.