Google Clarifies VideoObject Creator Markup: What Publishers Should Review

What changed in the VideoObject guide

The revised documentation explains supported properties and interaction values for video markup.

Google’s September 24 documentation update says the VideoObject guide now includes the `creator` property, with a note that `author` is supported, and clarifies supported interaction types for `interactionStatistic`. This helps implementers understand how to express who created a video and what sort of interaction a statistic represents.

The page shows how VideoObject markup can describe a video, including fields such as name, description, thumbnail, upload date, creator, and interaction data. The markup should represent information that users can verify on the page or through the underlying video service. A statistic is not a place to guess at views or add a marketing claim that the data does not support.

• Google Search Central documentation updatesSeptember 24 change log entry.
• Google Video structured data guideCurrent VideoObject property guidance and examples.

A practical review for existing video pages

Start by checking whether the structured data is complete, valid, and faithful to the visible content.

Video markup checks

1. List the pages with videos that are important to customers, subscribers, or search visibility.
2. Check that the video title, description, thumbnail, upload date, and creator details match the actual page and media asset.
3. If you use `interactionStatistic`, confirm the interaction type and count come from a reliable data source, and are not presented as independently verified if they are not.
4. Validate the rendered structured data after changes, including pages where JavaScript populates markup.
5. Monitor Search Console and search appearance over time, while remembering that valid markup does not guarantee a rich result.

This review is especially useful when a content management system creates schema automatically or when ownership of video data is split between a publisher, agency, and hosting provider. Establish one accountable source for fields such as creator names and view counts.

What not to infer from the change

New documentation detail should not be confused with a promise about ranking or rich result eligibility.

Google’s changelog says it updated the documentation to describe support and clarify interactions. It does not say that adding `creator` or `author` will raise rankings, generate a video carousel, or improve visibility in AI experiences. Those outcomes are not confirmed by this announcement.

The more defensible reason to maintain accurate markup is that it helps systems interpret a page’s structured details and makes the implementation easier to keep consistent. Search teams should make changes when they improve correctness, rather than treating every schema change as an opportunity for a speculative ranking tactic.

Frequently asked questions