Video sitemaps and alternatives

A video sitemap is a sitemap with additional information about video hosted on your pages. Creating a video sitemap is an excellent way to help Google find and understand the video content on your site, especially content that was recently added or that we might not otherwise discover with our usual crawling mechanisms. A video sitemap is an extension to the Sitemap protocol.

While Google recommends using video sitemaps, we also support mRSS feeds.

Guidelines for video sitemaps

Here are basic guidelines for video sitemaps:

  • You can create a separate sitemap just for video, or you can embed video sitemap tags within an existing web sitemap, whichever is more convenient for you.
  • You can host multiple videos in one web page.
  • Each sitemap entry is the URL of a page that hosts one or more videos. The structure of each sitemap entry is as follows: 
          <url>
        <loc>https://example.com/mypage</loc>      <!-- URL of host page -->
        <video> ... information about video 1 ... </video>
        ... as many additional <video> entries as you need ...
      </url>
  • Don't list videos that are unrelated to the host page. For example, if the video is a small addendum to the page, or unrelated to the main text content.
  • Each entry in a video sitemap includes a set of required, recommended, or optional values that you supply. Recommended and optional values provide useful metadata that can enhance your video results and improve Google's ability to include your video in search results. Refer to the list of sitemap tag definitions.
  • Google might use text on the video landing page rather than the text you supply in your sitemap, if the page text is deemed more useful than the information in the sitemap.
  • Google can't guarantee when or if your videos will be indexed, as Google relies on complex indexing algorithms.
  • If Google can't discover video content at the URL you provide, the sitemap entry is ignored.
  • Each sitemap file that you provide must have no more than 50,000 URL elements. If you have more than 50,000 videos, you can submit multiple sitemaps or a sitemap index file. You can't nest sitemap index files. Keep in mind that if you are adding optional tags, you may reach the 50MB uncompressed limit before you reach the 50,000 video limit.
  • Google must be able to access the source file or player (that is, the file or player can't be blocked by robots.txt, require a login, or be otherwise inaccessible to Googlebot). Metafiles that require a download of the source via streaming protocols are not supported.
  • All files must be accessible to Googlebot. If you want to prevent spammers from accessing your video content at the <player_loc> or <content_loc> URLs, verify that any bots accessing your server are really Googlebot.
  • Make sure that your robots.txt file isn't blocking any of the items (including the host page URL, the video URL, and the thumbnail URL) included in each sitemap entry. More information about robots.txt.
  • Google verifies that the information you provide for each video matches what is on the site. If not, your video might not be indexed.
  • You can specify pages from different sites in one sitemap. All sites, including the one containing your sitemap, must be verified in Search Console. More information about managing sitemaps for multiple sites.
  • Learn how to submit your sitemap to Google. For large sites, we recommend using the Search Console API to submit your sitemaps.

Example sitemap

Here is a sample video sitemap with one page hosting one video. This example includes all of the tags that Google uses.

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:video="http://www.google.com/schemas/sitemap-video/1.1">
   <url>
     <loc>http://www.example.com/videos/some_video_landing_page.html</loc>
     <video:video>
       <video:thumbnail_loc>http://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>
         http://www.example.com/videoplayer.php?video=123</video:player_loc>
       <video:duration>600</video:duration>
       <video:expiration_date>2021-11-05T19:20:30+08:00</video:expiration_date>
       <video:rating>4.2</video:rating>
       <video:view_count>12345</video:view_count>
       <video:publication_date>2007-11-05T19:20:30+08:00</video:publication_date>
       <video:family_friendly>yes</video:family_friendly>
       <video:restriction relationship="allow">IE GB US CA</video:restriction>
       <video:price currency="EUR">1.99</video:price>
       <video:requires_subscription>yes</video:requires_subscription>
       <video:uploader
         info="http://www.example.com/users/grillymcgrillerson">GrillyMcGrillerson
       </video:uploader>
       <video:live>no</video:live>
     </video:video>
   </url>
</urlset>

XML namespace

The video sitemap tags are defined in the following namespace:

xmlns:video="http://www.google.com/schemas/sitemap-video/1.1"

Video sitemap tag definitions

You can find more documentation on media sitemaps at rssboard.org.

Required tags
<url> The parent tag for a single host page on your site. This tag is defined by the basic sitemaps format.
<loc>

Specifies the host page where one or more videos are hosted. When a user clicks on a video result in Google Search, they are sent to this page. This URL must be a unique within the sitemap. This tag is defined by the basic sitemaps format.

For multiple videos on a single page, create a single <loc> tag for the page, with a child <video> element for each video on that page.

<video:video>

The parent element for all information about a single video on the page specified by the <loc> tag.

<video:thumbnail_loc>

A URL pointing to the video thumbnail image file. Follow the video thumbnail requirements.

<video:title>

The title of the video. All HTML entities must be escaped or wrapped in a CDATA block. We recommend that this match the video title displayed on the web page.
<video:description>

A description of the video. Maximum 2048 characters. All HTML entities must be escaped or wrapped in a CDATA block. It must match the description displayed on the web page (it doesn't need to be a word-for-word match).

<video:content_loc>

A URL pointing to the actual video media file. The file must be one of the supported formats.

Additional guidelines

  • HTML and Flash aren't supported formats.
  • Must not be the same as the <loc> URL.
  • This is the equivalent of VideoObject.contentUrl in structured data.
  • Best practice: If you want to restrict access to your content but still have it crawled, ensure that Googlebot can access your content by using a reverse DNS lookup.
<video:player_loc>

A URL pointing to a player for a specific video. Usually this is the information in the src element of an <embed> tag.

Additional guidelines

  • Must not be the same as the <loc> URL.
  • For YouTube videos, this value is used rather than video:content_loc. This is the equivalent of VideoObject.embedUrl in structured data.
  • Best practice: If you want to restrict access to your content but still have it crawled, ensure that Googlebot can access your content by using a reverse DNS lookup.
Recommended tags
<video:duration>

The duration of the video, in seconds. Value must be from 1 to 28800 (8 hours) inclusive.
<video:expiration_date>

The date after which the video is no longer be available, in W3C format. Omit this tag if your video does not expire. If present, Google Search won't show your video after this date.

Supported values are complete date (YYYY-MM-DD), or complete date plus hours, minutes and seconds, and timezone (YYYY-MM-DDThh:mm:ss+TZD).

Example: 2012-07-16T19:20:30+08:00.
Optional tags
<video:rating>

The rating of the video. Supported values are float numbers in the range 0.0 (low) to 5.0 (high), inclusive.

<video:view_count>

The number of times the video has been viewed.
<video:publication_date>

The date the video was first published, in W3C format. Supported values are complete date (YYYY-MM-DD) or complete date plus hours, minutes and seconds, and timezone (YYYY-MM-DDThh:mm:ss+TZD).

Example: 2007-07-16T19:20:30+08:00
<video:family_friendly>

Whether the video is available with SafeSearch. If you omit this tag, the video is available when SafeSearch is turned on.

Supported values:

  • yes: The video is available when SafeSearch is turned on.
  • no: The video is only available when SafeSearch is turned off.
<video:restriction>

Whether to show or hide your video in search results from specific countries.

Specify a space-delimited list of country codes in ISO 3166 format. Only one <video:restriction> tag can be used for each video. If there is no <video:restriction> tag, Google assumes that the video can be shown in all locations. Note that this tag only affects search results; it doesn't prevent a user from finding or playing your video in a restricted location though other means. Learn more about applying country restrictions.

Attributes:

  • relationship [Required] Whether the video is allowed or denied in search results in the specified countries. Supported values are allow or deny. If allow, listed countries are allowed, unlisted countries are denied; if deny, listed countries are denied, unlisted countries are allowed.

Example: This example allows the video search result to be shown only in Canada and Mexico:

<video:restriction relationship="allow">CA MX</video:restriction>

<video:platform>

Whether to show or hide your video in search results on specified platform types. This is a list of space-delimited platform types. Note that this only affects search results on the specified device types; it does not prevent a user from playing your video on a restricted platform.

Only one <video:platform> tag can appear for each video. If there is no <video:platform> tag, Google assumes that the video can be played on all platforms. Learn more about applying platform restrictions.

Supported values:

  • web - Traditional computer browsers on desktops and laptops.
  • mobile - Mobile browsers, such as those on cellular phones or tablets.
  • tv - TV browsers, such as those available through GoogleTV devices and game consoles.

Attributes:

  • relationship [Required] specifies whether the video is restricted or permitted for the specified platforms. Supported values are allow or deny. If the allow value is used, any omitted platforms will be denied; if the deny value is used, any omitted platforms will be allowed.

Example: The following example allows users on web or TV, but not mobile devices:
<video:platform relationship="allow">web tv</video:platform>

<video:requires_subscription>

Indicates whether a subscription is required to view the video. Allowed values are yes or no.

<video:uploader>

The video uploader's name. Only one <video:uploader> is allowed per video. The string value can be a maximum of 255 characters.

Attributes:

  • info [Optional] Specifies the URL of a webpage with additional information about this uploader. This URL must be in the same domain as the <loc> tag.
<video:live>

Indicates whether the video is a live stream. Supported values are yes or no.

<video:tag>

An arbitrary string tag describing the video. Tags are generally very short descriptions of key concepts associated with a video or piece of content. A single video could have several tags, although it might belong to only one category. For example, a video about grilling food may belong in the "grilling" category, but could be tagged "steak", "meat", "summer", and "outdoor". Create a new <video:tag> element for each tag associated with a video. A maximum of 32 tags is permitted.

Deprecated tags and attributes

We removed the following tags and attributes from our documentation: <video:category>, <video:gallery_loc>, the autoplay and allow_embed of the <video:player_loc> tag, the <video:price> tag and its attributes, and the <video:tvshow> tag and its attributes. See the deprecation announcement for more information.

Sitemap alternative: mRSS

While Google recommends using video sitemaps and schema.org's VideoObject to mark up your videos, we also support mRSS feeds.

Google supports mRSS, an RSS module that supplements the element capabilities of RSS 2.0. mRSS feeds are very similar to video sitemaps and can be tested, submitted, and updated just like sitemaps.

Each mRSS feed must be under 50MB in size when uncompressed, and can contain no more than 50,000 video items. If your uncompressed file is larger than 50MB, or you have more than 50,000 videos, you can submit multiple mRSS feeds and a sitemap index file. Sitemap indexes can contain mRSS feeds.

mRSS Example

Here's an example of an mRSS entry that provides all the key tags that Google uses. This includes <dcterms:type>live-video</dcterms:type>, which you can use to identify live, streaming videos.

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:dcterms="http://purl.org/dc/terms/">
<channel>
<title>Example MRSS</title>
<link>http://www.example.com/examples/mrss/</link>
<description>MRSS Example</description>
  <item xmlns:media="http://search.yahoo.com/mrss/" xmlns:dcterms="http://purl.org/dc/terms/">
    <link>http://www.example.com/examples/mrss/example.html</link>
    <media:content url="http://www.example.com/examples/mrss/example.flv" fileSize="405321"
      type="video/x-flv" height="240" width="320" duration="120" medium="video" isDefault="true">
      <media:player url="http://www.example.com/shows/example/video.swf?flash_params" />
      <media:title>Grilling Steaks for Summer</media:title>
      <media:description>Get perfectly done steaks every time</media:description>
      <media:thumbnail url="http://www.example.com/examples/mrss/example.png" height="120" width="160"/>
      <media:price price="19.99" currency="EUR" />
      <media:price type="subscription" />
    </media:content>
    <media:restriction relationship="allow" type="country">us ca</media:restriction>
    <dcterms:valid xmlns:dcterms="http://purl.org/dc/terms/">end=2020-10-15T00:00+01:00; scheme=W3C-DTF</dcterms:valid>
    <dcterms:type>live-video</dcterms:type>
  </item>
</channel>
</rss>

mRSS Tags

The full mRSS specification contains more optional tags, best practices, and examples. Once you have an mRSS feed, you can submit it just like any other sitemap.

Required tags
<media:content>

Encloses information about the video.

Attributes:

  • medium [Required] Type of content. Set to video.
  • url [Required] The direct URL to the raw video content. If this isn't specified, you must specify the <media:player> tag.
  • duration [Optional but recommended] Length of the video in seconds.

For all of the other optional attributes and child fields of the <media:content> tag, see the mRSS specification.
<media:player>

You must specify at least one of <media:player> or the url attribute in <media:content>.

A URL pointing to a player for a specific video. Usually this is the information in the src element of an <embed> tag and must not be the same as the content of the <loc> tag. It can't be the same URL as the <link> tag. <link> points to the URL of the page hosting the video, while this tag points to a player.
<media:title>

The title of the video. Maximum 100 characters. All HTML entities must be escaped or wrapped in a CDATA bock.
<media:description>

The description of the video. Maximum 2048 characters. All HTML entities must be escaped or wrapped in a CDATA block.
<media:thumbnail> A URL pointing to a preview thumbnail. Follow the Video thumbnail requirements.
Optional tags
<dcterms:valid>

The publication and expiration date of the video. Here's the Full specification of the dcterms:valid tag.

Example:

<dcterms:valid>
  start=2002-10-13T09:00+01:00;
  end=2002-10-17T17:00+01:00;
  scheme=W3C-DTF
<dcterms:valid>
<media:restriction>

A space-delimited list of countries where the video may or may not be played, in ISO 3166 format. If there is no <media:restriction> tag, Google assumes that the video can be played in all territories.

Attributes:

  • type [Required] Set the type attribute to country. Only country restrictions are supported.
  • relationship [Required] Specifies whether the video may or may not be played in the specified list of countries. Supported values:
    • allow
    • deny

Learn more about using country restrictions.

Example:

<media:restriction relationship="allow" type="country">us ca</media:restriction>
<media:price>

The price to download or view the video. Don't use this tag for videos that are available without payment. More than one <media:price> element can be listed (for example, in order to specify various currencies or purchasing options).

Attributes:

  • currency [Required] The currency in ISO 4217 format.
  • type [Required] The purchase option. Allowed values are rent, purchase, package, and subscription.