A page with a question as its heading and an answer beneath it looks like a question-and-answer page. Whether it counts as one, for Google’s structured data, depends on who can answer. That distinction is easy to miss, and getting it wrong means markup that cannot do what it was added for.
This article sets out what Google documents about Schema for Q&A Pages (QAPage), the general rules that sit above it, and its guidance on generated content. Where I give my own reading, I say so. It was prompted by a build of mine, ManFlu, whose visitor questions each get a page of their own. If you want a short routine to run on a page, my beginner guide, how to check whether a question page suits QAPage markup, walks through it.
What QAPage markup is for
Google describes Q&A pages as pages with data in a question and answer format: one question followed by its answers. Marked up with the schema.org QAPage, Question and Answer types, a page is eligible for a rich result. Google says the markup also helps it generate a better snippet, and that answer content may appear in the basic result when the rich result is not shown.
Eligible is the operative word. The General Structured Data Guidelines say structured data enables a feature to be present and does not guarantee that it will be, even when the Rich Results Test passes.
The rule most pages fail: users must be able to answer
The content guidelines are specific. Users must be able to submit answers to the question, and Google says not to use the markup where there is only one answer and no way for users to add alternatives. Its valid examples are a forum page where users can submit answers to a single question, and a product support page where users can do the same. Its invalid examples include an FAQ page written by the site itself with no way for users to submit alternative answers, a how-to guide that answers a question, a blog post that answers a question, and an essay that answers a question.
A question page, with and without what QAPage markup needs
Switch between a page that does not suit QAPage markup and one that does. Hover, focus or tap a numbered marker to see what Google says about that detail.
Does not suit QAPage
Boiler questions answered Three questions on this page
Note 1Answer by the site team
the only answer, no way for visitors to add anotherTop answer: the most recent one
picked because it is newestReply: I meant a panel radiator
marked up as a second answerMarkup holds a question the page does not show
- More than one question. Google says not to use QAPage markup for FAQ pages or pages with multiple questions per page. It is for pages whose focus is a single question and its answers. Schema for Q&A Pages (QAPage)
- No way to add answers. Users must be able to submit answers. Google lists an FAQ page written by the site itself, with no way for users to submit alternative answers, as an invalid use. Schema for Q&A Pages (QAPage)
- Top answer chosen by recency. A top answer must be accepted in some way on the site. Google says other forms of sorting, such as most recent, must not be used to identify top answers. Schema for Q&A Pages (QAPage)
- A comment marked up as an answer. Google says answer markup is for answers to the question, not for comments on the question or on other answers. Comments use the comment property and the Comment type. Schema for Q&A Pages (QAPage)
- Markup the reader cannot see. Google says not to mark up content that is not visible to readers of the page, and that structured data must be a true representation of the page content. A structured data issue can lead to a manual action, which costs the page eligibility for a rich result. General Structured Data Guidelines
Suits QAPage
- One question. The focus of the page is a single question and its answers. Google expects exactly one Question type on the page. Schema for Q&A Pages (QAPage)
- Users can answer. Google's valid examples are a forum page or a product support page where users can submit answers to a single question. Schema for Q&A Pages (QAPage)
- Accepted in a way the site supports. Google's examples of acceptance are the asker, a moderator or a voting system. Schema for Q&A Pages (QAPage)
- The reply is a comment. Comments on the question or on other answers go in the comment property, not in answer markup. Schema for Q&A Pages (QAPage)
- Markup matches the page. Google's QAPage guidelines also ask that each Question and Answer holds the entire text of the question or answer. Schema for Q&A Pages (QAPage)
My reading: a page where visitors send in a question and the site publishes one answer sits closer to the invalid list than the valid one, unless there is a way for others to add answers. Google does not discuss that exact case, so this is an inference. The practical test is the documentation’s own: could a second person add a different answer to this page?
One question per page, and not every page
Google says QAPage is for pages whose focus is a single question and its answers. It says not to use it for FAQ pages or pages with multiple questions per page, and not to apply it to every page of a site or forum where not all content is eligible. A forum may have many eligible questions and also pages that are not questions, and those other pages are not eligible. There must be one QAPage and one Question per page.
What the markup must contain
The required properties are the question’s name, an answer count, and at least one answer, either accepted or suggested. Questions with no answers can carry an answer count of 0 but are not eligible for the rich result. Google says each question should include the entire text of the question and each answer the entire text of the answer, and that answer markup is for answers, not for comments, which have their own type.
It also says an accepted answer must be accepted in some way on the site, such as by the asker, a moderator or a voting system, and that sorting by recency must not identify top answers. Q&A content may not appear as a rich result if it contains obscene, profane, sexually explicit, graphically violent, hateful or harassing language, or promotes dangerous or illegal activities. Where visitors supply the questions, that is a moderation matter as much as a markup one.
The markup must match what people can see
The general guidelines say not to mark up content that is not visible to readers of the page, and that structured data must be a true representation of the page content. A structured data issue can lead to a manual action. Google says this means the page loses eligibility for a rich result, and that it does not affect how the page ranks in Google web search. Markup is therefore not what decides whether a page is indexed or ranked; the page can exist and be found without it.
My reading: wrong markup costs you the feature and can attract a manual action, so leaving markup off is safer than claiming a type the page does not fit.
Generated answers: what Google says to check
If answers are written by a model, two documents apply. Google’s Spam Policies for Google Web Search define scaled content abuse as many pages generated for the primary purpose of manipulating search rankings and not helping users, and list using generative AI tools to generate many pages without adding value for users as an example.
Its Guidance on Generative AI Content on Your Website says generative models predict a likely sequence of words and do not retrieve facts, so outputs may contain inaccuracies. It calls it critical to fact-check and review generated content before publishing, including metadata and structured data, and suggests telling readers how automation was used. The same guidance says generative AI can be useful for researching a topic and adding structure to original content. The line it draws is value for users, not the tool.
My reading: a page needs a reason to exist beyond the fact that a question was asked, and for any subject where a wrong answer could do harm, review matters more than volume. For a satirical site that states plainly that it is satire, the disclaimer belongs on the page, where readers and reviewers can see it. My article on visitor-submitted questions and stories covers the user-generated side of this.
A short checklist before adding Q&A markup
- Is each page about one question, with the question and answer visible?
- Can visitors add their own answers? If not, check Google’s invalid list again.
- Does the markup contain the full text of the question and of every answer it describes?
- Has a person read the answer, and the title and description, before it went live?
- Is anything off-topic or unsuitable held back until it has been reviewed?
- Does the Rich Results Test show the markup parsing without critical errors, and does the URL Inspection tool show Google can reach the page?
Where this fits at Cultured Digital: structured data that describes the page
My structured data and entities guide covers the technical side of describing a page truthfully, and the websites page covers building sites with search in the architecture. My earlier piece on what Google supports and does not promise for structured data covers the general rules, and the article on AI-generated content and review covers the generated-content guidance in more depth.
