DiscussionForumPosting Schema: Appear in Google's Discussions Carousel

In 2023, Google introduced the "Discussions and Forums" carousel in search results — a dedicated section that surfaces community content from Reddit, Quora, Stack Exchange, and other forum-style platforms. By 2025, Google expanded this feature to include any website that uses DiscussionForumPosting schema markup.

This means your own blog's comment section can appear in Google's Discussions carousel alongside Reddit threads and Quora answers. You do not need to be on Reddit. You do not need to post on Quora. You just need the right schema markup on your own site.

I implemented DiscussionForumPosting schema across every blog post in our 52-site network that has comments. Within four weeks, three sites had pages appearing in the Discussions carousel for relevant queries.

What the Discussions Carousel Is

When you search for a question on Google, you will frequently see a dedicated section labeled "Discussions and forums" in the results. This section shows individual comments and posts from community platforms, with the author's avatar, a text snippet, and the source.

Google introduced this carousel because user behavior data showed that people increasingly appended "reddit" to their searches to find real human opinions instead of SEO-optimized content. Rather than losing that traffic to Reddit, Google brought the community content directly into the search results.

The carousel originally pulled exclusively from major platforms: Reddit, Quora, Stack Exchange, and established forums. But Google's documentation now specifies that any page using DiscussionForumPosting schema is eligible for inclusion — including blog comments, community sections, and Q&A pages on your own domain.

Why This Matters for Small Publishers

The Discussions carousel occupies premium real estate in search results. It appears above or between standard organic listings, often with visual formatting (avatars, comment counts) that draws attention. Pages that appear in this carousel get visibility that would otherwise require top-3 organic rankings.

For small publishers, this is an equalizer. Your blog post might rank on page two of organic results, but a well-structured comment on that post can appear in the Discussions carousel on page one — above competitors with higher domain authority.

The carousel also represents a trust signal. Users clicking on Discussions results are looking for authentic perspectives, not marketing copy. If your blog comments provide genuine insights, the traffic from the carousel converts at a higher rate than standard organic traffic.

Implementing DiscussionForumPosting Schema

The schema markup tells Google that a specific section of your page contains discussion-style content — comments, forum posts, or Q&A threads. Here is a complete implementation:

{
  "@context": "https://schema.org",
  "@type": "DiscussionForumPosting",
  "headline": "RE: Build a Calculator Widget That Earns Backlinks on Autopilot",
  "text": "I tried this with a mortgage calculator on my real estate blog. Got 12 embeds in the first month. The key was making the embed code dead simple — one line of HTML.",
  "author": {
    "@type": "Person",
    "name": "Mike R.",
    "url": "https://example.com/profile/mike-r"
  },
  "datePublished": "2026-05-30T14:23:00Z",
  "url": "https://the97dollarlaunch.com/blog/embeddable-widgets/#comment-42",
  "isPartOf": {
    "@type": "DiscussionForumPosting",
    "headline": "Build a Calculator Widget That Earns Backlinks on Autopilot",
    "url": "https://the97dollarlaunch.com/blog/embeddable-widgets/",
    "author": {
      "@type": "Person",
      "name": "J.A. Watte"
    },
    "datePublished": "2026-05-28T09:00:00Z"
  },
  "interactionStatistic": {
    "@type": "InteractionCounter",
    "interactionType": "https://schema.org/LikeAction",
    "userInteractionCount": 7
  }
}

Key Schema Properties

@type: DiscussionForumPosting — This is the signal that tells Google this content is community discussion, not editorial content. Without this type declaration, your comments will not be eligible for the Discussions carousel.

headline — For replies, prefix with "RE:" to indicate it is a response. For top-level posts, use the discussion topic.

text — The actual comment content. Google displays a snippet of this in the carousel, so the first 1-2 sentences should be substantive and directly responsive to the discussion topic.

author — Person schema with at least a name. Including a URL strengthens the author entity signal.

datePublished — ISO 8601 timestamp. Google uses this for freshness signals in the carousel.

isPartOf — Links the comment to the parent discussion, establishing the thread structure.

interactionStatistic — Engagement metrics (likes, upvotes) that influence carousel ranking.

Enabling Quality Comments

Schema markup is necessary but not sufficient. Google evaluates the quality of the discussion content, not just the markup. Comments that are substantive, on-topic, and provide unique perspectives are prioritized over "Great post!" type comments.

To generate carousel-worthy comments on your blog:

Seed the Discussion

After publishing a post, add 2-3 substantive comments that model the type of discussion you want. Frame them as questions, counterpoints, or practical applications:

• "Has anyone tried this with a service-based business? I'm wondering if the ROI differs for local businesses vs. e-commerce."
• "I implemented this last month. Two things I learned that the article doesn't mention: [practical insight]."

Encourage Specific Responses

End blog posts with specific discussion questions rather than generic "Let me know what you think" calls to action. Specific questions generate substantive answers:

• "What's the hardest part of building an embeddable tool for your niche?"
• "If you've tried calculator widgets, what conversion rate are you seeing on the embed page?"

Moderate Actively

Remove spam, low-effort comments, and off-topic posts. Google evaluates the overall quality of your discussion section. A comment thread full of spam will not appear in the carousel regardless of how good the schema markup is.

Technical Implementation for Static Sites

For static sites (like our Eleventy-based network), comments typically use a third-party service like Giscus (GitHub-based), Utterances, or a custom solution. The schema markup needs to be generated alongside the comment display.

The simplest approach is to generate the DiscussionForumPosting schema as part of your page template, dynamically building the JSON-LD block from your comment data:

// In your Eleventy template or build script
const commentSchema = comments.map(comment => ({
  "@context": "https://schema.org",
  "@type": "DiscussionForumPosting",
  "headline": `RE: ${postTitle}`,
  "text": comment.body,
  "author": {
    "@type": "Person",
    "name": comment.author
  },
  "datePublished": comment.date,
  "url": `${postUrl}#comment-${comment.id}`,
  "isPartOf": {
    "@type": "DiscussionForumPosting",
    "headline": postTitle,
    "url": postUrl
  }
}));

Results and Expectations

After implementing DiscussionForumPosting schema across our network:

• Three sites had comments appear in the Discussions carousel within four weeks
• The carousel appearances correlated with queries where the blog post already ranked in the top 20 — the schema did not create rankings from nothing, but it elevated existing visibility
• Click-through rates from Discussions carousel appearances averaged 3-5%, comparable to featured snippets
• Comments that included specific numbers or personal experience performed best in carousel selection

The implementation time was approximately 30 minutes per site for sites with existing comment systems, plus ongoing comment moderation.

The Discussions carousel is still expanding. Google continues to add queries where it appears and broaden the types of content it surfaces. Sites that implement DiscussionForumPosting schema now are building a structural advantage that compounds as the feature grows.

For the complete schema optimization strategy and the full low-budget launch playbook, see The $97 Dollar Launch and The $100 Dollar Network.