Skip to content

Discussion Forum Schema Generator - Forum Post JSON-LD

Import existing JSON-LD

Paste JSON-LD or a full <script> tag. Matching fields fill the form; properties the form doesn't cover are kept in the output as they are.

Post

Google needs text, an image or a video.

Author

Replies

Google Search Preview
Preview not available for this type.
All Google requirements met

JSON-LD Output

What is DiscussionForumPosting schema?

DiscussionForumPosting schema is structured data for a post in an online forum or community thread. It tells search engines who wrote the post, when, what it says, and which replies belong to it. Google uses it to find first-hand discussions to show in the Discussions and forums section of search results.

Each post needs an author with a name, a datePublished, and some content in text, image, or video. Replies go in the comment property as Comment objects, which follow the same rules and can nest further replies.

DiscussionForumPosting schema example (JSON-LD)

A complete example you can adapt. Paste it into the page's HTML, or build your own with the generator above.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DiscussionForumPosting",
  "headline": "Is a 1.5 mm nozzle worth it for large prints?",
  "text": "I print a lot of big planters in PETG. Has anyone switched from 0.6 to 1.5 mm? How much time did you save, and was the surface finish acceptable?",
  "url": "https://forum.example.com/t/1-5mm-nozzle-large-prints/91822",
  "datePublished": "2026-10-02T18:41:00+01:00",
  "author": {
    "@type": "Person",
    "name": "Tomasz Nowak",
    "url": "https://forum.example.com/u/tnowak/"
  },
  "commentCount": 1,
  "comment": [
    {
      "@type": "Comment",
      "text": "Switched last spring. Print time roughly halved on planters, but layer lines are obvious. Fine for garden pots, not for anything indoors.",
      "datePublished": "2026-10-02T20:15:00+01:00",
      "author": {
        "@type": "Person",
        "name": "Ellie Brookes",
        "url": "https://forum.example.com/u/ellieb/"
      }
    }
  ]
}
</script>

Which Google rich result does it enable?

This markup helps Google show your threads in the Discussions and forums feature and in Perspectives, which highlight first-hand experience from community sites. Google can often read forum pages without markup, but structured data removes guesswork about authors, dates, and which reply belongs to which post.

There is no guarantee of a special snippet. The markup makes your content easier to understand and eligible for these features.

Required and recommended properties

Property Status Notes
author Required A Person or Organization. Add author.url linking to the member's profile page.
author.name Required The display name shown on the post.
datePublished Required When the post was made, ISO 8601 with a time zone.
text, image, or video Required At least one. Use text for the body, image for image-only posts, and a VideoObject in video for video posts.
headline Recommended The thread title. Only needed on the first post.
url Recommended The canonical URL of the thread or post.
comment Recommended Replies as Comment objects, each with author, datePublished, and content.
commentCount Recommended Total replies, including ones on other pages of the thread.
dateModified Recommended When the post was last edited.
interactionStatistic Recommended Likes, views, or other counts as InteractionCounter objects.
creativeWorkStatus Recommended Set to Deleted for removed posts that still show a placeholder.
isPartOf Recommended The sub-forum or board the thread belongs to.
author.url, digitalSourceType, sharedContent, image, video Recommended Extra context: profile links, whether the content is AI-generated, and any linked media or pages.

Common DiscussionForumPosting schema mistakes

  • Using DiscussionForumPosting on a Q&A thread. Use QAPage when the format is a question with answers.
  • Flattening replies into a list when the page shows them threaded. Nest replies under the comment they answer.
  • Leaving out the time zone on datePublished, which makes post order ambiguous.
  • Marking up a site-written article with a comment section as a forum post.
  • Setting commentCount to only the replies on the current page when the thread runs across several pages.

Linking posts to profiles

Google puts weight on who wrote a post. Give every author a url that points to their profile page, and mark that page up with the ProfilePage schema generator. The profile can carry post counts, follower counts, and the date the account was created, which helps show that the contributor is a real, active member of the community.

Related Tools

Frequently Asked Questions

Should I use DiscussionForumPosting or QAPage?
Use QAPage when the thread is a question with answers, like a support forum where one reply can be accepted as the answer. Use DiscussionForumPosting for open conversation, such as opinions, show-and-tell posts, or news discussion. Do not add both to the same thread.
Does every reply need to be marked up?
Mark up the replies that are visible on the page, nested in the comment property. If the thread is split across several pages, mark up the comments shown on each page and repeat the original post on every page.
Can a blog post with comments use this markup?
Generally no. Google intends it for forum-style sites where users start the threads. Articles written by the site, even with a comment section, should use Article markup.
What if the post is only an image or a video?
That is fine. Google requires one of text, image, or video. A post that is only a photo can use image instead of text, and a video post can use a nested VideoObject.
How do I handle deleted or locked posts?
Use creativeWorkStatus with the value Deleted for posts that have been removed but still show a placeholder. Keep the post in the markup so the reply structure still makes sense.