Which Sitemap Extensions Should You Enable Per Content Type?

Sitemap extensions let you describe specific kinds of content—images, videos, news articles, and localized pages—inside the sitemap file you already submit to Google.

The question most operators face is not how the tags work, but which extensions are worth the maintenance effort for each content type on their site.

This article walks through that decision per content type, using Google's documented requirements as the baseline.

What a sitemap extension actually does

A standard sitemap tells Google a URL exists.

An extension adds metadata about the content on that URL: which images belong to a page, when a news article was published, or what video is embedded where.

Google supports four extensions: image, news, video, and xhtml (used for hreflang annotations on localized pages).

Each has its own namespace that you declare in the sitemap file.

Extensions are optional.

Google can often discover images, videos, and articles by crawling your pages normally.

The extensions matter most when content is hard to find otherwise—for example, images loaded with JavaScript that a crawler might miss, or videos embedded behind a player.

Image sitemaps: use them when images are hard to discover

Google's documentation describes image sitemaps as a way to surface images the crawler might not otherwise find, such as images your site loads with JavaScript.

If your pages use standard HTML image tags that are easy to crawl, an image sitemap adds little.

If your gallery pages, product pages, or interactive tools load images dynamically, the extension gives Google a direct list of image URLs.

Implementation is light.

You add an image:image block with an image:loc for each image, up to 1,000 images per URL entry.

You can either create a separate image sitemap or add the tags to your existing sitemap; Google treats both approaches the same.

Two practical requirements are easy to miss.

If your images are hosted on a different domain, such as a CDN, that hosting domain must be verified in Search Console.

And your robots.txt must not disallow crawling of the image URLs you list.

Also note that Google has deprecated several image tags, including caption, geo_location, title, and license—so older guides that recommend filling them in are out of date.

When to skip the image extension

If every image on your site sits in a plain img tag on a crawlable page, the extension mostly duplicates what crawling already finds.

The maintenance cost of keeping image lists in sync with your CMS usually outweighs the benefit.

Reserve it for JavaScript-heavy pages, image galleries, or sites where visual search matters to your demand generation.

News sitemaps: only for genuinely timely articles

The news extension is the most restrictive of the four.

Google's guidance is explicit: only include articles created in the last two days.

Once an article is older than two days, remove its URL from the news sitemap or strip the news metadata from that entry.

This means the file needs continuous updating as articles are published and age out.

The required tags are more demanding than the image extension.

Each entry needs the publication name, exactly matching the name shown on news.google.com, plus a language code, the original publication date in W3C format, and the article title.

A sitemap can hold up to 1,000 news entries; beyond that you split into multiple files.

Google recommends a separate news sitemap reserved for news articles, noting this may enable better tracking in Search Console.

It also warns that a news sitemap can legitimately be empty if you have not published recently.

An empty-sitemap warning in Search Console is expected in that case and causes no problems.

Who should use it

Use the news extension only if you publish timely, news-style articles on a regular cadence and want them considered for Google News surfaces.

A company blog publishing evergreen thought leadership does not qualify; those posts belong in your standard sitemap with no news tags.

If your publishing is sporadic, the two-day pruning requirement creates ongoing work for little gain.

Video sitemaps: the richest metadata, the highest effort

The video extension carries the most required information.

Each video entry needs a thumbnail URL, a title, a description, and either the media file location or a player URL.

For videos hosted on platforms like YouTube or Vimeo that allow iframe embedding, you use the player URL rather than the file location.

The description must match what appears on the page, though not word for word, and the title should match the on-page title.

Optional tags let you add duration, publication date, rating, platform and country restrictions, and subscription requirements.

Two tags deserve caution.

The expiration date tag tells Google to stop showing your video after a date—omit it unless the video genuinely expires.

Restriction tags affect search results only; they do not prevent users from finding or playing the video through other means.

Use the video extension when video is a meaningful part of your content strategy and the videos live on pages you want ranked.

If you embed a YouTube video in an occasional blog post, structured data on the page may serve you better than maintaining video sitemap entries.

If you host a library of product demos or webinars on your own pages, the extension is worth building into your publishing workflow so every new video gets an entry automatically.

Hreflang via the xhtml extension: for localized pages

The fourth extension uses xhtml tags to declare hreflang alternates—telling Google which language or regional version of a page corresponds to which audience.

If you operate localized versions of your site, adding these annotations to your sitemap is one accepted way to signal the relationships.

If your site is single-language, skip it entirely.

Combining extensions in one file

Pages often fit multiple extensions at once: a news article that embeds a video and contains images, for example.

Google's combining guide explains that you declare each extension's namespace in the urlset tag.

Then add the tags from each extension inside the relevant url entry, in any order after the loc tag.

One file can carry news, video, image, and hreflang tags together.

The tradeoff is file size.

Google notes that combining extensions increases sitemap file size significantly, and reminds you to respect general sitemap size limits.

For sites with many URLs and rich media, splitting by content type keeps each file manageable.

Use separate image, video, and news sitemaps plus a standard sitemap; this also makes Search Console reporting easier to read.

Google itself suggests a separate news sitemap may enable better tracking, which is a reasonable pattern to extend to other types when size becomes a concern.

A practical decision path per content type

• Standard blog and landing pages: no extensions. A clean standard sitemap is enough.
• JavaScript-loaded or gallery images: image extension, with CDN domain verified in Search Console and robots.txt checked.
• Timely news articles on a regular cadence: a separate news sitemap, pruned to the last two days, with the exact publication name and original publication dates.
• Hosted video libraries or demo pages: video extension, wired into your publishing process so entries stay current; skip expiration tags unless videos genuinely expire.
• Localized pages: xhtml hreflang tags, either in the sitemap or through page-level annotations.

Whatever you choose, verify the result in Search Console rather than assuming the tags are correct.

Google provides a sitemap troubleshooting guide for investigating errors, and a malformed namespace or missing required tag will show up there.

Keeping extensions maintained without adding overhead

The extensions that fail in practice are the ones nobody maintains.

Examples include news sitemaps full of month-old articles, video entries pointing at removed embeds, and image lists that drifted from the CMS.

Before enabling any extension, confirm your publishing stack can update the sitemap automatically.

Most modern CMS platforms and sitemap generators can.

But the mapping between your content model and the required tags—especially the news publication name and video title-matching rules—needs a one-time setup check.

Start with the standard sitemap, and add extensions only where content is genuinely hard to discover or a content type is strategically important.

Review Search Console reports after each addition.

Extensions are a precision tool, not a default setting.

For a broader view of how sitemaps fit alongside other discovery signals, see Sitemap, IndexNow, or Wait: Choosing Your Discovery Signal.

And once discovery brings visitors to content, the next question is measuring what that content earns—Which Attribution Report Type Answers Your Revenue Question? covers that.

If your content team is deciding which assets deserve richer treatment first, Which Lead Score Should You Build First? applies a similar prioritization lens to qualification data.

Source references: developers.google.com; developers.google.com; developers.google.com; developers.google.com.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.