What fields are actually mandatory in a Google video sitemap?

Why does Google require two levels of URLs for each video?

Google distinguishes between the container page URL (the one that the user visits) and the URL of the video resource itself. This architecture reflects the reality of online video: the same video can be embedded on multiple pages, or conversely, one page can host multiple playback formats.

The page URL serves for ranking in the SERPs, while the player or file URL allows Google to check the technical accessibility of the video, generate thumbnails, and extract metadata. Without this second URL, Googlebot cannot crawl the actual video content.

Flash in 2025, really?

The mention of the Flash player in Google's documentation is a relic of legacy documentation. Flash has been dead for years, but Google hasn't cleaned up its XML specs. Ignore this reference: focus on MP4/WebM file URLs or HTML5 embeddings via player_loc.

What matters: provide a URL that is directly crawlable by Googlebot. YouTube, Vimeo, or Wistia players work through their respective APIs, but a self-hosted video file offers more control over structured metadata.

When can you skip mandatory metadata?

The nuance boils down to one line: if you provide a functional video file URL, Google can generate the thumbnail automatically. But be careful, this automation does not exempt you from providing a title or description in most cases.

In practice, Google extracts the thumbnail from the MP4/WebM file if it contains correctly formatted EXIF or XMP metadata. This is rare for videos exported from consumer-grade tools but common in professional workflows using MediaInfo or ffmpeg.

• Page URL mandatory: always, without exception. It's the ranking anchor.
• Player or file URL: at least one of the two. The direct file is preferable for control.
• Title and description: mandatory unless auto-generated from file metadata (rare).
• Thumbnail: mandatory unless the video file allows automatic extraction (check on Google Search Console).
• Duration, publication date, family: optional but highly recommended for visibility in video carousels.

Is this flexibility around metadata a trap?

Google suggests that you can delegate thumbnail generation to the crawler. Let's be honest: this automation is fickle. Field tests show that Google extracts the thumbnail from an MP4 file in less than 60% of cases, even when the file is technically compliant.

The risk? Your indexed video might end up without a thumbnail, or worse, with a randomly extracted black frame from the sequence. Result: disastrous CTR in video SERPs. In other words, this "option" isn't really one for a site aiming for performance.

What URL strategy should you prioritize in practice?

Two schools of thought are in conflict. Some prefer to point to the embed player URL (YouTube, Vimeo) because it's simple to automate via APIs. Others advocate for self-hosting the video file, arguing that it keeps control over metadata and the schema.org VideoObject.

My opinion after 15 years of testing: if your business relies on video (e-learning, tutorials, product demonstrations), self-host and serve MP4s with complete EXIF metadata. If it's secondary content, embedding YouTube with a sitemap pointing to player_loc is more than enough. [To be checked]: Does Google favor videos hosted on its own platforms (YouTube) in ranking? Public data is lacking, but experience suggests a slight advantage.

Do CMSs generate compliant video sitemaps by default?

No, and it's a real issue. WordPress with Yoast or RankMath produces video sitemaps that are technically valid but poor in metadata. They often omit duration, category, or geographic restrictions, all signals that Google uses to refine ranking.

Shopify and WooCommerce are even worse: they rarely generate separate video sitemaps, drowning URLs in the overall product sitemap. Result: slow video discovery rate, sometimes several weeks. If you publish more than 10 videos a month, a custom generator or specialized plugin becomes essential.

What should you implement concretely in the sitemap?

For each <video:video> tag, structure at a minimum: video:content_loc (file URL) OR video:player_loc (embed URL), video:thumbnail_loc (JPEG/PNG thumbnail URL), video:title (maximum 60 characters), video:description (optimal 200 characters). Always add video:duration in seconds, as it's a quality signal often overlooked.

Avoid relative URLs: Google requires absolute URLs with HTTPS protocol. A sitemap with http:// in 2025 will be partially ignored. Also, make sure to declare restrictions: video:requires_subscription, video:platform, video:restriction to target geographically.

How can you verify that Google indexes my videos correctly?

First reflex: Google Search Console > Enhancements > Video. This section lists discovered videos, parsing errors, and indexing status. If a video does not appear 72 hours after submitting the sitemap, the problem often lies with the content_loc URL being inaccessible to the crawler.

Manually test each video file URL via curl or Screaming Frog. Google should receive a Content-Type: video/mp4 with HTTP 200 status. 301/302 redirects on video files often break the crawl. Also check the robots.txt: no Disallow directive should block /videos/ or /media/.

What errors block video indexing?

Classic mistake: thumbnail in base64 or data URI. Google requires an external crawlable URL, not an inline image. Another trap: thumbnails served in WebP without JPEG fallback. Google handles WebP, but some legacy parsers in the video pipeline remain fickle.

False or rounded video durations (1:00 instead of 1:03) also disturb the recommendation algorithm in carousels. Lastly, beware of CDNs with authentication tokens: if the content_loc URL expires after 24 hours, Googlebot will never be able to crawl the file.

• Generate a separate video sitemap (video_sitemap.xml) distinct from the main sitemap
• Always include title, description, thumbnail, duration, and publication date
• Test each video file URL with curl -I to verify HTTP 200 and correct Content-Type
• Submit the sitemap via Google Search Console and monitor errors under Enhancements > Video
• Implement schema.org VideoObject in addition to the sitemap to enhance signals
• Ensure thumbnails are served in JPEG/PNG via absolute HTTPS URL, never in base64