Google's September 24, 2026 documentation update gives export teams a reason to check who is credited for a video and where its interaction counts come from. It does not create a new mandatory author field for video indexing. Start with one useful product demonstration, installation guide or factory video, and confirm that its page and data describe the same asset.
For a mainland China team serving overseas customers, this is a content maintenance task with a clear limit: accurate markup helps describe an existing video, but it cannot substitute for a useful page, accessible media or an appropriate viewing experience.
By GRC. Official documentation checked September 28, 2026, Asia/Shanghai. Recommendations below are a proposed workflow, not results from a client website or Search Console account.
What did Google actually change?
Google's update log says it added documentation for creator, noted support for author, and clarified supported interaction types in VideoObject. This records a documentation change, not evidence that a new ranking mechanism began that day. Google Search documentation updates.
VideoObject is structured data used to describe a video. In the current documentation, creator information and interaction statistics are recommended properties. The required properties remain name, thumbnailUrl and uploadDate; meeting requirements does not guarantee a rich result. Google's VideoObject reference.
That distinction changes the work order. Before asking a developer to add fields to every page, ask whether the team can provide reliable values. An optional field with an invented value would undermine the purpose of the update.
Who should be named as the video's creator?
Credit the person or organization that actually created or published the video, as appropriate to the asset. Google supports creator or author; when specifying a person or organization, provide name or alternateName. An accompanying URL should identify that person or organization. Creator field definitions.
Our editorial recommendation is to record the credit decision before editing markup. Check the production brief, publication record or approved credit with the person responsible for the asset. Do not automatically make the salesperson who uploaded the file its creator.
Consider three illustrative situations:
| Video | Credit question to resolve | Useful editorial evidence |
|---|---|---|
| A product demonstration filmed for your company | Which person or organization is responsible for the published video? | Approved credit and a matching identity page. |
| An installation guide supplied by a manufacturer | Who created or published the original, and what use was authorized? | Original source, permission and any agreed attribution. |
| A factory tour made by an outside production team | How should the organization and production contributor be represented? | Production agreement and approved public credit. |
The table is an editorial checklist, not a rule that assigns ownership. If the evidence is unclear, resolve the credit instead of guessing. A company homepage may be useful only when it actually identifies the credited organization. The fact that a video appears on your domain does not settle every attribution question.
Which interaction counts belong in the markup?
Use a count only when you can identify the video, action and source behind it. Google's documented types are WatchAction, LikeAction, CommentAction and ShareAction; each count belongs to its own action. Interaction statistic definitions.
For your internal record, add the source platform or player, asset identifier, retrieval time and counting definition. This is GRC's recommended evidence trail, not a claim that Google requires these extra record fields in JSON-LD.
Suppose an installation video appears on your site and another channel. Your team has a reliable watch count from one player, a like count from the other channel and page views from website analytics. These measure different things. Do not add them together and label the total as watches. If you cannot match a statistic to the exact video and action, omit that optional statistic until you can.
Missing data should remain missing. Zero means an observed zero, not “we could not find the report.” Assign an owner to refresh any counts you use, or choose to leave them out if your workflow cannot maintain them reliably.
Does a product page with a video count as a watch page?
Not automatically. Google describes a watch page as a page whose main purpose is viewing one video. A product page where the video supports other product information is a different kind of page. A web page being indexed also does not mean its video is indexed. Google's video SEO guidance.
Decide around the visitor's task. A buyer comparing specifications may benefit from a short demonstration on the product page. A technician looking for an installation procedure may benefit from a dedicated page where the video is prominent and the title clearly identifies the procedure.
For an illustrative installation guide, a useful viewing page could include the relevant model, the version shown, the video, supporting steps and a link to the matching product. That arrangement gives the reader context for applying the instructions. It is a proposed design, not a statement that those elements alone qualify the page for a search feature.
A factory tour needs an equally clear purpose. It might explain an actual production stage or inspection process. Avoid turning it into a generic collection of claims that the footage cannot support. If a separate viewing page would add no useful experience, do not create one solely to fill out an SEO checklist.
What should a mainland China team check before implementation?
Confirm rights, editing access and the actual audience experience. This method concerns your own website content; it does not depend on buying a new video platform or using a particular overseas AI service.
Choose one asset and prepare this suggested handover record:
| Item | Record before editing | Practical check |
|---|---|---|
| Intended viewer | Buyer, installer or other overseas audience | Does the video answer that person's question? |
| Asset identity | Video title, version and publication date | Are the page and media describing the same video? |
| Creator | Approved name and identifying page | Can the team substantiate the credit? |
| Statistics | Action, source and retrieval time, or unavailable | Are different measures kept separate? |
| Viewing page | URL and its primary purpose | Is the video central or supporting content? |
| Resources | Thumbnail, player and media locations | Can the required resources be reached? |
Google's guidance emphasizes accessible video resources and stable URLs. Inspect the page, thumbnail and relevant player or media separately; loading one does not prove that all work. Video resource and crawling guidance.
For mainland teams, your own office playback test and an overseas customer's playback experience are separate checks. Access to an external dashboard, account permissions and network conditions also need confirmation in your environment. Do not infer them from this article or from a successful documentation request.
Ask the website maintainer to identify what currently generates the video markup before changing it. A theme, app or content integration may already be responsible. Review one proposed output against the real asset and visible page. This article intentionally supplies no example viewing counts or ready-to-paste identity values that could be mistaken for your data.
How will you know whether the change helped?
Separate correctness from business performance. First establish that the published page contains the intended values, the video works and the markup can be parsed. If your team has authorized access to relevant search tools, inspect indexing and video visibility separately. Those checks answer different questions.
For a small pilot, record the date, selected page and exact changes. Keep other major page changes visible in the same record. Later, compare actual search observations and relevant customer behavior where measurement exists; without a baseline, report the observations rather than claiming uplift.
A passed technical check does not establish rankings, GEO citations or inquiry growth. Better evidence and a useful viewing experience are worthwhile deliverables in their own right. Any commercial result remains to be tested.
For the broader content process, GRC's guide to creating a fact sheet before using AI to write offers a related starting point. Use a separate video record for credits and statistics; product facts cannot supply missing video evidence.
For website content and search implementation support, see GRC's services. Discuss your project with one video page, the original asset information and the data you can substantiate. That gives the scope discussion a concrete starting point; any implementation and measurement work is agreed separately.
