Google Adds a Creator Property to VideoObject Structured Data

Google updated its VideoObject structured data documentation on 24 September 2026, adding a creator property and clarifying which interaction types interactionStatistic supports. Both changes are documented directly in the Search Central changelog, not inferred from third-party reporting.

What changed

creator property (new). Google's changelog describes it as adding "the creator property (noting support for author)". In the docs, creator expects a Person or Organization value and represents "the person or organization that created or published the video" — for example:

"creator": {
  "@type": "Organization",
  "name": "Google Netherlands",
  "url": "https://www.example.com"
}

author continues to work as an alias, so nothing already marked up with author needs to change. This is a documentation clarification of existing support rather than a brand-new requirement.

interactionStatistic (clarified). Google's docs now spell out exactly which interactionType values it recognises inside interactionStatistic:

• WatchAction — number of times the video has been watched
• LikeAction — number of likes or upvotes
• CommentAction — number of comments
• ShareAction — number of reshares

Google's own guidance: "While we continue to support interactionCount, we recommend interactionStatistic moving forward" — so sites still using the older interactionCount field should plan to migrate, even though it isn't being deprecated outright.

The Microdata equivalent works the same way, nesting creator as its own itemscope:

<span itemprop="creator" itemscope itemtype="https://schema.org/Organization">
  <meta itemprop="name" content="Google Netherlands" />
  <link itemprop="url" href="https://www.example.com" />
</span>

Why it matters

Neither field is required for basic video rich results, but both feed Google's understanding of a video's provenance and engagement — inputs that plausibly matter more now that video content is being pulled into AI Overviews and multimodal Search results, where attribution and popularity signals help Google decide what to surface. Sites with a video content library (product demos, how-tos, embedded YouTube) get a documented, low-effort way to add creator attribution and standardise engagement counts using types Google explicitly says it reads.

Attribution matters more than it used to for a specific reason: as more video appears inside AI-generated answers rather than a traditional blue-link result, the visible path back to "who made this" gets thinner. A user watching a clip surfaced inside an AI Overview may never see the source site's branding the way they would scrolling a normal results page. Explicit creator markup gives Google a structured signal to carry that attribution through, rather than relying on it being inferred from page context.

The interactionStatistic clarification is smaller in scope but removes a genuine ambiguity. Before this update, sites had schema.org's general InteractionCounter type to work with but no confirmation of which specific interactionType values Google's video features actually read. Marking up a fifth type Google doesn't recognise — say, a custom "download" count — would have silently done nothing. Now there's a documented list of four to target, which makes markup auditing far more precise: sites can check their existing interactionStatistic blocks against these four values and know immediately which entries are wasted effort.

What to do

• Add creator (or confirm author is already present) to VideoObject markup where a clear creator or publisher exists — this matters most for licensed, syndicated or multi-author video content where "who made this" isn't obvious from the page alone.
• If using the older interactionCount field, migrate to interactionStatistic with one of the four supported interactionType values: WatchAction, LikeAction, CommentAction or ShareAction.
• Drop any interactionStatistic entries using unsupported interaction types — they were never being read, and cleaning them up simplifies the markup without losing anything.
• Validate changes with the Rich Results Test before deploying sitewide.
• Re-check video markup periodically against the Search Central changelog — VideoObject has had several incremental property additions this year, and each one is opt-in until you add it.

This is also a reminder that VideoObject markup rewards periodic re-auditing rather than a one-time setup. Structured data guidance for established schema types doesn't stand still — Google adds properties, deprecates others, and clarifies ambiguous fields as its own understanding of what's useful evolves. A VideoObject block written two years ago and never revisited is likely missing several fields Google now documents, not because it was wrong at the time, but because the target has moved.

Sources

• Google Search Central: Latest documentation updates — September 24, 2026
• Google Search Central: Video (VideoObject) structured data documentation