What is discussion forum structured data?

Discussion forum structured data is a Schema.org markup built exclusively for user-generated content on forums: discussion threads, replies, and comments that several people write collectively. Google Search Central describes it as markup for forum-style sites where people share first-hand perspectives, and it draws a clear line against other content types. The official documentation states plainly that DiscussionForumPosting markup should only be used to describe a user-generated post on a website, not content that is primarily authored by the site's publishers. That excludes articles, blog posts, and brand-written product reviews, even when they are published in a thread format. There is also a boundary with a related markup type: if a site's structure is primarily questions with answers, Q&A markup applies instead of forum markup. The core of the schema is DiscussionForumPosting, which can nest comments (Comment) inside the original post, mirroring the actual structure of a thread: an initial message and a chain of replies underneath. This distinction between what a brand writes and what its community writes is the axis of the entire markup, and also the reason a support forum, a product community, or a topical subforum are the natural candidates for implementing it, while a corporate blog is not.

The markup requires a minimum set of properties both on the main post and on each nested comment. For DiscussionForumPosting, Google Search Central requires as mandatory author (with author.name), datePublished in ISO 8601 date-time format, and at least one of these three: text, image, or video. The same requirement repeats inside each Comment: author, publication date, and again at least text, image, or video. Without these properties, Google does not consider the markup valid, and the page is not eligible for the rich result, no matter how complete the remaining information is. Alongside the required properties there is a group of recommended ones that Google does not demand but does value: dateModified to signal later edits, commentCount and interactionStatistic to reflect the thread's activity, url and author.url to link the author's profile, and one recently added to the documentation, digitalSourceType, meant to distinguish content generated by a person from content generated by an algorithmic or AI-trained system. Google's documentation, checked on August 20, 2026, shows a last-updated date of March 24, 2026, indicating that Google keeps adjusting this markup and has not left it unchanged since launch. There is also an unusual technical detail: while Google prefers JSON-LD for most structured data types, for DiscussionForumPosting it explicitly recommends Microdata or RDFa wherever possible, a declared exception to its own general rule.

This markup matters because it covers a content type no other schema represents precisely: the collective conversation, with multiple authors and a thread structure, distinct from a single-author article or a list of questions and answers. Google introduced it, according to Search Engine Land, on November 27, 2023, together with profile page markup, and continues to actively update it, as shown by the digitalSourceType addition documented in March 2026. For a site with an active community, such as a technical support forum, a question space among users of a product, or a niche-specific subforum, implementing it is the difference between Google treating that content as a generic mass of text or recognizing it for what it is: contributions from real people with first-hand experience, exactly the kind of signal Google's content quality guidance has asked for over years. The decision that hinges on this is simple to state: any site with active forums or user communities should evaluate whether to implement this markup before putting the same effort into another structured data type with a weaker real fit for its content. For agencies or in-house teams managing several client sites with community sections, the added benefit is that the implementation is repeatable across sites once the pattern has been solved technically for a given forum platform.

• Mark the main post and each comment as separate entities (nested DiscussionForumPosting and Comment), not as a single block of text, so Google reads the thread structure correctly.
• Always include author.name and datePublished for every post and every comment: they are mandatory, and without them the markup is not valid, no matter how complete the rest is.
• Add dateModified when the thread is edited, so Google can distinguish between the original date and a later update.
• Use Microdata or RDFa for this specific markup type instead of JSON-LD, following Google's explicit recommendation, even if the rest of the site uses JSON-LD.
• Validate the markup with the Rich Results Test and check the corresponding report in Search Console before considering it published.
• Reserve this markup for genuinely user-generated content; if the site publishes articles written by the editorial team, use the article structured data type instead of this one.

• Applying DiscussionForumPosting to articles or product reviews written by the brand itself, a use case Google's documentation explicitly rules out.
• Skipping the nesting of comments and marking only the initial post, so the thread loses the conversation structure that gives the markup its purpose.
• Confusing this markup with the Q&A one when the site actually functions as a pure question-and-answer forum.
• Using JSON-LD out of habit, without accounting for the fact that Google recommends Microdata or RDFa specifically for this structured data type, regardless of what the rest of the site uses.
• Assuming the markup guarantees the rich result: Google may or may not show it, depending on its own quality and relevance criteria, and a valid implementation is only the entry ticket, not a guarantee.