Google has expanded its documented support for video creator information and clarified how publishers can describe audience interactions in VideoObject structured data. The change gives video teams a concrete metadata task: identify who created or published each asset and describe its engagement using the appropriate interaction type.
The official Search Central changelog dates the update to September 24, 2026. It describes documentation of support and clarification, rather than announcing a new ranking system or a guaranteed video presentation in search.
What the documentation now specifies
The VideoObject reference lists creator, with author also supported, as a Person or Organization. The identity can include a name and a URL that uniquely identifies it. These appear among recommended properties.
For interactionStatistic, Google documents an InteractionCounter with interactionType and userInteractionCount. WatchAction describes views; the supported list also includes LikeAction, CommentAction and ShareAction. The changelog therefore covers a broader clarification than watch counts alone. The reference notes that interactionStatistic has been recommended since October 2019: it is not a newly invented property.
A small example for an existing video object
The following is an illustrative fragment to merge into a correctly implemented VideoObject, not a complete production object. The publisher, URL and count are placeholders: replace them with verified values for the particular video.
{
"creator": {
"@type": "Organization",
"name": "Example Publisher",
"url": "https://example.com/about"
},
"interactionStatistic": {
"@type": "InteractionCounter",
"interactionType": {
"@type": "WatchAction"
},
"userInteractionCount": 1250
}
}The implementation question is where those values come from. A template that accepts any author string or fills every video with the same count creates an operational problem even if the JSON parses. Decide which content record owns the creator identity and which analytics source owns the metric before connecting them to the page.
Creator identity needs an editorial decision
A presenter, production company, distribution platform and website publisher may be different parties. Teams should decide which identity they are describing for each asset and keep that decision consistent across the visible page and the metadata.
Our recommendation is to maintain a reusable creator record in the CMS, with a stable profile or organization page. That makes attribution easier to review when names change, contributors leave or the same production appears in several articles. Avoid silently assigning every embedded third-party video to the owner of the embedding website.
Existing author implementations deserve an audit rather than an automatic rename. Because Google continues to support author, the useful work is checking that the value describes the correct entity and that templates do not generate contradictory identities.
View counts require a measurement policy
A video can have activity on a hosting platform, an embedded player and social reposts. For editorial accuracy, define the scope of the figure you publish. State internally whether it represents a single asset on one platform or a documented aggregation, and record how often it is refreshed.
Do not label impressions, page visits or estimated reach as video watches merely because those numbers are easier to retrieve. If a reliable count is unavailable, our recommendation is to omit that optional metric until the data pipeline can support it. A stale or ambiguous number adds maintenance work without making the attribution clearer.
What this means for SEO and AI visibility
The practical opportunity is cleaner asset description. A video SEO audit can now ask whether creator identity and engagement metadata are populated consistently across the library, rather than treating every page as an isolated implementation.
For AI Search, the implication is a hypothesis to test: explicit attribution may help downstream systems interpret the relationship between a video and its publisher. This update does not establish that the fields increase AI citations, confer authority or create a new ranking advantage. Treat those outcomes as measurement questions.
Separate technical deployment from performance analysis. Record which templates changed, when they shipped and which video pages received valid values. Then compare indexing and search performance against unchanged pages while accounting for new uploads, promotion and seasonal demand. A rise in traffic after deployment alone cannot identify the cause.
A focused rollout checklist
- Choose a small, representative set of video pages before changing the entire library.
- Check creator attribution against the video credits and the visible page.
- Document the source, scope and refresh schedule of each interaction metric.
- Validate the merged object and inspect the rendered output, including pages with missing data.
- Keep a deployment log so technical changes can be distinguished from editorial and distribution changes.
Google’s update makes the metadata contract clearer. For publishers, the valuable response is a controlled attribution and measurement workflow: accurate identities, defensible counters and a CMS implementation that can be maintained as the video library grows.