# Understand and check VideoObject on WordPress

`VideoObject` describes a video in structured data. It helps connect the recording, its thumbnail, its publication information and the page that presents it. It does not replace a visible transcript, and syntactically valid JSON does not prove that Google will index a video or display an enhanced result.

## Keep three addresses separate

The page URL is the article or viewing page. A player URL loads an embeddable player. A media URL returns the video file itself. Copying the same watch-page address into every property can produce valid JSON that describes the resources incorrectly.

| Property | Meaning to verify | Common mistake |
| --- | --- | --- |
| `name` | An accurate title of the video | A generic site-wide title |
| `thumbnailUrl` | A stable, accessible thumbnail for this video | A missing or unrelated image |
| `uploadDate` | The video's first publication date, with the appropriate date/time format | The date you revised the article |
| `description` | A specific summary of the recording | A copied sales paragraph |
| `duration` | The actual duration, in ISO 8601 form | The recording's planned duration |
| `contentUrl` | A directly accessible media file, when known | A page containing a player |
| `embedUrl` | An embeddable player address, when applicable | A file URL or unrelated page |

Google lists `name`, `thumbnailUrl` and `uploadDate` as required properties for its VideoObject eligibility guidance; the other fields above are recommended. Schema.org's vocabulary is broader than the properties Google uses. A vocabulary definition and a search-feature requirement are different sources of truth.

## Inspect an actual output

The [JSON-LD export from our WordPress demonstration](/media/hub-20261116/videoobject-en.json.txt) is saved as text so it can be studied without adding its video entities to this guide's metadata. Its local origin was replaced with the reserved `https://example.invalid` address. These deliberately nonfunctional URLs are not production metadata to copy.

**Observed output, with a limitation:** one VideoObject and three Clip objects were present for each published language variant. The plugin output sets `embedUrl` to the same MP4 address as `contentUrl` in this HTML5 case; that does not distinguish a player URL from a media-file URL and should be reviewed separately. The export is preserved, not offered as an ideal template or a Google-validated result. The English duration is declared as `PT30S`, rounded up from a decoded 29.645867 seconds; the French duration is `PT41S` for 40.571233 seconds. Those rounded values do not establish key-moment eligibility. See the [environment and measurements](/media/hub-20261116/evidence.json).

<details><summary>Inspect these exact properties from the exported object (excerpt)</summary>

```json
{
  "@type": "VideoObject",
  "name": "Watch. Read. Revisit.",
  "uploadDate": "2026-11-16T16:59:22+00:00",
  "duration": "PT30S",
  "contentUrl": "https://example.invalid/wp-content/uploads/2026/11/demo-en.mp4",
  "embedUrl": "https://example.invalid/wp-content/uploads/2026/11/demo-en.mp4"
}
```

</details>


To inspect your own page, open its source and search for `application/ld+json`, then for `VideoObject`. Check every matching object. A theme, an SEO extension and a video extension can each contribute markup; counting objects is only the start. Determine whether they describe different videos or contradict each other about the same one.

## Validate meaning as well as syntax

Use a structured-data test to locate parse errors and missing fields. Then manually compare the title, image, duration and date with the visible page and the recording. Open the thumbnail and media/player addresses in a signed-out browser. A successful test using pasted code does not prove that a crawler can retrieve those URLs on the live site.

If chapter metadata is present, test the chapter links against playback. `Clip` describes a named portion with a real start time and a URL that reaches it. Do not invent chapters for eligibility. Google applies additional conditions to key moments; adding a list of times is not a promise of that display.

## Check the transcript separately

Schema.org defines a `transcript` text property for audio and video objects. A string inside JSON-LD is not a visible reading experience, and that property is not one of Google's required VideoObject properties. Search the page's normal HTML for a distinctive spoken sentence, as shown in the [before/after comparison](/blog/before-and-after-a-video-page-with-and-without-an-exposed-transcript/).

If the markup is coherent but the video remains unindexed, continue with [page indexing versus video indexing](/guides/page-indexing-vs-video-indexing/). If the page and media addresses are missing from discovery signals, examine the [video sitemap](/guides/video-sitemap-wordpress/). For the actual VidSEO settings, use the [documentation](/docs/).

## References

- [Google: VideoObject structured data](https://developers.google.com/search/docs/appearance/structured-data/video).
- [Google: video SEO practices](https://developers.google.com/search/docs/appearance/video).
- [Schema.org: transcript](https://schema.org/transcript).

[Browse all resources](/resources/).
