On September 24, Google updated its video structured data documentation. It added the creator property and clarified which interaction types the interactionStatistic property supports. If your nonprofit sits on a library of unmarked video, the takeaway is simple: mark up the videos you already have, and tell Google who made them.
The short version
- Google's September 24, 2026 changelog added the creator property to VideoObject structured data and documented the interaction types interactionStatistic accepts. Both are recommended, not required.
- The required VideoObject properties are still only three: name, thumbnailUrl, and uploadDate. Most nonprofit pages supply none of them.
- VideoObject markup is what makes a video eligible for video rich results, key moments, and the LIVE badge in Google Search.
- The markup only counts on a page where the video actually plays. A link to a video that lives somewhere else does not qualify.
- Creator and author attribution matters more now that AI-generated answers are assembled from sources, and provenance is part of what those systems weigh.
What actually changed on September 24
The change is small on paper and useful in practice: Google now documents how to name the creator of a video and how to report engagement on it.
The changelog entry reads that Google "added the creator property (noting support for author) and updated interactionStatistic to document supported interaction types" in the VideoObject documentation. The creator property accepts a Person or an Organization, with a name (or alternateName) and an optional url pointing to a profile or homepage. The interactionStatistic property uses an InteractionCounter, which pairs an interactionType, such as WatchAction, LikeAction, CommentAction, or ShareAction, with a userInteractionCount.
Both sit under recommended properties. Nothing breaks if you skip them. But recommended is not the same as optional-and-ignored. These are signals you can now send deliberately, and the fact that Google bothered to document them in this cycle tells you where attention is going.
Why this matters for nonprofits specifically
Nonprofits produce more video than almost any other content type, and mark up almost none of it.
Think about what a typical mission-driven org publishes in a year: the gala recap, the program explainer, three or four testimonial clips, the annual impact film, a grant-funded documentary short. Most of it gets embedded as a raw YouTube iframe on a program page and left there. No VideoObject block, no thumbnail declared to Google, no upload date, no creator.
When I audited a legal-services nonprofit's site earlier this year, it had more than 40 videos embedded across program and impact pages, and not a single VideoObject block anywhere on the domain. Every one of those pages was leaving video rich results on the table. Worse, Google had no structured way to know that the organization, and not some random re-uploader, was the source of the footage. On a results page increasingly stitched together from sources, that provenance is cheap to provide and expensive to leave blank.
The markup that earns video rich results
You need three required fields to be eligible, and a handful of recommended ones to be competitive.
The required properties are name, thumbnailUrl, and uploadDate. Here is a VideoObject block that covers the requirements and adds the creator and interactionStatistic properties Google just documented:
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "2026 Scholarship Program: Maria's Story",
"description": "How a first-generation college student used the fund to finish her degree.",
"thumbnailUrl": ["https://example.org/thumbs/marias-story.jpg"],
"uploadDate": "2026-09-15T08:00:00-05:00",
"duration": "PT3M12S",
"contentUrl": "https://example.org/video/marias-story.mp4",
"embedUrl": "https://www.youtube.com/embed/XXXXXXXX",
"creator": {
"@type": "Organization",
"name": "Example Community Foundation",
"url": "https://example.org"
},
"interactionStatistic": {
"@type": "InteractionCounter",
"interactionType": { "@type": "WatchAction" },
"userInteractionCount": 12483
}
}
Name, thumbnailUrl, and uploadDate do the eligibility work. Duration and the content and embed URLs help Google surface the right clip. The creator block names your organization as the source, and the interactionStatistic block reports real engagement. If you want the fuller picture of how JSON-LD feeds search and AI answers, I wrote about that in schema markup for AI search.
The mistake that quietly wastes the effort
Google will ignore your markup if the video is not watchable on the page that carries it.
Google's guidance is blunt on this: "VideoObject structured data must be added to a page where users can watch the video." I see the same pattern on nonprofit sites constantly. There is a nicely designed page with a "Watch our story" button, the button links out to a separate YouTube page, and the VideoObject markup sits on the landing page that has no player on it. That markup does nothing. Put the embed and the structured data on the same page, so the thing you describe is the thing a visitor can actually play.
How to prioritize when you have 200 clips
Do not mark up everything. Mark up the videos that sit on pages with a job.
The clips worth your time are the ones attached to intent: the explainer on or near your donation page, the testimonial on a program page that drives inquiries, the annual impact film on your about or impact page, the recording of a recurring signature event. Skip the b-roll, the unlisted board-meeting archive, and the fifteen-second social cutdowns that live nowhere permanent. The goal is not markup coverage for its own sake, it is making your highest-intent pages richer in search and more quotable to the systems that now summarize them. The same discipline applies to earning AI citations: a few well-structured pages beat a hundred thin ones.
What this does not cover
This is about VideoObject markup on pages you control. It is not about ranking inside YouTube's own search, which is a separate system with its own signals. It does not get into video sitemaps, which are worth doing once you are marking up video at volume but are a different task. It does not cover where to host your video, and it does not cover captions and transcripts. Those last two are accessibility work first, and they happen to help search second. If accessibility is the gap, that is its own 30-minute audit, not a schema project.
Frequently asked questions
Do we need video structured data if our videos are hosted on YouTube?
Yes, if you embed them on your own site. YouTube handles its own listings inside YouTube. The VideoObject markup goes on your page, where the video plays, and it is what makes your page eligible for video rich results in Google Search. The two are separate, and your own site is the one you control.
Is the creator property required now?
No. It is a recommended property, not a required one. The required fields are still name, thumbnailUrl, and uploadDate. Creator is a signal you can choose to send, and after the September 24 update there is documented support for sending it cleanly.
Will marking up video get us into AI Overviews or AI Mode?
No single property is a switch that turns that on. Clean VideoObject markup makes your video eligible for rich results and gives AI systems structured provenance about who made it. That improves your odds of being surfaced and cited. It does not guarantee placement, and anyone who tells you otherwise is selling something.
How many interactionStatistic entries should we include?
You can report more than one interaction type, for example watches and likes, each as its own InteractionCounter. Use real numbers you can stand behind. Inventing engagement counts is the kind of thing a spam update eventually catches, and it is not worth the risk for a recommended property.
If you want me to audit which of your videos are actually eligible for rich results, and write the JSON-LD for the ones that sit on pages with a job, book a 20-minute read-out and I will show you the gaps on your own site.