These two schema types were always different, but the difference was easy to ignore: both marked up questions and answers, both were valid, both could earn a rich result. Then Google retired FAQPage's rich result in May 2026 and kept QAPage's. Suddenly the distinction is the difference between a supported rich result and none.
Yet they're still constantly conflated, and the conflation now has a concrete cost: sites using the wrong type either forfeit a rich result they're eligible for, or expect one that no longer exists. This post draws the line precisely.
The one-sentence difference
FAQPage is for questions you answer. QAPage is for questions your users answer.
FAQPage marks up a page where the site owner publishes both the questions and the authoritative answers, the FAQ section at the bottom of a product page. One definitive answer per question, written by you.
QAPage marks up a page where a single question receives answers from a community, a forum thread, a Stack Overflow-style page, a support community where users respond. One question, potentially many competing answers, submitted by other people.
That's the whole distinction, and every other difference flows from it.
Why it suddenly matters
Before May 2026, this was a pedantic point. Both types produced rich results, so using FAQPage where QAPage fit still got you something.
That changed:
- FAQPage rich results were removed on May 7, 2026, for every site, including the government and health publishers who'd kept eligibility since 2023. The markup remains valid and useful for machine comprehension, but it no longer produces a SERP feature. We covered this fully in Is FAQ Schema Dead?.
- QAPage rich results remain supported. Google still displays the question, answer count, and top answer as a rich result for eligible Q&A pages.
So the stakes flipped. Using FAQPage where QAPage was correct now means forfeiting a live rich result. Using QAPage where FAQPage was correct means claiming user-generated content you don't have, a mismatch with your actual page. The types aren't interchangeable, and picking wrong has a real consequence in each direction.
There's a historical irony worth noting. For years, FAQPage was the heavily-promoted, widely-abused type, bolted onto pages that weren't FAQs to grab extra SERP space, while QAPage sat quietly as the niche option for forums. The May 2026 change inverted that: the abused type lost its feature, and the niche one is now the type with the live rich result that many eligible sites don't use. If you run genuine community Q&A, you're sitting on the more valuable of the two and may not know it.
How to tell which you have
Ask one question: who wrote the answers?
You wrote them → FAQPage. Your shipping FAQ, your product FAQ, your policy explanations. You are the authority, the answer is definitive, and there's one answer per question.
Your users wrote them → QAPage. A community forum, a Q&A board, a discussion where multiple people respond to one question. The answers compete, they can be voted on, and there's one question per page.
A useful tell: if the "answers" could be edited by your marketing team without anyone objecting, it's FAQPage. If editing a user's answer would be misrepresenting what they said, it's QAPage.
The trap: a product page with "Why is our product better than the competition?" and "What makes us different?" is not Q&A content of either kind. Those are marketing statements dressed as questions. Neither FAQPage nor QAPage belongs there, and using either is the "marking up content that isn't really that" pattern Google treats as a problem.
FAQPage structure
For reference, since it's still valid markup worth implementing correctly even without the rich result:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does shipping take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Standard shipping takes 3-5 business days within the US."
}
},
{
"@type": "Question",
"name": "Do you ship internationally?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes, we ship to most countries. International delivery takes 7-14 business days."
}
}
]
}The defining traits: mainEntity is an array of multiple Questions, and each Question has exactly one acceptedAnswer. You provide the answer, so it's always "accepted." There's no suggestedAnswer, no upvoteCount, no answer authors, because there's no community involved.
QAPage structure
QAPage is shaped by the community it describes, and it's more involved:
{
"@context": "https://schema.org",
"@type": "QAPage",
"mainEntity": {
"@type": "Question",
"name": "How do I center a div in CSS?",
"text": "I've tried margin: auto but it doesn't always work. What's the modern approach?",
"answerCount": 14,
"upvoteCount": 382,
"author": {
"@type": "Person",
"name": "css_newbie"
},
"acceptedAnswer": {
"@type": "Answer",
"text": "Use flexbox: set the parent to display:flex, justify-content:center, align-items:center.",
"url": "https://example.com/q/123#answer-1",
"upvoteCount": 215,
"author": {
"@type": "Person",
"name": "css_expert"
}
},
"suggestedAnswer": [
{
"@type": "Answer",
"text": "CSS Grid also works: display:grid, place-items:center on the parent.",
"url": "https://example.com/q/123#answer-2",
"upvoteCount": 89,
"author": {
"@type": "Person",
"name": "grid_fan"
}
}
]
}
}Notice the structural differences from FAQPage:
mainEntity is a single Question, not an array. Google requires exactly one Question per QAPage, one Question definition nested under mainEntity. A page with several independent questions is not a QAPage.
answerCount is required, and reflects the total number of answers on the page.
Both acceptedAnswer and suggestedAnswer are valid. acceptedAnswer is the chosen or top answer (zero or one); suggestedAnswer is an array of the others. FAQPage only uses acceptedAnswer.
Answers carry author, url, and upvoteCount. These make sense because real people wrote them, they live at specific anchors, and they can be voted on. Google recommends a URL for each answer, anchoring to where it appears on the page.
The question itself has a text and often an author. The name is the question title; text is its full body, as a user would have typed it.
The property that catches everyone
The single most common error, and it produces a confusing symptom.
If you build an FAQ (you wrote the answers) but use suggestedAnswer instead of acceptedAnswer, the Rich Results Test reports a "Missing field acceptedAnswer" error. Your markup is technically valid, suggestedAnswer is a real property, but it's the wrong property for FAQPage, and Google ignores it in that context.
The reverse trips people too: using acceptedAnswer exclusively on a genuine QAPage is fine, but if the community hasn't accepted an answer, you should be using suggestedAnswer for the responses, not forcing one into acceptedAnswer.
The rule to memorize: acceptedAnswer = the definitive answer (you, or the accepted community answer). suggestedAnswer = competing community answers with no single authority. Get this right and most QAPage/FAQPage confusion disappears.
Education Q&A and Discussion Forum
Two related types round out the family, both still supported, both frequently missed.
Education Q&A is a specialization for education-focused questions and answers, which can surface as flashcards to help students. If you run an education or study-resource site with genuine Q&A content, this is more specific than plain QAPage and worth using.
Discussion Forum (DiscussionForumPosting) is for forum-style content, user-generated posts followed by threaded or non-threaded discussion. Google introduced it alongside Profile Page in late 2023, and it's aimed at the forum and community sites that Google also began surfacing more prominently. If your site is structured as a forum rather than a single-question-with-answers format, DiscussionForumPosting may fit better than QAPage.
The takeaway: "questions and answers on a page" isn't one schema type. It's four, FAQPage, QAPage, Education Q&A, and Discussion Forum, and three of them still earn rich results. Choosing the one that honestly describes your page is the whole game.
Migrating from FAQPage to QAPage
If you've realized your community Q&A content is marked up as FAQPage, or not marked up at all, and QAPage genuinely fits, here's how to switch without breaking things.
Confirm it's actually QAPage content first. The trap is switching to chase the rich result when your content is authored, not user-generated. Re-run the "who wrote the answers" test. Only migrate if real users submitted the answers.
Restructure to one question per page. This is the biggest change and it's architectural, not just markup. FAQPage puts many questions on one page; QAPage requires exactly one question per page. If your community content already lives at one-question-per-URL, as forum threads usually do, you're aligned. If you'd been cramming multiple community questions onto one page under FAQPage, you need to split them, which is a URL and content decision, not only a schema one.
Capture the answer metadata you were discarding. FAQPage threw away everything that makes community answers rich, authors, vote counts, timestamps, per-answer URLs. QAPage uses all of it. If your platform records who answered and how answers were voted, surface that data into the markup; it's what powers the answer-count and top-answer display.
Map accepted vs suggested honestly. If your community has an "accepted answer" mechanism, that answer becomes acceptedAnswer and the rest become suggestedAnswer. If there's no acceptance mechanism, everything is suggestedAnswer and you omit acceptedAnswer, don't fabricate an acceptance that didn't happen.
Validate one page before rolling out. Because QAPage is template-driven on community sites, a mistake replicates across every thread. Get one page passing the Rich Results Test cleanly, confirm the answer count and top answer display as intended, then apply the template.
Don't leave both types on the page. If FAQPage markup lingers alongside new QAPage markup, you're describing the same content as two contradictory things. Remove the old markup as part of the switch.
The reward for getting this right is real: community Q&A is one of the content types Google still actively surfaces with a rich result, and a lot of forum and support-community sites are currently claiming none of it.
Which should you use? A decision guide
You run an ecommerce or business site with an FAQ section you wrote → FAQPage. Accept that it won't produce a Google rich result post-May-2026, but it remains valid and useful for machine comprehension. Don't switch to QAPage to chase the rich result, your content isn't user-generated, and misrepresenting it is worse than losing a SERP feature.
You run a community, forum, or support board where users answer questions → QAPage (or Discussion Forum, if it's more forum-shaped). This is where the live rich result is, and where a lot of sites are leaving it unclaimed by either using FAQPage or no markup at all.
You run an education or study site with Q&A content → Education Q&A.
You have marketing copy shaped like questions → neither. Use Article or the appropriate content type, and don't force Q&A markup onto it.
You're not sure whether your answers count as user-generated → ask whether editing them yourself would be honest. If yes, it's your content (FAQPage). If editing would misrepresent someone, it's theirs (QAPage).
What this means for AI search
Worth a brief, honest note, since it's where the FAQPage-still-matters argument usually lands.
The common claim is that FAQPage markup, though it lost its Google rich result, still helps AI systems parse your questions and answers. That's plausible, structured Q&A content is easier for a machine to extract than the same content in prose, and Microsoft has confirmed structured data helps its models understand content. But it's not a Google-documented benefit: Google states no special schema is required for its AI features. So the accurate framing is that FAQPage remains useful for machine comprehension across systems, not that it's secretly an AI ranking lever. We set out where that line sits in does schema markup help with AI Overviews.
For QAPage the AI angle is stronger in one specific way: genuine community Q&A content, real questions, real competing answers, is exactly the kind of specific, first-hand material that answer engines tend to find citable, precisely because it's not the generic content forty other sites also have. The markup helps a machine parse it; the community-generated substance is what makes it worth citing.
Common mistakes
Using FAQPage for user-generated Q&A, forfeiting the QAPage rich result that content is eligible for.
Using QAPage for content you authored, claiming community answers you don't have.
suggestedAnswer on an FAQPage, the "missing acceptedAnswer" error.
Multiple Questions in a QAPage, QAPage requires exactly one question per page; multiple questions is FAQPage territory (or separate QAPages).
Q&A markup on marketing copy shaped like questions.
Expecting an FAQPage rich result post-May-2026, it's gone; the markup is for comprehension now.
Missing answerCount on QAPage, a required field.
Omitting answer url anchors on QAPage, recommended, and it helps Google associate each answer with its place on the page.
Validation
Run both types through the Rich Results Test. For QAPage it confirms eligibility for the Q&A rich result; for FAQPage it will validate the syntax but no longer indicates a rich result, since that feature is retired.
Search Console retains reporting for supported types. The FAQ report is being retired alongside the feature, so don't rely on it going forward.
The Schema Markup Validator at validator.schema.org handles generic syntax for both.
The check that matters most isn't technical, though, it's whether you've chosen the type that honestly describes who wrote the answers. Valid markup of the wrong type is still the wrong type.
For the current full picture of what's supported, see our complete guide to Google's supported schema types, and if you'd rather have the right type generated for you automatically, see our docs or pricing.
Frequently Asked Questions
AI Schema Gen generates the correct question-and-answer schema type for your content, FAQPage, QAPage, or Q&A, across 530+ types. Start free or browse the schema types directory.
Generate perfect schema in 30 seconds
AI Schema Gen handles everything automatically, free to start.
Get Started Free