Quick Answer
Use creator or supported author markup when a video page clearly identifies the real person or organisation responsible for the video. Add interactionStatistic only when you have genuine, maintainable counts for supported actions. Keep the visible page and structured data consistent, validate the markup, and prioritise required VideoObject fields first. Do not invent engagement or expect the added properties to produce an automatic visibility gain.
What Changed in Google's Documentation
Google's Search documentation update for 24 September 2026 added the creator property, noted continued support for author, and clarified supported interaction types for interactionStatistic in VideoObject markup.
This is a documentation change about supported properties. It is not an announcement that every page must migrate from author to creator, or that engagement counts became a new ranking factor.
That distinction is important because schema updates often trigger unnecessary development work. Audit before changing, ideally as part of the wider search engine optimisation process rather than as an isolated schema task.
Creator, Author, and Publisher Are Not Interchangeable Labels
| Property | Practical use |
|---|---|
creator | The person or organisation that created or published the video |
author | A supported alternative for identifying authorship |
publisher | The organisation responsible for publishing the containing work or page, depending on the schema context |
Use the property that truthfully describes the visible content and your publishing model. If a named expert presents and creates a tutorial, a Person may be appropriate. If the video is created by the company studio, an Organization may be clearer.
Do not add a famous executive as creator merely because their name appears on the site. Structured data should describe what users can verify on the page.
What Interaction Statistics Should Represent
interactionStatistic uses an InteractionCounter to describe supported engagement. The count should come from a real source and correspond to the action type being marked up.
The implementation questions are operational:
- Where does the view, like, comment, or share count come from?
- Is that number visible or otherwise defensible?
- How often is it refreshed?
- Does an embedded platform count the same action in the same way?
- What happens if the video is replaced or reuploaded?
A stale count can make the markup less trustworthy. If the team cannot maintain it, omit the optional statistic.
A 13-Field Video Page Audit
Review one important video page using the following fields:
1. page URL; 2. video title; 3. description; 4. thumbnail URL; 5. upload date; 6. duration; 7. content or embed URL; 8. visible creator name; 9. creator type: Person or Organization; 10. creator URL; 11. interaction type; 12. interaction count and source; 13. last validation date and owner.
Required properties and video accessibility come before optional additions. A perfect creator block cannot rescue a missing thumbnail, inaccessible embed, wrong upload date, or video that is not prominent on the page. The serious SEO audit checklist can help teams place these checks alongside crawlability, indexing, templates, and internal links.
A Practical Audit Note
Open Google's Rich Results Test and the live page side by side. Compare the structured data with what a visitor sees.
Check for three common failure patterns:
- Template reuse: every page names the company as creator even when different experts or partners made the videos.
- Inflated interaction: the page combines views from several platforms or uses a lifetime channel total instead of the video total.
- Detached video: the markup describes a video that is hidden, removed, blocked, or not central to the page.
Record URL, issue, visible evidence, schema value, source system, owner, first fix, and retest result. Fix factual mismatches before adding optional properties.
Example Structure
The exact JSON-LD depends on the page, but the relationship should be understandable:
VideoObject identifies the video. creator identifies the responsible Person or Organization. interactionStatistic contains a genuine count tied to a supported interaction type. The visible page supports the same facts.
Do not copy a generic block into production without replacing every value and validating the result.
Where This Helps Beyond Rich Results
Clear creator information can strengthen the page's accountability and entity consistency. It can help users understand who made the video and where to find more from that source. It may also make the page easier for systems to interpret. Useful transcripts, summaries, and supporting explanations should be handled through the same content writing and marketing standards as the rest of the page. The same requirement for clear ownership and accurate supporting content appears in the AI-assisted content quality checklist.
Those are reasons to implement accurate markup. They are not evidence that creator or interactionStatistic will directly improve rankings or cause an AI answer to cite the video.
Tips for Video SEO Teams
- Audit the highest-value original videos first, not every embed on the site.
- Keep creator names and URLs consistent with visible bylines, profiles, and organisation pages.
- Use a transcript or useful surrounding copy when it helps people understand the video.
- Keep thumbnails accessible, descriptive, high quality, and stable.
- Validate after CMS or video-platform changes, not only at launch.
- Remove optional engagement markup if the data source cannot be maintained reliably.
What to Keep an Eye On
Monitor Rich Results Test output, Search Console video indexing and enhancement reports, changes to Google's supported properties, thumbnail and embed accessibility, video impressions and clicks, creator consistency, and whether your update process keeps engagement values current.
FAQs
Is creator required for VideoObject rich results?
No. Google's update documents it as a supported recommended property. Continue to satisfy the required properties first.
Should we replace author with creator everywhere?
Not simply because the documentation changed. Google notes support for author. Change markup when it improves accuracy or consistency, not to follow novelty.
Can we add YouTube view counts to a video embedded on our site?
Only if the count accurately represents that video, uses a supported interaction type, and your process can keep it current. Document the source.
Will the markup improve AI citations?
This update does not create a fixed outcome. Accurate structure may help systems interpret a page, but visibility depends on broader content, technical, quality, and authority signals.
Accuracy Is the Upgrade
The best outcome from this documentation change is not more schema. It is better schema: a real creator, defensible engagement data, accessible video assets, and an owner who will keep the information correct.