
A video sitemap is an XML file, or a set of XML tags inside your existing sitemap, that tells Google exactly where a video lives, what it shows, and how to preview it. It uses tags like video:thumbnail_loc, video:title, and video:content_loc so Google can discover and index video it might otherwise miss, particularly video loaded through JavaScript players or buried on pages with few internal links.
Not every site needs one. If you only embed a handful of YouTube clips, Google usually finds them without help, since YouTube already submits its own sitemaps. If you self-host video, run a media-heavy site, or want a specific page to qualify for video rich results, a video sitemap is one of the few technical fixes that pays off almost immediately. This guide covers the exact tags Google requires, a working XML example, how video sitemaps differ from a regular or image sitemap, and the mistakes that quietly keep videos out of Google's Video tab.
A video sitemap is an extension of the standard XML sitemap format. Instead of listing only a page URL and a last-modified date, it nests a video:video block inside the url entry for any page that hosts video, and that block carries metadata about the video itself. Google reads this the same way it reads a normal sitemap: as a signal, not a command, but one that speeds up how quickly it finds and understands your video content.
The format comes from Google's own video sitemap documentation, which defines the video namespace (xmlns:video) and the full list of supported tags. You declare that namespace once at the top of the file, then add a video:video block for every video on every relevant page. A page can have more than one video listed if it genuinely contains more than one.
Where this differs from a plain sitemap or an image sitemap is the depth of metadata. A regular sitemap entry is just a URL and a date. A video sitemap entry carries a thumbnail, a title, a description, a runtime, and a location for the actual video file or player, all of which Google can use to build a preview in search results before anyone clicks.
Video visibility is not a niche concern worth skipping. Searchmetrics analyzed 500,000 keywords and found that video thumbnails appear in roughly 62% of Google search results, a share that climbs to 78% for how-to queries and 71% for product queries. A page competing in that territory without any video signals is handing an advantage to competitors who send Google the metadata it needs.
These three formats share the same XML skeleton but serve different jobs. The table below shows where they overlap and where they split.
| Format | What it describes | Core tags | Best for |
|---|---|---|---|
| Regular XML sitemap | Page URLs | loc, lastmod | Every site, as the baseline |
| Image sitemap | Images on a page | image:loc, image:caption | Photo galleries, ecommerce product shots |
| Video sitemap | Videos on a page | video:thumbnail_loc, video:title, video:description, video:content_loc or video:player_loc | Self-hosted video, video-heavy landing pages |
No. Google's own documentation states you can create a separate sitemap or mRSS feed just for video, or add video sitemap tags within an existing sitemap, whichever is more convenient. For most site owners, adding a video:video block to the url entry you already have is simpler than maintaining a second file.
A separate video sitemap earns its keep on large, video-first sites such as streaming platforms or course libraries, where video metadata changes on its own schedule and mixing it into the main sitemap would make both files harder to manage. For a marketing site with video scattered across a few dozen pages, folding the tags into your existing XML sitemap is the more practical route.
Google's specification is stricter about video sitemaps than about a plain URL list. Four tags are mandatory for every video:video block, and the rest are optional signals that sharpen how Google displays and ranks the video.
| Tag | Required? | What it does |
|---|---|---|
| video:thumbnail_loc | Yes | URL of the video's thumbnail image |
| video:title | Yes | Video title, should match the title shown on the page |
| video:description | Yes | Description up to 2,048 characters, should match the on-page description |
| video:content_loc or video:player_loc | Yes, at least one | Direct file URL, or a URL to the player that plays the video |
| video:duration | No | Length in seconds, from 1 to 28,800 |
| video:publication_date | No | When the video was first published, in W3C date format |
| video:expiration_date | No | When the video stops being available |
| video:rating | No | Rating from 0.0 to 5.0 |
| video:view_count | No | Total number of views |
| video:family_friendly | No | Whether the video is safe to show with SafeSearch on |
| video:tag | No | Up to 32 keyword tags per video |
| video:live | No | Marks a livestream |
Here is a working example straight from Google's documentation, showing the required tags plus two common optional ones:
<?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://www.example.com/videos/some_video_landing_page.html</loc>
<video:video>
<video:thumbnail_loc>https://www.example.com/thumbs/123.jpg</video:thumbnail_loc>
<video:title>Grilling steaks for summer</video:title>
<video:description>Alkis shows you how to get perfectly done steaks every time</video:description>
<video:content_loc>http://streamserver.example.com/video123.mp4</video:content_loc>
<video:player_loc>https://www.example.com/videoplayer.php?video=123</video:player_loc>
<video:duration>600</video:duration>
<video:publication_date>2007-11-05T19:20:30+08:00</video:publication_date>
</video:video>
</url>
</urlset>Every field here is copied directly from Google Search Central's video sitemap reference, so it validates as-is. Swap in your own thumbnail, title, description, and file or player URL, and the block is ready to paste into your sitemap.
Open your current sitemap.xml, add the video namespace to the opening urlset tag, then insert a video:video block inside the url entry for any page that has video. You do not need a new file or a new submission in Search Console, since Google re-crawls your existing sitemap on its own schedule.
Practically, that means three steps: declare xmlns:video on the urlset element, find or add a url block for each video page, and nest one video:video block per video inside it with at least the four required tags filled in. If your sitemap is generated automatically by a CMS or a plugin, check whether it already supports video output before writing anything by hand. WordPress plugins with a video SEO add-on, for example, scan posts for embedded video and build these tags for you.
Usually not. YouTube already crawls and indexes its own video library and submits its own sitemaps to Google, so a video hosted and played entirely on youtube.com rarely needs a separate entry from your site. This matches what hosting providers like Swarmify report: sites that only embed YouTube or Vimeo players rarely benefit from a dedicated video sitemap, since the platform is already handling discovery.
The exception is when you want your own page, not the YouTube watch page, to be the one that shows up with a video thumbnail in Google's results. In that case, add a video:video block with video:player_loc pointing to the embed URL. Google's documentation makes no special exception for embedded platforms, so the same tag requirements apply either way.
There is no fixed timeline in Google's own documentation, and a sitemap never guarantees indexing at all. Swarmify, a video hosting and CDN company, reported that some of its customers went from zero video impressions in Search Console to appearing in Google's Video tab within 48 hours of submitting a sitemap, though that outcome depends heavily on the site's existing crawl activity and authority.
Treat any timeline claim, including that one, as a best case rather than a promise. A new or rarely crawled site can take considerably longer, and Google can decide not to feature a video at all if it does not meet quality expectations. Submitting the sitemap is the fast part. Earning a spot in results still depends on the video and the page around it.
Most video sitemap problems come from mismatched or incomplete metadata rather than a broken file.
Each of these is a five-minute fix once you know to look for it, which is exactly why a technical review catches them faster than trial and error. If your core sitemap already has structural issues, fix those first since a video block sitting inside a broken sitemap inherits the same problems.
A video sitemap covers discovery on your own domain, but if the goal is ranking inside YouTube itself, that is a separate discipline with its own rules around titles, tags, and watch time. Our YouTube SEO checklist walks through the on-platform side, and if you would rather hand off channel growth entirely, see our YouTube SEO services for what a managed program covers.
What is a video sitemap in simple terms? A video sitemap is an XML file, or a set of XML tags added to your existing sitemap, that tells Google where each of your videos lives, what it shows, and how to preview it. It uses tags such as video:thumbnail_loc, video:title, and video:content_loc so search engines can find and understand video content they might otherwise miss.
Is a video sitemap required for every site with video? No. Google can discover and index video without a sitemap, especially when the video is embedded from YouTube or Vimeo. A video sitemap earns its place on sites that self-host video, load players through JavaScript, or want to help Google find video content that is not well linked internally.
Do YouTube-hosted or embedded videos need a video sitemap entry? Usually not, since YouTube already submits its own video sitemaps and indexes videos on its own platform. But if you embed a YouTube video on your page and want that specific page to qualify for video rich results in Google, adding a video sitemap entry with video:player_loc pointing to the embed URL still helps.
What is the difference between video:content_loc and video:player_loc? video:content_loc points straight to the raw video file, such as an MP4, so Google can fetch and read it directly. video:player_loc points to a player page that plays the video, such as a YouTube embed URL. Google's documentation requires at least one of the two, and content_loc is the one it recommends when you can provide it.
How long can the video:description tag be? Google's video sitemap documentation caps video:description at 2,048 characters, and the text should match the description shown on the page itself. A mismatched or padded description can cause Google to ignore the entry rather than trust it.
Does submitting a video sitemap guarantee my video gets indexed? No. A video sitemap is a discovery signal, not a guarantee. Google still evaluates the page and video against its normal quality and indexing standards, and it can choose not to index or feature a video even after reading a valid sitemap entry.
Can one page list more than one video in its video sitemap entry? Yes. A single url block in your sitemap can contain more than one video:video entry if the page genuinely hosts multiple distinct videos. Each video still needs its own thumbnail, title, description, and content or player location.
Where do I submit a video sitemap once it is built? The same place as any sitemap: Google Search Console, under Indexing then Sitemaps. If you added video tags to your existing sitemap, you do not need to submit anything new, since Google already re-reads that file on its normal schedule.
What is the difference between a video sitemap and VideoObject schema markup? A video sitemap is a discovery file that helps Google find your video in the first place. VideoObject schema is structured data placed on the page itself that describes the video in detail for rich results. Google's own guidance recommends using both together, since they serve different jobs and reinforce the same information.
If your site self-hosts video or loads it through a JavaScript player, add video tags to your existing sitemap this week using the four required fields above, then check back in Search Console's Video indexing report. If your videos are all straight YouTube embeds, your time is better spent on the checklist that actually moves YouTube rankings. Either way, a stat like Searchmetrics' finding that video shows up in 62% of search results is a reminder that skipping video discoverability is leaving visibility on the table. If you want a technical review of your whole sitemap setup, not just the video piece, request a free SEO audit from Rankite.
Get a free, no-obligation SEO audit and a 30-minute strategy session. We'll show you exactly where the growth is hiding.
Fill out the form and we'll get back to you within one business day. Prefer email? Write to us directly at contact@rankite.com.