On September 24, 2026, Google's documentation updates log recorded that the creator property is now documented for VideoObject, that author is also supported, and that interactionStatistic lists four interaction types: WatchAction, LikeAction, CommentAction and ShareAction.
This applies if you host videos on your own watch pages and already publish, or plan to publish, VideoObject markup. Nothing becomes mandatory. Google's required properties are still name, thumbnailUrl and uploadDate, and both creator and interactionStatistic are recommended, not required.
So, the first step is to leave the required core exactly as it is. Then add a creator and counts only where the page can back them up. The creator should be named on the page or on a linked profile, and each count should come from your current analytics and match the total visitors can see.
What Google documented on September 24, 2026
Google's documentation updates page records the change in one line: "Added the creator property (noting support for author) and updated interactionStatistic to document supported interaction types in the VideoObject structured data documentation." Google gives the purpose as documenting support for creator and author, and clarifying the supported interaction types for interactionStatistic.
The matching video structured data documentation was updated the same day. It describes the Google Search video feature, which depends on the video sitting on a watch page, meaning a page where a visitor can actually watch it.
Google's entry says what the feature documentation now covers, and a valid VideoObject does not guarantee a video rich result.
Google also keeps interactionStatistic as its recommended way to describe counts. Its documentation has recommended it instead of the older interactionCount since October 2019, and Google says it continues to support interactionCount. If your current markup uses interactionCount, it still works, and you can move to interactionStatistic when you next edit the template.
Add creator, or keep author
The creator property names the person or organization that created or published the video. Google lists creator.name and creator.url as recommended whenever you use creator, and author as a supported alternative. If your markup already uses author for the same person, Google says that is also supported, so you do not have to rename it. Pick one property per video and use it consistently across your watch pages.
The values should match what a visitor can see. Put the creator's name on the page, or link to a creator profile that shows it, and point creator.url at a page that identifies that person or organization. A profile page, a team page or an about page all work, as long as the URL resolves and the page says who they are.
Use Person when an individual made the video and Organization when a business or channel published it. If a video has no clear creator, for example an archive clip of unknown origin, leave the property out. An accurate page with fewer fields is better than a complete one that names the wrong person.
For vocabulary, schema.org's creator definition describes the creator of a creative work, and VideoObject is the type that carries it. Schema.org validity and Google feature support are separate questions: a property can be valid vocabulary without a search feature behind it. For the wider set of types you might combine with video, see the guide to types of schema markup.
The four interaction types in interactionStatistic
Each interactionStatistic entry is an InteractionCounter that pairs an interactionType with a userInteractionCount. Google documents four types: WatchAction for the number of times the video was watched, LikeAction for likes or upvotes, CommentAction for comments, and ShareAction for reshares. Google lists interactionStatistic and its two inner properties as recommended if applicable, so a video with no like button simply has no LikeAction entry.
You do not need all four. Add the ones your site actually tracks and shows. A watch page with a play counter and a comment section can describe two interactions, and that is a complete answer.
Each count is a whole number for that single video. Schema.org defines InteractionCounter as a summary of how users interacted with a creative work, and the four actions are vocabulary terms in their own right: WatchAction, LikeAction, CommentAction and ShareAction.
Before and after: a VideoObject with creator and counts
The first block shows a baseline VideoObject as a site might have written it before this documentation update, with author and no counts. Everything in it is teaching code: the page, the person and the numbers are fictional, and the URLs use the reserved example.com domain. Replace each value with the real facts for your own video, and never paste the example into a live page as it stands.
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "How to Plan a Small Garden",
"description": "A fictional guide to planning a small home garden.",
"thumbnailUrl": [
"https://example.com/images/small-garden-video.jpg"
],
"uploadDate": "2026-09-20T10:00:00-05:00",
"duration": "PT8M12S",
"contentUrl": "https://example.com/videos/small-garden.mp4",
"author": {
"@type": "Person",
"name": "Mara Example",
"url": "https://example.com/authors/mara-example"
}
}The second block adds creator and the four interaction types. The counts are invented for the demonstration, so replace them with the current totals from your own system, and delete any entry you do not track. The required name, thumbnailUrl and uploadDate stay exactly where they were.
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "How to Plan a Small Garden",
"description": "A fictional guide to planning a small home garden.",
"thumbnailUrl": [
"https://example.com/images/small-garden-video.jpg"
],
"uploadDate": "2026-09-20T10:00:00-05:00",
"duration": "PT8M12S",
"contentUrl": "https://example.com/videos/small-garden.mp4",
"creator": {
"@type": "Person",
"name": "Mara Example",
"url": "https://example.com/authors/mara-example"
},
"interactionStatistic": [
{
"@type": "InteractionCounter",
"interactionType": { "@type": "WatchAction" },
"userInteractionCount": 1842
},
{
"@type": "InteractionCounter",
"interactionType": { "@type": "LikeAction" },
"userInteractionCount": 96
},
{
"@type": "InteractionCounter",
"interactionType": { "@type": "CommentAction" },
"userInteractionCount": 18
},
{
"@type": "InteractionCounter",
"interactionType": { "@type": "ShareAction" },
"userInteractionCount": 42
}
]
}Google also lists contentUrl, description, duration and embedUrl as recommended for this feature, with embedUrl as the alternative when you have no direct file URL. For more copyable patterns, the JSON-LD schema examples guide has code for other types, and the format itself is defined in the W3C JSON-LD 1.1 Recommendation.
Keep counts accurate and current
A count is a factual claim about one video, so it should come from the system that actually records it: your site's analytics, your player's play counter, or the comment and like totals your own pages display. Update the markup when those totals change. A template that reads the live number each time the page is built keeps the markup and the visible total in step, while a number typed in by hand tends to go stale.
Google's structured data policies, updated July 10, 2026, say markup should represent content visitors can see. In practice, do not mark up statistics that a visitor cannot reasonably tie to this video, and do not add a count just because the video has views, likes or shares somewhere else.

If your video is a YouTube embed, the figures that belong to it are the video's own statistics. YouTube's Data API documents viewCount, likeCount and commentCount for a video resource, and the channel owner can read them. YouTube's embedding help covers the iframe itself. Use those real totals only if your watch page shows them and you keep them updated. If your page shows no verified total, leave interactionStatistic out rather than guessing.
Make the video markup readable for Bing and AI search
Bing's structured data documentation says publishers can use Schema.org in JSON-LD, so the same block serves both Google and Bing. Microsoft says Copilot web search sends generated queries to Bing, which makes Bing's documentation the relevant reference for that path.
Yandex documents its own video markup with interactionCount for comments, likes and views. That counter format differs from Google's interactionStatistic example, so check Yandex's page before reusing Google's block there.
To let ChatGPT Search and Perplexity reach the watch page, allow OAI-SearchBot (OpenAI's crawler documentation) and PerplexityBot (Perplexity's crawler documentation) in robots.txt. For the full comparison, see whether AI systems use schema markup.
Test the markup and watch the reports
Test the page after you edit it, and again after you change how the counts are produced. The steps run in this order:
- Add
creatorand, where applicable, one or moreinteractionStatisticobjects. - Make sure each value matches the visible page and the current video data.
- Test the live URL or pasted code in Google's Rich Results Test, and fix any
VideoObjecterrors before publishing. - In Search Console, review the Video indexing report and the Video rich result report.
- Use URL Inspection on the indexed version of an individual video page.
- Allow time for Google to recrawl the updated page.

For syntax and vocabulary, paste your block into the Schema Nova schema validator, which tells you whether the JSON parses and the types and properties are well formed. Google's Rich Results Test help explains the Google-specific side. A pass means the markup meets Google's checks for the feature. It does not guarantee a rich result, indexing, a higher position or an appearance on every Google surface.
The Video indexing report and Google's video best practices cover why a video page may not be indexed at all, which is a separate question from whether the markup is valid.
Questions people ask
Is creator required for Google video results?
No. Google lists creator as recommended for its video feature, along with creator.name and creator.url when you use it. The required properties are still name, thumbnailUrl and uploadDate.
Can I use author instead of creator?
Yes. Google's documentation notes support for author alongside the new creator entry. Use one of them for the same person on a given video, and keep the name and URL consistent with the page.
Should I use interactionCount or interactionStatistic?
Google recommends interactionStatistic instead of the older interactionCount, and says it continues to support interactionCount. Use interactionStatistic for new markup and move older templates when you next edit them.
Do the counts need to appear on the page?
Google's structured data policies say markup should represent content visitors can see, so the safest pattern is a visible total that your markup mirrors. If the page shows no total for a video, omit that count.
Does adding these fields guarantee a video rich result?
No. A passing Rich Results Test means the markup meets Google's checks for the feature, and Google decides whether to show a result. The change documented on September 24, 2026 does not alter that.
