Skip to content

QAPage vs FAQPage vs DiscussionForumPosting: which schema fits

QAPage, FAQPage or DiscussionForumPosting for forum and community content? Which one Google's docs say fits, required properties, examples and common mistakes.

By Crawlito · 7 min read

In short

  • Google says to use QAPage for a page built around one question where users can submit answers, not for FAQ pages or pages with several questions.
  • DiscussionForumPosting is for user-generated forum threads that are not mainly question and answer; Google says not to use it for content written by the site's publishers.
  • FAQPage describes questions and answers written by the site itself; Google removed the FAQ rich result in May 2026, but the schema.org type is still valid.
  • QAPage requires mainEntity with a Question that has name, answerCount and an acceptedAnswer or suggestedAnswer; DiscussionForumPosting requires author, datePublished and text, image or video.
  • Markup must match visible content: every answer or comment you mark up must be on the page, in full.
On this page

Use QAPage when a page is built around a single question and users can post answers to it, as on Stack Exchange-style sites. Use DiscussionForumPosting for forum threads and community discussions that are not mainly question and answer. Use FAQPage only for a list of questions and answers your own organisation wrote. That is how Google's structured data documentation divides them, and picking the wrong one is the most common mistake on community sites.

This guide covers what each type is for according to Google, the required properties, working JSON-LD examples, and the errors to avoid.

Which type fits your page

PageTypeWho writes the answers
One user question with answers from other usersQAPageUsers
Forum thread, discussion or comment threadDiscussionForumPostingUsers
Social media post with repliesSocialMediaPostingUsers
Help centre FAQ, product FAQFAQPageThe site
Blog post or article with a comment sectionArticle or BlogPostingThe site
Customer reviews of a productReview within ProductUsers

Three rules from Google's documentation settle most cases:

  • Google's Q&A guidance says QAPage is for a page focused on a single question and its answers, and must not be used for FAQ pages or pages with multiple questions. Users must be able to submit answers.
  • Google's discussion forum guidance says that if the site is mainly questions and answers, use Q&A markup; DiscussionForumPosting is for more general discussion structures.
  • The same forum guidance says DiscussionForumPosting is for user-generated content, not content primarily written by the site's publishers or their agents. Articles and blog posts with comments do not qualify, and neither do product reviews.

QAPage: one question, user answers

A QAPage has a mainEntity that is a Question. The question carries its answers as acceptedAnswer (the answer the asker or the site marked as accepted) and suggestedAnswer (the others).

Google's required properties at the time of writing:

TypeRequiredRecommended (selection)
QAPagemainEntity
Questionname, answerCount, and acceptedAnswer or suggestedAnswertext, author, datePublished, upvoteCount, comment, dateModified
Answertexturl, author, datePublished, upvoteCount, comment

Google strongly recommends a url on each answer so it can link directly to it. It also says questions with no answers are not eligible for the rich result, although answerCount can be 0 in the markup.

json
{
  "@context": "https://schema.org",
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "How do I reset the filter light on a Model 400 purifier?",
    "text": "The filter light stays on after I fitted a new filter. How do I reset it?",
    "answerCount": 2,
    "datePublished": "2026-06-02T09:14:00+01:00",
    "author": { "@type": "Person", "name": "jlee", "url": "https://forum.example.com/u/jlee" },
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Hold the filter button for five seconds until the light blinks twice.",
      "url": "https://forum.example.com/q/1842#answer-1",
      "upvoteCount": 14,
      "datePublished": "2026-06-02T10:01:00+01:00",
      "author": { "@type": "Person", "name": "dana_r", "url": "https://forum.example.com/u/dana_r" }
    },
    "suggestedAnswer": [{
      "@type": "Answer",
      "text": "Unplug it for a minute first if holding the button does nothing.",
      "url": "https://forum.example.com/q/1842#answer-2",
      "upvoteCount": 3,
      "datePublished": "2026-06-02T11:20:00+01:00",
      "author": { "@type": "Person", "name": "mk2", "url": "https://forum.example.com/u/mk2" }
    }]
  }
}

Google notes that answers in Q&A markup may be shown in the snippet of a normal result even when no rich result appears, and that education Q&A pages with a single expert-selected answer may be eligible for a separate carousel.

DiscussionForumPosting: threads and discussions

DiscussionForumPosting describes the original post of a thread, with replies as comment items. Google's required properties:

  • author: a Person or Organization with a name
  • datePublished: ISO 8601 date and time
  • At least one of text, image or video, unless the post is represented by a link to another page, such as a forum category listing

Recommended properties include headline, url, comment, commentCount, interactionStatistic (likes, views, replies), isPartOf (the subforum), sharedContent, dateModified and creativeWorkStatus. Setting creativeWorkStatus to Deleted marks a removed post that you keep on the page for context.

json
{
  "@context": "https://schema.org",
  "@type": "DiscussionForumPosting",
  "headline": "Which sourdough starter ratio works in a cold kitchen?",
  "text": "My kitchen sits around 16 degrees in winter and my starter barely rises. What ratio do you use?",
  "url": "https://forum.example.com/t/cold-kitchen-starter",
  "datePublished": "2026-01-12T08:30:00+00:00",
  "author": { "@type": "Person", "name": "breadhead", "url": "https://forum.example.com/u/breadhead" },
  "isPartOf": { "@type": "WebPage", "url": "https://forum.example.com/c/sourdough" },
  "interactionStatistic": {
    "@type": "InteractionCounter",
    "interactionType": "https://schema.org/CommentAction",
    "userInteractionCount": 2
  },
  "comment": [{
    "@type": "Comment",
    "text": "I switched to 1:5:5 and moved the jar on top of the fridge.",
    "datePublished": "2026-01-12T09:05:00+00:00",
    "author": { "@type": "Person", "name": "ovenspring", "url": "https://forum.example.com/u/ovenspring" }
  }]
}

Google asks that you include the entire text of the post and of each comment shown on the page.

FAQPage: your own questions and answers

FAQPage is for questions and answers written by the site: a returns FAQ, a product FAQ, a support page. Users cannot add answers.

Google's FAQ rich result is gone. Its structured data changelog says the feature stopped appearing in Search from 7 May 2026, and the FAQ documentation was removed in June 2026. The type itself is still part of schema.org, and the markup remains a valid, machine-readable description of a page's questions and answers. Our FAQ schema guide covers whether to keep it.

The point for community sites is what not to do: marking a forum thread or a user Q&A page as FAQPage misdescribes it. The answers are from users, there may be many of them, and they may disagree. QAPage and DiscussionForumPosting describe that structure; FAQPage does not.

Pages that mix types

Real community sites rarely fit one box. A few patterns and how to handle them:

  • A support forum with an official answer. If users ask and a staff member answers, and other users can add answers too, the page is still a QAPage. The staff reply can be the acceptedAnswer. The type follows the structure of the page, not who happens to answer.
  • A thread that starts as a question and turns into a discussion. Pick the structure that describes most of the page. If the opening post is a question and replies are answers to it, use QAPage. If replies talk to each other and drift, DiscussionForumPosting fits better.
  • A product page with a customer questions section. The page is about the product, so its main markup is Product. Do not wrap the whole page in QAPage. If the questions have their own pages, mark those up separately.
  • A help centre with a "was this helpful" widget and comments. The article was written by the site, so it is an Article or a FAQPage, not a forum post. Comments do not change who authored the main content.

When unsure, describe less rather than more. Markup that understates a page is harmless; markup that claims a structure the page does not have is the kind Google's guidelines warn against.

What crawlers need besides markup

Markup sits on top of the page. For forum and Q&A content, a few page-level basics matter as much:

  • Server-rendered threads. Many forum platforms load replies with JavaScript. If the first answer is not in the initial HTML, crawlers that do not run JavaScript see a question with no answers.
  • One URL per thread. Sort orders and view modes often create several URLs for the same thread. Point them at one canonical URL.
  • Crawlable pagination. Long threads split across pages need plain links between pages, not only a "load more" button.

Knowledge bases and AI search covers the same issues for help centres.

Common mistakes

Using QAPage for a page with many questions. A category page that lists ten questions, each linking to its own thread, is not a QAPage. Mark up each question page separately, or use DiscussionForumPosting on the thread pages.

Using DiscussionForumPosting for your own blog. Google lists blog posts and articles written by the site, even with comments, as invalid uses.

Marking up content that is not on the page. Every answer, comment and count must match what a visitor can see. If replies load by JavaScript after the initial HTML, they are not in the server's response for crawlers that do not render. Render them on the server or mark up only what is in the HTML.

Wrong or missing answerCount. It should match the number of answers on the page. A stale count from a cache is a quiet source of mismatch.

Anonymous authors. Google recommends author.url for both types. A profile URL helps identify who wrote what, and on a forum it is usually available.

Ignoring deleted posts. If you keep a placeholder for a removed post so the thread still makes sense, mark it with creativeWorkStatus: Deleted rather than removing the item or keeping old text.

How to check your markup

  1. Fetch the raw HTML and confirm the JSON-LD is in it, not injected later:
bash
curl -s https://forum.example.com/q/1842 | grep -c 'application/ld+json'
  1. Paste the URL into Google's Rich Results Test and the Schema Markup Validator. The first checks Google's requirements; the second checks schema.org syntax.
  2. Compare every marked-up answer and comment with the visible page.
  3. After deploying, check the structured data reports in Search Console, where your property shows them, for errors across the site.

JSON-LD errors lists the syntax problems that make whole blocks unreadable, and structured data and AI search covers what is and is not documented about how AI systems use markup.

Frequently asked questions

Can I use FAQPage on a forum or Q&A page?

It is the wrong type. FAQPage describes questions and answers written by the site. User-submitted answers fit QAPage, and general discussion threads fit DiscussionForumPosting.

Should a Q&A site use QAPage or DiscussionForumPosting?

Google says sites that are mainly questions and answers should use Q&A markup. Use DiscussionForumPosting for discussion that is not structured as a question with answers.

Can I mark up comments on my blog posts as DiscussionForumPosting?

No. Google's forum guidance says it is not for articles or blog posts written by the site, even if they have comments.

Does QAPage markup make my answers appear in AI answers?

No AI search operator documents that QAPage markup changes whether a page is used. Markup describes the page; it does not cause citations. Make sure the answers are in the HTML first.

Check the HTML behind your markup

Structured data only describes what is on the page, so start with the page. To see whether your answers and comments are in the HTML that AI crawlers receive, run the free check on a thread or question page.

Filed under Structure and schema. Topics: structured-data, json-ld, google, content