Google now documents creator information for video structured data, giving businesses a clearer way to connect a video with the person or organization behind it. The September 24, 2026 update adds the creator property to Google’s VideoObject guidance, notes that author is also supported, and clarifies which engagement statistics Google accepts.

This is not a shortcut to rankings. It is a useful identity and context improvement for websites that publish original videos. When the markup is accurate, Google can more easily understand what the video is, where it can be watched, who created it, and what its engagement numbers represent.

What changed in Google’s VideoObject guidance?

Google’s Search documentation changelog identifies two changes:

• Google added documentation for the creator property and confirmed support for author.
• Google clarified the supported interaction types inside interactionStatistic.

The creator can be a Person or an Organization. Google asks for a name or alternate name and recommends a URL that uniquely identifies that creator, such as an author profile, About page, or organization homepage.

For interactions, Google documents four supported action types:

• WatchAction for views
• LikeAction for likes or upvotes
• CommentAction for comments
• ShareAction for reshares

The change is documentation, not a promise of a new rich-result layout. Google does not guarantee that valid structured data will appear as a special search feature.

What is VideoObject structured data?

VideoObject is Schema.org markup that describes a video on a webpage in a machine-readable format. Google can use it to understand details such as the video name, description, thumbnail, upload date, duration, file or embed location, creator, and engagement statistics.

Google says video structured data can make a video easier to find and can influence the information shown in video results. Eligible videos may appear in the main search results, Video mode, Google Images, and Google Discover.

The markup belongs on a watch page where the video is the main content. Adding a hidden or unrelated VideoObject to every page is not a sound SEO strategy.

Why creator attribution matters for business video

It connects the asset to a real source

A product demonstration, training video, interview, workshop replay, or customer education video is more useful when its source is clear. Creator markup gives search systems an explicit relationship between the video and the person or organization responsible for it.

It supports consistent brand identity

A business may publish videos on its website, YouTube, social media, course platform, and help center. Consistent organization names and URLs reduce ambiguity. The creator URL should point to a stable page that accurately represents the same entity named in the markup.

It helps separate the creator from the subject

A video about a customer, product, or event is not necessarily created by that subject. Structured data should identify the person or organization that created or published the video, not whichever name seems most marketable.

A practical VideoObject creator example

The following simplified JSON-LD example describes a small-business tutorial video and attributes it to the organization that produced it:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "How to Photograph Products for an Online Store",
  "description": "A practical product photography walkthrough for small retailers.",
  "thumbnailUrl": [
    "https://example.com/images/product-photo-video-16x9.jpg"
  ],
  "uploadDate": "2026-09-28T09:00:00-04:00",
  "duration": "PT6M42S",
  "embedUrl": "https://example.com/video/product-photography/embed",
  "creator": {
    "@type": "Organization",
    "name": "Example Business Studio",
    "url": "https://example.com/about/"
  },
  "interactionStatistic": [
    {
      "@type": "InteractionCounter",
      "interactionType": { "@type": "WatchAction" },
      "userInteractionCount": 1842
    },
    {
      "@type": "InteractionCounter",
      "interactionType": { "@type": "LikeAction" },
      "userInteractionCount": 96
    }
  ]
}
</script>

Use values that are visible, accurate, and supported by the page or video platform. Do not invent view counts, copy engagement from an unrelated social post, or identify a creator that did not produce or publish the video.

Creator or author: which property should you use?

Google documents support for both creator and author. For new video markup, creator is a clear choice because it directly describes the entity that created or published the video. An existing system that uses author does not need to panic simply because the newer documentation highlights creator.

Consistency matters more than duplicating every possible property. Choose the property your publishing system can populate accurately, use a stable entity type, and keep the name and URL aligned with the visible page.

How to add interaction statistics correctly

Match each number to one action

A view count should use WatchAction. Likes should use LikeAction, comments should use CommentAction, and reshares should use ShareAction. Do not combine several measurements into one total.

Use integers and current data

The userInteractionCount value is an integer. If a platform displays an abbreviated count such as 1.8K, use the accurate underlying number when it is available rather than guessing.

Only report statistics that belong to the video

Do not place the company’s total followers, total channel views, or website traffic inside a single video’s interactionStatistic. The number must describe the interaction performed on that video.

Do not let stale counts break the workflow

Engagement properties are recommended information, not an excuse to build a fragile hourly update system. If the website cannot maintain accurate counts, publish the core video metadata first and add statistics when the data pipeline is reliable.

The metadata businesses should prioritize first

Creator and engagement fields are useful, but they come after the essentials. A solid VideoObject implementation should start with:

• Name: a specific title that matches the visible video.
• Description: an accurate summary rather than keyword stuffing.
• Thumbnail: a crawlable, stable image URL with useful framing.
• Upload date: the real publication date with a timezone.
• Duration: the video’s actual ISO 8601 duration.
• Content or embed URL: a valid location Google can access.
• Creator: the real person or organization responsible for the video.

If Google cannot fetch the page, thumbnail, embed, or actual video bytes, an impressive block of schema will not solve the discovery problem.

Video SEO mistakes to avoid

Marking up a video that is not prominent

Google recommends dedicated watch pages where the video is the main content. A tiny video below a long unrelated sales page is unlikely to send a clear signal.

Using a thumbnail Google cannot fetch

The thumbnail URL should be stable, indexable, and available without login. Avoid expiring URLs and blocked asset folders.

Making the markup disagree with the page

The title, description, creator, date, and video shown to visitors should align with the structured data. Hidden claims create quality and policy risks.

Assuming schema guarantees rankings

Structured data helps Google understand content and assess eligibility for search features. It does not replace a useful video, a crawlable page, strong page experience, or audience demand.

Forgetting the customer

A technically perfect video page can still fail if the video opens slowly, has poor sound, lacks captions, buries the next step, or never answers the customer’s question.

A small-business video SEO checklist

1. Choose a dedicated, indexable watch page with the video prominently displayed.
2. Write a unique title and useful visible summary.
3. Create a strong thumbnail that remains available at a stable URL.
4. Add accurate VideoObject JSON-LD.
5. Identify the creator as a Person or Organization.
6. Link the creator to a stable profile, author, or About page.
7. Add only engagement counts the business can verify and maintain.
8. Confirm that Google can fetch the page, thumbnail, embed, and video file.
9. Test the markup in Google’s Rich Results Test.
10. Monitor Search Console’s video indexing and video search appearance reports.

What WordPress site owners should check

Some SEO and video plugins generate VideoObject automatically, but their fields may be incomplete or duplicated. View the page source and search for VideoObject. Confirm that only the intended markup appears and that the creator, thumbnail, upload date, duration, and URLs are correct.

A plugin update may add creator support later, but businesses do not need to install multiple schema plugins to chase one new property. Competing schema generators can create conflicting objects. Use one controlled source and validate the final output.

CodeForce can help with WordPress and website improvements, Google campaign and video landing-page planning, social video workflows, and the data systems that keep content accurate.

VideoObject creator structured data FAQ

Will adding creator markup improve rankings?

Google does not promise a ranking boost. The property gives Google clearer information about who created or published the video.

Can the creator be a company?

Yes. Google supports both Person and Organization for the creator or author.

Do I need to include views and likes?

No. Interaction statistics are useful when accurate and applicable, but they should not be fabricated or guessed.

Can I use YouTube engagement numbers?

Only when the markup describes that same video and the numbers are accurate. Do not mix channel-wide totals or engagement from a different upload.

Sources

• Google Search Central: September 2026 documentation updates
• Google Search Central: Video structured data
• Google Search Central: Video SEO best practices
• Google Search Central: General structured data guidelines

Publishing original video but unsure whether Google can understand, fetch, and credit it? Book a free CodeForce intro call.