Google Updates Forum and Q&A Structured Data With New AI Content Labels

Google quietly updated its Discussion Forum and Q&A Page structured data documentation on March 24, 2026, adding a cluster of new optional properties that give forum and Q&A operators a formal mechanism to declare whether their content was written by humans or generated by machines.

The headline addition is `digitalSourceType`, a property that uses IPTC digital source enumeration values to indicate how content was created. Google supports two values, including `TrainedAlgorithmicMediaDigitalSource` for content produced by a trained model such as a large language model. The second supported value, `AlgorithmicMediaDigitalSource`, covers content created by a simpler algorithmic process, such as an automated reply bot.

Google already uses similar IPTC source type values in its image metadata documentation to identify how images were created, and this update extends that concept to text-based forum and Q&A content. The move signals that the same provenance-labeling framework Google has been building out for visual media is now being applied to the conversational, user-generated content that dominates forums and help communities.

The default behavior carries its own significance for site operators. For sites that publish a mix of human and machine-generated content, the `digitalSourceType` addition provides a structured way to communicate that to Google, and the new properties are optional, with no existing implementations breaking. If a site chooses not to implement the property at all, Google simply treats the content as human-generated by default.

Beyond `digitalSourceType`, the update touched other parts of both markup types. Google added `commentCount` as a recommended property across both documentation pages, letting sites declare the total number of comments on a post or answer even when not all comments appear in the markup. The Q&A Page documentation includes a new formula where `answerCount` plus `commentCount` should equal the total number of replies of any type, giving Google a clearer picture of thread activity on pages where comments are paginated or truncated. The Discussion Forum documentation also expanded its `sharedContent` property, which previously accepted a generic `CreativeWork` type; the updated docs now explicitly list four supported subtypes, including `WebPage` for shared links.

The practical impact on search visibility remains entirely unresolved. Google has not said how it will use the `digitalSourceType` data in its ranking or display systems, and the documentation describes it only as a way to indicate content origin. Whether the property eventually feeds into ranking signals, eligibility for rich results, or content labeling in SERPs is speculation at this point.

The new properties are optional, and no existing implementations will break. Existing forum and Q&A structured data implementations remain valid, and sites that want to adopt the new properties can add them incrementally. That low barrier to entry means there is no urgency to overhaul current markup, but for platforms already wrestling with how to handle AI-generated posts, the property at least provides an official, standardized channel to surface that information to Google before the search engine decides for itself.