# Video sitemaps: purpose, contents and checks

A video sitemap tells a search engine where a video is presented and provides discovery information about that video. It can complement links and structured data. Its presence is not proof of page indexing, video indexing or impressions. Start by checking that the page and its resources are actually public.

## Read the addresses before the tags

In a video sitemap, the outer `loc` identifies the host page. The video entry then supplies a thumbnail, title, description and a media or player location. Do not replace the host page with the MP4 address. Do not use a YouTube watch page where an embeddable player URL is needed.

| Element | Question to answer |
| --- | --- |
| `loc` | Which canonical page presents this video? |
| `video:thumbnail_loc` | Can the correct thumbnail be fetched? |
| `video:title` and `video:description` | Do these describe the visible recording? |
| `video:content_loc` | Is this a directly accessible media file? |
| `video:player_loc` | Is this a player for the video, when used instead of or alongside a file? |

Google's video sitemap guidance requires a `video:video` entry, thumbnail, title and description, and at least one of `content_loc` or `player_loc`. Optional information must still be true. A sitemap with more fields is not automatically more useful.

## Follow a real WordPress export

Download the [demo sitemap index](/media/hub-20261116/video-sitemap-index.xml.txt), then the [video sitemap it references](/media/hub-20261116/video-sitemap.xml.txt). These are text copies from an isolated WordPress installation. The local origin was replaced with reserved `https://example.invalid` addresses; these nonfunctional demonstration URLs must not be submitted to Search Console.

**Observed in the isolated test:** the video sitemap returned HTTP 200 with an XML content type and two video entries, one for each published English/French page. This establishes that the tested output was available and contained those entries. No sitemap was submitted to Google. The [evidence record](/media/hub-20261116/evidence.json) identifies the package, environment and exports.

<details><summary>Read the observed XML (line breaks added for readability)</summary>

```xml
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:video="http://www.google.com/schemas/sitemap-video/1.1">
<url>
<loc>https://example.invalid/?page_id=6</loc>
<video:video>
<video:thumbnail_loc>https://example.invalid/wp-content/uploads/2026/11/demo-en-poster.png</video:thumbnail_loc>
<video:title>Watch. Read. Revisit.</video:title>
<video:description>An original video to watch, read and explore by chapter.</video:description>
<video:content_loc>https://example.invalid/wp-content/uploads/2026/11/demo-en.mp4</video:content_loc>
<video:publication_date>2026-11-16T16:59:22+00:00</video:publication_date>
</video:video>
</url>
<url>
<loc>https://example.invalid/?page_id=11</loc>
<video:video>
<video:thumbnail_loc>https://example.invalid/wp-content/uploads/2026/11/demo-fr-poster.png</video:thumbnail_loc>
<video:title>Regardez. Lisez. Retrouvez.</video:title>
<video:description>Une vidéo originale pour regarder, lire et retrouver les passages utiles.</video:description>
<video:content_loc>https://example.invalid/wp-content/uploads/2026/11/demo-fr.mp4</video:content_loc>
<video:publication_date>2026-11-16T16:59:22+00:00</video:publication_date>
</video:video>
</url>
</urlset>
```

</details>


On your own installation, use the current [VidSEO documentation](/docs/#video-sitemap) to locate the enabled sitemap output. Follow the index to a child sitemap and locate one known published video. Compare its page address and metadata with the [VideoObject on that page](/guides/videoobject-wordpress/). The XML and JSON-LD are different formats, but contradictory identities or publication details deserve investigation.

## Check the published state

Work from a signed-out request. Confirm the host page is not private, password-protected or redirected to an unrelated destination. Inspect `noindex` in the page metadata and HTTP headers, then examine robots access. Check the thumbnail and the player or media file independently; a page returning HTTP 200 says nothing about a blocked image.

A draft in an editor is not a published video placement. When an entry is missing, check the publication state and eligible host page before adding XML by hand. When an entry remains after a change, investigate cache state and the actual response rather than assuming the editor preview represents the public feed.

## Submit and observe without skipping a step

For an authorized production property, submit the public sitemap URL in Search Console and record whether it was fetched and parsed. A successful sitemap submission only settles that stage. Inspect the page URL separately, then read the video indexing report if Google has detected a video there.

The report's sitemap filter groups pages by sitemap membership; it is not a test that each video-specific XML element caused indexing. Keep a dated note of what each report actually says. The [Search Console procedure](/guides/video-search-console/) separates the live test, known index state and delayed reports.

**Next step:** select one published page and trace its canonical URL through the page HTML, VideoObject and sitemap. Resolve contradictions before interpreting missing search appearances.

## References

- [Google: video sitemap format and requirements](https://developers.google.com/search/docs/crawling-indexing/sitemaps/video-sitemaps).
- [Search Console: video indexing report](https://support.google.com/webmasters/answer/9495631).

[Browse all resources](/resources/).
