Google has enhanced its structured data support for forum and Q&A pages, enabling webmasters to better indicate reply threads, quoted content, and whether content is generated by humans or algorithms. These changes aim to improve how Google interprets complex discussion formats and user-generated content.

Overview of the Update

The recent updates to Google’s structured data documentation focus on two main schema types: QAPage and DiscussionForumPosting. For QAPage schemas, new properties such as commentCount and digitalSourceType have been introduced, while DiscussionForumPosting now supports sharedContent alongside the same comment tracking and digital source classification.

Improved Reply Thread Signaling

Previously, signaling the total amount of interaction on Q&A and forum posts was limited. With the addition of commentCount, site owners can specify the total number of comments on questions, answers, or individual comments, even if the entire thread is not fully marked up. This offers a more granular representation of discussion volume.

Google recommends that answerCount plus commentCount should sum to the total number of replies across all forms within a thread. This clarifies for search engines exactly how many interactions a post has received, enhancing the accuracy of rich results.

Expert Insight

“By enabling detailed counts of answers and comments, Google empowers community platforms to better showcase active discussions and user engagement,” commented Emma Lawson, a digital marketing analyst specializing in structured data strategies.

Distinguishing Human and Automated Content

One of the most significant updates is the introduction of the digitalSourceType property. This attribute allows content creators to specify whether a post or comment is human-generated or produced by an automated system. Two distinct values support this classification:

• TrainedAlgorithmicMediaDigitalSource for content generated by advanced models such as large language models.
• AlgorithmicMediaDigitalSource for content generated by simpler forms of automation.

If the property is omitted, Google assumes the content is human-generated by default. This advancement enables better trust signals and transparency about content origins, which is critical given the rise of AI-produced text in community environments.

Marking Shared Content in Forums

DiscussionForumPosting schemas now accept the new sharedContent property. This allows site owners to indicate the main item being shared within a forum post, such as a webpage link, an image, a video, or another referenced post or comment. Google supports several schema types for this attribute, including WebPage, ImageObject, VideoObject, and references to other forum posts or comments.

This capability is especially beneficial for forum-heavy sites and UGC platforms that often include reposts, quotes, or shared media items within discussions. Accurately marking shared content improves Google’s understanding of the post’s context and relevance.

Benefits for Community and Support Sites

Websites hosting support communities, forums, and Q&A sections stand to gain significantly from these new structured data features. By providing Google with better signals about replies, source type, and shared content, these platforms can enhance how their content is displayed in search results and improve indexing accuracy.

“This update allows support forums and knowledge bases to represent the true structure of their conversations, reducing misinterpretations by search engines,” said Michael Cheng, a SEO consultant for large-scale community websites.

Implementation Considerations

Site owners should carefully audit their existing schema implementations to incorporate commentCount, digitalSourceType, and sharedContent where applicable. Accurate counts and content origin identification will help align with Google’s current understanding and reduce risks of misclassification.

Furthermore, developers should ensure that the use of digitalSourceType reflects the actual content generation processes transparently, which contributes to user trust and compliance with emerging guidelines around AI disclosure.

Examples of Markup Usage

Consider a Q&A page discussing a product where multiple answers and comments exist:

{
“@context”: “https://schema.org”,
“@type”: “QAPage”,
“mainEntity”: {
“@type”: “Question”,
“name”: “How to improve battery life?”,
“answerCount”: 3,
“commentCount”: 5,
“acceptedAnswer”: {},
“digitalSourceType”: “HumanGenerated”
}
}

For a forum post sharing an image with AI-generated comments:

{
“@context”: “https://schema.org”,
“@type”: “DiscussionForumPosting”,
“text”: “Check out this diagram”,
“sharedContent”: {
“@type”: “ImageObject”,
“contentUrl”: “https://example.com/image.jpg”
},
“commentCount”: 2,
“digitalSourceType”: “AlgorithmicMediaDigitalSource”
}

Where to Learn More

Detailed documentation on these schema properties is available through Google’s official structured data guidelines and schema.org references. Developers can also leverage community forums and schema testing tools to validate implementations.

For more information, visit https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data and https://schema.org/QAPage.

Conclusion

The expanded structured data support for forums and Q&A pages offers website owners enhanced control over how user interactions and content origins are communicated to search engines. By adopting these updates, platforms can improve search result visibility and better serve users through clearer indexing and display of complex discussions.