Crawvix

Image, Video and News Sitemaps: When They Help and How to Build Them

Crawvix Editorial Team · Published October 29, 2026 · Last updated October 29, 2026 · 7 min read

A standard XML sitemap lists page URLs. Google also supports extensions that add detail about the images, videos and news articles on those pages. They are optional, and for many sites they add nothing: search engines usually find images and videos by reading your page HTML. They earn their place when media is loaded in a way crawlers might miss, when you publish many new videos, or when you run a news publication.

This guide is for site owners and developers who want to decide whether an image sitemap or video sitemap is worth the effort, and for publishers who need a news sitemap. You will learn what each extension contains, which tags are required, which have been dropped, the limits that apply, and how to publish and check the result.

An image sitemap or video sitemap does not ensure that media will be indexed or shown. Google's own sitemap documentation says a sitemap helps search engines find content but does not ensure everything listed is crawled or indexed. Treat these files as accurate hints, not as switches.

Before you begin

  • Access: the ability to publish a file on your site (or change your sitemap generator), and Search Console access to submit it.
  • Prerequisite: a working base sitemap of canonical, indexable pages. If you do not have one, start with how to create an XML sitemap.
  • Time: an hour for a simple site; longer if a CMS or video platform must feed the data.
  • Risk: low. A malformed file produces errors in Search Console but does not remove pages from the index.
  • Data you need: for images, the image URLs per page. For video, a thumbnail, title, description and either a media file URL or a player URL for each video. For news, publication name, language, publication date and title for recent articles.
  • Back up: keep a copy of your current sitemap before you edit it.

Do you need one?

Ask three questions before you build anything.

  1. Can crawlers already see the media? Google's image sitemap documentation says an image sitemap is most useful for images it might not otherwise find, such as images a page loads with JavaScript. Otherwise Google discovers images from the page's HTML. If your images are normal <img> elements in server-rendered HTML, a separate file adds little.
  2. Is video a main part of the site? Google recommends video sitemaps, and also supports mRSS feeds, to help it find and understand videos, especially new ones that normal crawling might miss. If video is incidental, structured data and good page markup may be enough.
  3. Do you publish news? News tags apply to news publishers. They describe only articles from the last two days.

If the answer to all three is no, skip this guide and spend the time on page quality, internal links and a clean base sitemap. If you answered yes to any, continue.

Step-by-step instructions

Step 1: Choose between a separate file and tags in your main sitemap

Why: both are valid, and the choice is about maintenance.

Action: Google says you can create a separate image sitemap or add image tags to an existing sitemap, and that both are equally fine. For news, it says either works, but a separate sitemap may make tracking in Search Console easier. Pick the option your sitemap generator supports. Remember the standard limits apply to every file: 50,000 URLs and 50 MB uncompressed. If you outgrow one file, use a sitemap index.

Confirm: you can say in one sentence where each kind of data will live.

Step 2: Build an image sitemap

Why: it names the images that belong to each page, including ones the page loads with scripts.

Action: add the image namespace, and for each page URL add one <image:image> block per image with an <image:loc>.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
  <url>
    <loc>https://www.example.com/products/blue-mug</loc>
    <image:image>
      <image:loc>https://www.example.com/img/blue-mug-front.jpg</image:loc>
    </image:image>
    <image:image>
      <image:loc>https://www.example.com/img/blue-mug-side.jpg</image:loc>
    </image:image>
  </url>
</urlset>

Only image:image and image:loc are required. Google removed image:caption, image:geo_location, image:title and image:license from its documentation, so do not add them. Each <url> can hold up to 1,000 image entries. If images are hosted on another domain or a CDN, Google says both domains must be verified in Search Console, and your robots.txt must not block the images you want indexed. For file formats and alt text, see WebP and AVIF and image SEO.

Confirm: every image URL loads, returns 200 and is not blocked.

Step 3: Build a video sitemap

Why: it gives Google the details it needs to understand each video and where to find it.

Action: add the video namespace and a <video:video> block per video.

<?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/glaze-basics</loc>
    <video:video>
      <video:thumbnail_loc>https://www.example.com/thumbs/glaze-basics.jpg</video:thumbnail_loc>
      <video:title>Glaze basics for beginners</video:title>
      <video:description>A short walkthrough of mixing and applying a first glaze.</video:description>
      <video:content_loc>https://www.example.com/media/glaze-basics.mp4</video:content_loc>
      <video:duration>312</video:duration>
      <video:publication_date>2026-10-01T08:00:00+00:00</video:publication_date>
    </video:video>
  </url>
</urlset>

Required: thumbnail_loc, title, description (up to 2,048 characters) and at least one of content_loc (the media file, preferred) or player_loc (a player URL, for embeds). Useful optional tags include duration (1 to 28,800 seconds), publication_date, expiration_date, family_friendly, restriction and platform. The content_loc and player_loc values must each differ from the page <loc>, and the files must be reachable by Googlebot, with no robots.txt block, firewall or login. Streaming protocols are not supported. Do not list videos unrelated to the page's main content. The title and description should match what the page shows. Tags Google no longer documents include category, gallery_loc, price and tvshow.

Confirm: each video page loads the video, and the file or player URL is public.

Step 4: Build a news sitemap (publishers only)

Why: it tells Google about fresh articles.

Action: add the news namespace and one <news:news> block per article.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:news="http://www.google.com/schemas/sitemap-news/0.9">
  <url>
    <loc>https://www.example.com/news/town-council-vote</loc>
    <news:news>
      <news:publication>
        <news:name>The Example Gazette</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-10-29T07:30:00+00:00</news:publication_date>
      <news:title>Town council approves new library budget</news:title>
    </news:news>
  </url>
</urlset>

Rules from Google's documentation: one <news:news> per <url>; up to 1,000 per sitemap; include only articles from the last two days; update the same file rather than creating a new one each time; and after two days remove the URL or remove its news metadata. The publication name must match the name on news.google.com, without anything in parentheses. The date is the original first-publication date, not the date you added the URL. The title is the headline as shown, without author, publication name or date. The documentation does not describe eligibility rules for Google News, so a news sitemap alone should not be treated as a route into it.

Confirm: only recent articles are present, and dates and titles match the pages.

Step 5: Publish, reference and submit

Why: Google has to find the file.

Action: upload to your site root or the directory that covers the URLs inside it, because a sitemap affects only descendants of its parent directory unless submitted through Search Console. Add a Sitemap: line to robots.txt with the full URL, or submit it in the Search Console Sitemaps report. Use UTF-8 and escape special characters such as ampersands in URLs.

Confirm: the file loads anonymously and the Sitemaps report shows Success.

Step 6: Keep the files accurate

Why: stale entries waste attention and invite errors.

Action: regenerate whenever media or articles change. Remove entries for deleted pages. For videos that expire, set expiration_date. Check the report weekly for the first month. If listed URLs error out, see fixing 404 and 500 errors in sitemaps.

Confirm: no listed page returns an error or redirect.

Final verification checklist

  • The base sitemap is valid and lists canonical, indexable URLs only.
  • The image, video or news namespace is declared once per file.
  • All required tags are present for each entry, and no deprecated tags are used.
  • Every media URL and page URL returns 200 and is not blocked by robots.txt.
  • Video titles and descriptions match the page; news dates and names follow the rules.
  • No file exceeds 50,000 URLs or 50 MB uncompressed; news files stay at or under 1,000 articles.
  • The sitemap is referenced in robots.txt or submitted in Search Console.
  • Search Console shows Success.

Common mistakes to avoid

  • Building an image sitemap for images already in plain HTML. It adds maintenance for little gain.
  • Adding deprecated image tags. Caption, geo location, title and license are no longer documented.
  • Using the page URL as the video file or player URL. They must differ from <loc>.
  • Listing videos Googlebot cannot fetch. A login, firewall or robots.txt block defeats the entry.
  • Leaving old articles in the news sitemap. Remove them after two days.
  • Using the sitemap date as the publication date. Use the original first-publication date.
  • Blocking CDN images. Check robots.txt on the CDN host too.
  • Expecting the file to produce results. It informs; it does not force indexing.

Frequently asked questions

Can I put image, video and news tags in one sitemap?

Yes, as long as the file declares the right namespaces and stays within size limits. Separate files can be easier to monitor.

Is a video sitemap better than structured data?

They do different jobs, and Google's video page treats the sitemap as one of several ways to tell it about videos, including mRSS feeds. This guide does not rank them.

Do I need an image sitemap if I use lazy loading?

Not always. Images that are present in the HTML or the rendered page can be found from the page itself. Images that appear only after a script runs or after a user interaction are the risky case, and Google does not load content that needs interaction. Test with URL Inspection.

Do Bing and other search engines read these extensions?

The extension namespaces here are Google's. This guide does not verify how other engines treat them, so check their documentation.

Official references

Next step: See how Crawvix checks a website and capture a baseline once scanning opens. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.