A creator editing digital video content at a workstation
WordPress & Web

Google VideoObject Schema Update 2026: How to Add Creator Data in WordPress

Google updated its Search documentation on September 24, 2026, adding the creator property (and noting support for author) to its VideoObject structured-data guidance, while clarifying supported interaction types for interactionStatistic. For site owners who publish tutorials, product demonstrations, interviews, or embedded videos, this is a useful moment to review video metadata—not because a schema change guarantees more visibility, but because accurate structured data helps search engines interpret what a page contains.

This guide explains what changed, when VideoObject markup is appropriate, how to prepare accurate fields, and how to validate a WordPress page before publishing.

A creator editing digital video content at a workstation
Video publishing begins with a clear, accurate record of the content and its creator.

What changed in Google’s VideoObject documentation?

Google’s September 24 documentation update added creator and clarified that author is also supported. The creator or author should identify the person or organization that actually created or published the video. Google also documented supported interaction types for interactionStatistic, including watch, like, comment, and share actions.

These are documentation and structured-data details, not a promise of a new rich result or a ranking boost. Google says VideoObject markup can help it understand details such as a video’s description, thumbnail, upload date, and duration, and can make a video easier to discover when added to an appropriate watch page.

When should a website use VideoObject markup?

Consider it when a page has a meaningful video that visitors can actually watch—such as a tutorial, demonstration, lesson, interview, or recorded event. A page that merely mentions a video or links away to a third-party video without providing a watch experience may not be an appropriate place for video markup.

Structured data should describe the visible page accurately. Do not add video properties to a page that does not contain that video, and do not invent view counts, dates, durations, creators, or thumbnail URLs.

Laptop displaying a web development workspace
Review your site’s existing schema output before adding custom markup.

Key VideoObject fields to review

  • name: The video’s title, consistent with the visible content.
  • description: A concise, accurate explanation of the video.
  • thumbnailUrl: A crawlable thumbnail image representing the video.
  • uploadDate: The original publication date and time, using a valid date format and timezone where applicable.
  • duration: The actual runtime in ISO 8601 duration format, if known.
  • creator or author: The real person or organization responsible for creating or publishing the video. Include a name and, when available, a URL that identifies that creator.
  • interactionStatistic: Include only accurate, available interaction counts and a supported interaction type. Do not estimate or fabricate counts.
  • contentUrl or embedUrl: Use the appropriate video-file URL or embed URL where applicable; do not put the ordinary webpage URL in contentUrl.
Analytics dashboard representing structured video data review
Only publish interaction statistics that you can verify.

How to add video structured data in WordPress

  1. Choose a real video page. Confirm that the video is visible and playable for visitors and that the page provides useful context beyond the video alone.
  2. Check your current setup. Review your SEO, video, or schema plugin settings and inspect the page’s rendered source or structured-data output. Avoid adding a second, conflicting VideoObject block if a plugin already generates one.
  3. Confirm every value. Match the title, description, thumbnail, upload date, duration, creator, and any interaction counts to the actual video. Use a creator profile or organization homepage only if it genuinely identifies the creator.
  4. Keep the markup aligned with the page. If the video changes, update the metadata. Do not mark a video as live after the broadcast has ended, and do not add unsupported properties just to make the markup look more complete.
  5. Test before and after publishing. Use Google’s Rich Results Test to check supported features and the URL Inspection tool in Search Console to see how Google accesses the page. A valid test does not guarantee that a search feature will appear.

Example: creator information in JSON-LD

The simplified example below shows the structure of creator information. Replace the example values with verified details from your own video. Include the full VideoObject only when you have accurate values for its required and relevant properties.

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "How to Prepare a Print-Ready PDF",
  "description": "A tutorial explaining the export settings for a print-ready PDF.",
  "thumbnailUrl": "https://example.com/images/tutorial-thumbnail.jpg",
  "uploadDate": "2026-09-20T10:00:00+05:00",
  "creator": {
    "@type": "Organization",
    "name": "Example Studio",
    "url": "https://example.com/about/"
  }
}

This is an illustrative snippet, not ready-to-paste markup: the example domain, date, video title, and creator are placeholders. Add only fields that accurately describe the actual video, and confirm the complete markup against Google’s current requirements.

Common mistakes that can make video markup less useful

  • Using a generic site name as the creator when a named creator or publishing organization is known.
  • Entering a video page URL as contentUrl instead of the actual video file URL.
  • Using a thumbnail that is blocked from crawling, unrelated, or not representative.
  • Copying view counts from a platform without verifying the number and its meaning.
  • Adding structured data to pages where the video is not actually available to visitors.
  • Assuming a valid schema test guarantees indexing, a video result, or higher rankings.
Content team planning a digital publishing workflow around a laptop
A repeatable review workflow helps keep video metadata accurate as content changes.

A practical review checklist for publishers

For each important video page, record the page URL, video title, creator, upload date, thumbnail URL, duration, and the location of the structured-data output. After changes, run a validation test, inspect the live URL, and keep a note of what was changed. This small audit trail makes future updates easier, especially when videos are replaced or moved.

If your site is built with WordPress, first review your existing SEO and video plugins before adding custom code. For broader site usability, see our WordPress website design tips. If you are building a content workflow that uses AI, our guide to AI automation for WordPress covers how to keep human review in the process.

Digital team collaborating around a laptop
Validate the live page and document what was changed.

Frequently asked questions

Does adding the creator property improve Google rankings?

Google’s documentation update does not say that adding creator is a ranking boost. Structured data helps describe content; it does not guarantee a ranking change or enhanced search appearance.

Should I use creator or author?

Google’s updated guidance notes support for both. Choose the property that accurately describes the person or organization responsible for creating or publishing the video, and use consistent, truthful information.

Can I add VideoObject markup to any blog post with a YouTube link?

Not automatically. The page should provide a real video-watching experience and the markup must describe the video accurately. Review Google’s current video structured-data guidance before implementing it.

Does a successful Rich Results Test mean Google will show a video result?

No. Validation can identify markup issues, but Google decides whether and how eligible content appears. Crawling, indexing, relevance, and feature eligibility still matter.

Official references

Editorial note: This article is an implementation guide, not a guarantee of search visibility. Google’s documentation and supported features can change; verify the current official guidance before deploying schema across a large site.

Leave a Reply

Your email address will not be published. Required fields are marked *