In short. Google requires at least one accepted or suggested answer for Q&A rich result eligibility.
Definition: No. For a Google Q&A rich result, a
Questionmust have at least one answer, expressed withacceptedAnswerorsuggestedAnswer. An unanswered question can useanswerCount: 0, but it is ineligible for this rich result.
Key facts
- Google's QAPage documentation says a Q&A page contains one question followed by its answers.
- Google states that a question needs at least one answer, either
acceptedAnswerorsuggestedAnswer, to be eligible for the rich result. - For a question with no answers, Google says to set
answerCountto0; the same table says that question is not eligible for the rich result. - The
QAPageitem must contain itsQuestionundermainEntity, and Google expects oneQuestiondefinition on the page. - Schema.org describes
QAPageas aWebPagefocused on a specific question and its answers, as shown in the QAPage type definition.
What does Google require?
Google's QAPage documentation defines the rich result condition directly. The required Question properties include answerCount and either acceptedAnswer or suggestedAnswer. The answer property can describe an accepted answer or a suggested answer. The answer itself requires text, which is the full text of the answer.
The same table allows answerCount to be 0 when a question has no answers. That value records the state of the question. It does not make the question eligible: Google says that questions without answers are ineligible for the rich result.
How should the page be structured?
The page must represent a single question and its answers. Google's documentation says that the Question is nested under the mainEntity property of the QAPage item, and that only one QAPage type definition and one Question type definition should appear on the page. Schema.org describes mainEntity as the primary entity described by a page or other creative work.
For a question that already has an answer, the JSON-LD shape can look like this excerpt from Google's example:
{
"@context": "https://schema.org",
"@type": "QAPage",
"mainEntity": {
"@type": "Question",
"name": "How many ounces are there in a pound?",
"answerCount": 3,
"acceptedAnswer": {
"@type": "Answer",
"text": "1 pound (lb) is equal to 16 ounces (oz)."
}
}
}
The markup describes an answer only when the answer is present in the page content. A question with no answer can represent its count as zero, but it cannot meet the answer requirement for the Q&A rich result.
Does the rule apply to every QAPage?
Google says users must be able to submit answers to the question. It gives forums and product support pages as valid use cases, and it excludes an FAQ written by the site with no way for users to submit alternative answers. A page that answers a question as a how-to guide, blog post, or essay is also outside the documented QAPage use case.
Google documents a specific education-related case in which a Q&A page may have a single answer provided or selected by in-house experts. That exception still has one answer. It does not change the answer requirement for an unanswered question.
How can you check it?
Google recommends the Rich Results Test to validate and preview structured data. For a live page, its documentation also recommends the URL Inspection tool and says that Google must be able to access the page without a robots.txt block, noindex tag, or login requirement. Check that the rendered Question contains answerCount and at least one acceptedAnswer or suggestedAnswer, with the answer's full text.
Related terms
FAQ
Can an unanswered question use QAPage markup?
Yes, it can record answerCount as 0. Google says that an unanswered question is ineligible for the Q&A rich result.
Is one suggested answer enough?
Yes. Google identifies either acceptedAnswer or suggestedAnswer as sufficient to meet the answer property requirement, provided the answer includes its full text.
Can a site-written FAQ use QAPage markup?
Google's QAPage guidance gives a site-written FAQ with no way for users to submit alternative answers as an invalid use case. FAQPage structured data is a separate term in Google's structured data documentation.
Sources
- Google Search Central, "Q&A (QAPage) structured data", 8 September 2026
- Schema.org, "QAPage", undated
Check how a page reads to answer engines. Open the GEO score analyzer