What Is QAPage Schema? Markup for Single-Question Pages

QAPage is the schema.org type for a page whose focus is a single question with one or more answers — the shape of a forum thread, a support-community post, or a Stack Overflow question. The markup declares one Question as mainEntity, with a suggestedAnswer list and optionally an acceptedAnswer, each answer carrying properties like upvoteCount and author that only make sense in a community context.

When is QAPage the right type instead of FAQPage?

The dividing line is authorship and cardinality. One page, many publisher-written Q&As: FAQPage. One page, one question, answers contributed by users: QAPage. Google's QAPage documentation is explicit that the type is for pages where users can submit answers, and it excludes single-author editorial content. The distinction matters operationally because the two types feed different search features and carry different eligibility rules — and because conflating them is a common structured-data audit finding.

How does the markup structure work?

The skeleton is a QAPage whose mainEntity is a Question with name (the question text), text (elaboration), answerCount, and answer entities. acceptedAnswer marks the answer the asker or community endorsed; suggestedAnswer holds the rest. Vote counts, timestamps, and author attribution per answer let consumers rank answer quality. As with all structured data, everything marked up must be visible on the page, and the markup should ship in server-rendered JSON-LD so non-rendering crawlers see it.

Why does QAPage matter for AI visibility?

Community Q&A punches far above its weight in AI answers — Reddit and Stack Exchange content appears constantly in ChatGPT and Perplexity citations because it contains specific, experience-based answers to long-tail questions no editorial team covers. If you operate a product community, support forum, or developer Q&A, QAPage markup makes that long-tail inventory legible: each thread becomes a machine-readable question-answer unit aligned with exactly one user query. For brands, a well-structured community is a citation asset that competitors cannot easily replicate, and marking it up correctly is the cheap part. Pair it with monitoring of which community threads engines actually cite via content and AEO tooling to learn which question formats earn answers.