About the Q&A Page Schema Generator
QAPage markup is for pages built around a single question that users answer, such as a thread on a support community or a Q&A site. It can make the page eligible for Google's Q&A rich result, which can show the question with a preview of the top answers. The mainEntity must be a Question with a name, answerCount and at least one acceptedAnswer or suggestedAnswer; each Answer needs text, with author, upvoteCount, url and datePublished recommended.
This QA page schema generator builds the markup in your browser. It is not a replacement for FAQ markup: if the site owner wrote all the questions and answers, QAPage is the wrong type. Use one question per page, include every answer shown on the page, and keep vote counts in step with what visitors see.
How to use it
- Enter the question title, full question text, author and date.
- Add each answer with its text, author and upvote count.
- Mark the accepted answer, if there is one.
- Copy the JSON-LD into the question page template and test it.
Frequently asked questions
When should I use QAPage instead of FAQPage?
Use QAPage when one question is asked and users can submit answers, as on forums and support communities. FAQPage is for questions and answers written by the site owner. Using QAPage on a static FAQ, or on a page with several unrelated questions, does not follow Google's guidelines.
What is the difference between acceptedAnswer and suggestedAnswer?
acceptedAnswer marks the answer the question's author or a moderator chose as the best. suggestedAnswer covers other answers. A page needs at least one of the two, and can have one accepted answer with several suggested ones. Include every answer visible on the page.
Can I use QAPage for a product question section?
Google's guidance is aimed at pages whose main purpose is a single question and its answers. A product page with a questions section has the product as its main topic, so Product markup fits better there than QAPage. Keep any visible Q&A section accurate.