Google updated its VideoObject documentation on September 24, 2026 to describe creator information and clarify supported interaction statistics. For a WordPress site with genuine video pages, the useful task is to map verified video metadata into the existing schema output. It is not a reason to add invented view counts or mark an ordinary article as a video watch page.
The change is documented in Google's Search documentation updates. It is a documentation update, not a promise that adding these properties will improve rankings.
Start With the Video and Its Owner
Pick one page containing a real video and identify the person or organization responsible for creating or publishing it. Separate that identity from the software hosting the file, the author of the surrounding article, and the agency maintaining the website. Those roles may overlap, but do not assume they are identical.
Google's VideoObject reference supports creator or author as a Person or Organization. Use the identity supported by the actual video and site records. Avoid competing schema plugins emitting contradictory owners for the same video.
Treat Engagement Counts as Data, Not Decoration
Google documents WatchAction, LikeAction, CommentAction, and ShareAction for the supported interaction types. A page view is not automatically a video watch, and a social post's reactions are not automatically reactions to the embedded video.
Build a mapping before adding counts:
| Field you have |
Question before publishing |
| Player views |
Does this measure the same video and a defined watch event? |
| Likes |
Is the count tied to the video rather than its surrounding post? |
| Comments |
Does the source include unrelated page comments? |
| Shares |
Is the metric a real reshare count or only a button click? |
If no reliable corresponding statistic exists, omit that optional statistic. Do not populate it with zero as a placeholder or copy a number from a different platform asset. Document the source, retrieval time, and update process for any metric you do publish.
Explanatory test plan. Record your own observations; no customer results are shown.
Add Metadata Through One Responsible Component
Inspect the rendered page for existing JSON-LD before editing. Determine whether a video plugin, SEO plugin, theme, or custom code owns the VideoObject. Use its supported integration method instead of adding a second full object to every page through a global header field.
A developer should preserve the existing required metadata and make the smallest change to the correct object. Ensure the creator's name and URL are accurate, counts are integers of the intended meaning, and escaping does not turn values into malformed JSON. Keep a copy of the previous output for comparison.
For agencies managing several sites, create a small metadata worksheet per video: public page, video identity, schema owner, creator source, metric source, and reviewer. This is more dependable than assuming every video embedded from the same provider belongs to the same creator.
Check the Watch Page Separately
Google's video SEO guide explains that the page, player, media file, and thumbnail have different roles. Make sure the visible video can be found and used, its thumbnail represents it, and the page is appropriate for the intended video search experience.
Do not confuse a platform-property performance report with the indexability of your own WordPress page. The social and video reporting guide covers that separate source of audience evidence.
Validate One Page Before Expanding
Run the affected URL through Google's Rich Results Test, inspect the emitted metadata, and fix critical errors. Then check the deployed document, not only the editor preview. Use Search Console URL Inspection and available video reports to monitor what Google later observes.
Record the validation result and any unresolved eligibility issue. Valid structured data does not guarantee a video result or indexing. If a plugin update later changes the schema output, repeat the small-page check before applying the same configuration across the library.
HandL WP can help review conflicting video-schema output, including which component should own it and whether the published statistics match real source data.
Sources checked September 26, 2026. Visuals and examples are explanatory, not customer measurements.