Marking up a forum and its discussions
Discussion markup is meant for sites where people share first-hand perspectives. Replies nest the way the thread organises them, later pages of a long thread tie the original post to the main address, and a page listing posts must not name one of them as its main entity.
Who this markup is for
Discussion forum markup is designed for any forum-style site where people collectively share first-hand perspectives; it lets the engine better identify those discussions and make use of them in the discussions and forums features.
officialSource : Google Search Central, “Discussion forum (DiscussionForumPosting) structured data”
The phrasing is worth noting: first-hand perspectives, shared collectively. That describes an editorial genre rather than a technical format, and it is exactly the criterion the rater guidelines apply when judging these pages.
A forum following a question and answer pattern belongs to a different markup, the one provided for Q&A, rather than to discussion markup.
officialSource : Google Search Central, “Discussion forum (DiscussionForumPosting) structured data”
The first sorting therefore happens before any line of code: a space where a question draws rated answers is not a discussion forum, and it belongs to a different markup. Picking the wrong family is not an offence, but it describes the page as something it is not.
Nesting, and what it says
The general recommendation is to nest comments under the post they relate to; a threaded forum is represented by a tree of comments, a linear one by a series of comments attached to the original post.
officialSource : Google Search Central, “Discussion forum (DiscussionForumPosting) structured data”
The rule asks that the thread’s real structure be reflected, not an ideal one. A threaded forum produces a tree, a linear one produces a list. Flattening a tree loses the information that separates a reply from a general remark.
On later pages of a long thread, the ideal is to include the original post with the main page URL of the thread, the posts on the current page being attached to it as comments.
officialSource : Google Search Central, “Discussion forum (DiscussionForumPosting) structured data”
This is the most useful point for an old forum: without that link back, page fourteen of a thread presents itself as a discussion with no beginning. With it, it stays the continuation of an identified discussion, and the reference address does not move.
We mark up every page of your forum as a separate discussion: more declared pages, more chances of appearing in discussion results.
The declaration you must not make
Where a URL is primarily about a single post, that post is identified as the page's main entity; conversely, the documentation asks that a post not be marked as main entity on a page that is not the discussion page for it.
officialSource : Google Search Central, “Discussion forum (DiscussionForumPosting) structured data”
On a page listing posts — profile, topic or category — information is often incomplete, and it is up to the publisher to declare only what is present on the page while linking to the discussion-specific address.
officialSource : Google Search Central, “Discussion forum (DiscussionForumPosting) structured data”
The distinction is sharp: a page devoted to one post declares it as its main entity; a page listing several must name none of them that way. Since a forum engine’s template often produces the same structured data for the thread page and the category page, the mistake is easy and silent.
Markup describes a discussion, it does not produce one: on a page whose value lies in the exchanges it carries, markup makes visible what exists and adds nothing where the exchange is missing.
hypothesis
The status is that of a reading, and it links this guide to the previous one: the rater guidelines describe a forum’s main content as the question, the answers and the exchanges. Impeccable markup on a thread with no replies correctly describes a page that has not yet achieved its purpose.
Reflecting the real structure of discussions in the markup
hypothesis
- Effort
- high
- Time to effect
- weeks
- Risk
- none
- Durability
- lasting
The effort is high because it touches several templates and the logic of a forum engine. The delay follows crawling. The risk is nil: nothing here is a technique. Durability is medium, this markup being recent and tied to a feature that may change.
What does not work, or no longer works
Using this markup on a question and answer space. The documentation points explicitly to the other family.
Then declaring every page of a long thread as a standalone discussion. Later pages must tie the original post to the main address.
Finally, naming a post as main entity on a category or profile page. The documentation asks precisely that this not be done.
Sources
- Discussion forum (DiscussionForumPosting) structured data — Google Search Centralaccessed on
- General Guidelines, version of 11 September 2025, 182 pages — Googleaccessed on
Block revalidated on
Frequently asked questions
- Does this markup suit a Q&A page?
- No, and the documentation says so in its opening: a forum following a question and answer pattern belongs to the Q&A markup. Discussion markup targets sites where people share first-hand perspectives, which is not the same thing.
- How do you mark up a thread spread over several pages?
- By including, on each later page, the original post with the main page URL of the thread, the posts on the current page attached to it as comments. The discussion then keeps one reference address, whichever page you enter through.
- Should category and profile pages be marked up?
- The documentation leaves the choice, noting that those pages often hold only part of the information. One rule is firm, however: do not mark a post as main entity on a page that is not its discussion page.
- Must the reply tree be reproduced?
- Yes where it exists: the documentation asks that comments be nested under the post they relate to, and that a threaded forum be represented by a tree of comments. A linear forum is simpler, every post attaching to the original one.
- Does this markup improve the chances of appearing?
- It makes the exchange identifiable as a discussion, which is a condition of use in the corresponding features. It does not create the page's value: that lies in the posts themselves, which the rater guidelines treat as a forum's main content.