What changed in Google’s documentation
Google’s Search Central update log records a September 24 clarification to its VideoObject structured-data documentation. The page now documents the creator property, notes support for author, and explains which interaction types are supported for interactionStatistic. This is a documentation update that makes existing guidance clearer; it is not a new video ranking factor announcement or a promise that a marked-up page will gain a special search display.
VideoObject describes a video and can help Google understand details such as its name, thumbnail, upload date and creator. The structured data belongs on a page where the video can actually be watched. Publishers should use the properties that accurately describe their content instead of adding every optional field simply because the vocabulary permits it.
Creator and author identify who made the video
Google now documents creator, with support for author, as a recommended way to identify the person or organisation that created or published a video. The property should reflect the real creator or publisher and use a corresponding name and, where appropriate, a profile URL. A publisher should not assign a famous creator merely because that person appears in, comments on or hosts the video.
This is a useful reminder to align markup with the visible page. If the page credits a production team or company, structured data should not contradict it. Where multiple people contributed, use the representation that is accurate and supported by the content. Good metadata clarifies provenance; it does not replace a genuine credit or establish rights to use the video.
Use interactionStatistic only for real counts
Google’s documentation describes interactionStatistic as an optional way to provide user statistics for a video. It lists WatchAction, LikeAction, CommentAction and ShareAction as supported interaction types. The accompanying count should come from an actual and clearly defined source. Do not estimate views, convert page visits into watch counts or insert a number because it makes a result look more complete.
When a platform exposes counts with different definitions, document what is being counted and keep the page and markup consistent. Counts may change as the video receives interactions, so a static value can become stale. If there is no reliable source or maintenance process, omitting the property is safer than publishing a misleading statistic.
A practical VideoObject review
Start with the basics: the page should offer a real, playable video; the title and description should match the visible content; the thumbnail should be crawlable; and uploadDate should reflect the original publication time with an appropriate timezone. Google recommends a direct contentUrl when available, or an embedUrl for the player. These URLs should point to the media or player, not just repeat the page address.
Then check creator or author, duration and any interaction statistics against the page and source system. Validate JSON-LD syntax, test the URL with Google’s available inspection tools and inspect rendered output after deployment. A valid schema graph can still describe a page that does not meet Google’s eligibility and quality guidelines.
Structured data is descriptive, not a ranking promise
Google says structured data can help it understand content and that eligible videos may appear in different search experiences. Eligibility does not guarantee that a rich result will show, and the documentation change does not promise a ranking increase. Search systems make their own decisions based on page quality, relevance, technical accessibility and feature availability.
For publishers, the best use of schema is accurate description at a manageable maintenance cost. Add properties when the information is present and trustworthy, keep the video prominent on its watch page, and remove stale values. The September update gives clearer guidance for creator identity and interaction types; the editorial and technical responsibility remains with the site owner.
Sources & further reading
Have a factual correction or a source to suggest? Contact the editorial desk.
