Part of the SiteMap Series
Across Module 1 and Module 2, you have built complete competence with standard URL sitemaps. You know what they are, how they work, how to build them, how to host them, how to submit them, how to validate them, and how to maintain them over time. That covers most of what most sites need.
But not all of it.
Some sites have content that does not fit cleanly into a standard URL sitemap. Image galleries, video libraries, news articles, multilingual content. Each of these benefits from richer metadata than a standard sitemap can convey. The sitemaps.org protocol has extensions designed for exactly these cases, and Google supports four of them: image, video, news, and hreflang.
This lesson covers why these specialised types exist, what each one does at a high level, how they fit alongside your standard URL sitemap (you do not replace it, you add to it), and which sites actually need each type. The lessons that follow go deep on the implementation details for each one.
Why specialised sitemap types exist
A standard URL sitemap tells search engines that a URL exists. It can carry some metadata about that URL (the lastmod timestamp, the changefreq and priority hints covered in Module 1), but it does not convey what is on the URL beyond the URL itself.
For most pages, that is enough. The engine fetches the URL, crawls the content, and figures out what is on it through its own indexing process. The sitemap is purely a discovery mechanism, and the discovery half of its job is the only half it needs to do.
For some content types, the engine benefits from richer metadata up front. An image on a page is just “an image” to a standard URL sitemap. To an image sitemap, that same image has a title, a caption, a geographic location, and licence information. The engine can index those details directly from the sitemap rather than relying entirely on what it can extract from the page.
This matters more now than it did at launch. AI Search era engines pulling multimodal results (image, video, audio) benefit from the structured metadata that specialised sitemaps provide. The information that used to be optional has become more useful as search has become richer and more visual.
The four main specialised types Google supports
There are four extensions of the standard sitemap protocol that Google actively supports.
1. Image sitemaps
For sites where images are a significant part of the content or where image search traffic matters. The extension adds image-specific elements (title, caption, geographic location, license) for each image on the URLs in your sitemap. Most relevant for e-commerce, photography, recipe sites, real estate, and news.
2. Video sitemaps
For sites with video content where video search visibility matters. The extension adds video-specific elements (title, description, thumbnail URL, duration, publication date, content URL) for each video on the URLs in your sitemap. Most relevant for sites hosting original video content, tutorial sites, course platforms, and entertainment sites. Less useful for sites that only embed YouTube videos, because YouTube handles the discovery side of that already.
3. News sitemaps
For news publishers wanting articles indexed in Google News and surfaced quickly in news-focused search. The extension adds news-specific elements (publication name, language, publication date, title) for each article. Has strict eligibility criteria – Google News only accepts sites that meet specific editorial standards, so not every news-adjacent site qualifies.
4. Hreflang in sitemaps
For international sites with content in multiple languages or for multiple regions. Hreflang annotations signal which version of a page to serve to which audience based on language and region. Can be implemented in the HTML head, in HTTP headers, or directly in the sitemap (the sitemap approach is often cleanest for larger sites and is covered in its own lesson).
A fifth type, mobile sitemaps, used to be relevant before Google’s transition to mobile-first indexing made them mostly unnecessary. It is covered briefly later in the module for historical context.
How specialised types fit alongside the standard URL sitemap
You do not replace your standard URL sitemap with specialised types. You add to it. Three patterns work for combining them.
Pattern 1: Add specialised metadata inline.
Each <url> block in your standard sitemap can include child elements from the specialised extensions. An image-heavy URL can have <image:image> elements inside its <url> block. A video URL can have <video:video> elements. A multilingual URL can have <xhtml:link> elements for hreflang. The sitemap still functions as a single URL sitemap, just with extra structured metadata.
Pattern 2: Create separate specialised sitemaps.
A sitemap-images.xml separate from your standard sitemap.xml, both submitted to Search Console. The specialised sitemap only contains URLs with the relevant content type. This works well when image, video, or news content lives in a distinct section of your site rather than scattered across all URLs.
Pattern 3: Use a sitemap index that references both.
A parent sitemap_index.xml that points to multiple child sitemaps, including the specialised ones. The most flexible approach for larger sites, and the standard pattern in modern WordPress SEO plugins.
The right approach depends on the size of the site and how the SEO plugin or build pipeline handles it. WordPress plugins like Yoast, Rank Math, and All in One SEO typically use Pattern 1 (inline) for simplicity. Larger sites and custom builds often use Pattern 3 (sitemap index with specialised children).
The later lessons in this module show exactly which pattern to use for each specialised type and stack.
Which sites actually need specialised sitemaps
Not every site needs them. Most sites are fine with the standard URL sitemap from Module 2. The decision to add a specialised type should come from a real reason, not from “everyone should have one”.
You probably need an image sitemap if any of the following apply:
- Images are a meaningful part of your content (galleries, product photos, recipes, real estate listings, portfolios).
- You see significant traffic from Google Images already, or want to start.
- Your images are dynamically loaded in ways crawlers might miss (lazy-loading, JavaScript-rendered).
You probably need a video sitemap if any of the following apply:
- You host original video content on your site, not just embedded YouTube.
- Video search traffic matters to your business or audience.
- Your videos are dynamically loaded, behind interactions, or hosted with limited markup.
You probably need a news sitemap if all of the following apply:
- You are an actual news publisher with an editorial process and a regular publishing cadence.
- You want articles in Google News, which has strict eligibility criteria for inclusion.
- You publish time-sensitive content where minutes of indexing latency genuinely matter.
You probably need hreflang in your sitemap if any of the following apply:
- You have content in multiple languages or for multiple regions.
- You see (or want) international traffic from specific countries.
- Your content varies by audience location in meaningful ways (currency, regulatory disclosures, region-specific stock or pricing).
If none of these apply to your site, the standard URL sitemap from Module 2 is enough. There is no benefit to adding specialised sitemaps “just in case”, and there is some downside in additional maintenance overhead.
Where this leaves us
You now have an overview of specialised sitemap types and know whether your site needs them. The lessons that follow each go deep on one specialised type:
- How to Create an Image Sitemap
- How to Create a Video Sitemap
- How to Create a News Sitemap
- How to Use Hreflang in Sitemaps for International SEO
- Other Sitemap Formats and When to Use Them
- When to Combine or Separate Specialised Sitemaps
Each lesson covers the protocol details, the implementation paths (WordPress plugin, manual, and static generators), common gotchas, and validation specific to that type.
The first specialised type covered is image sitemaps. Even sites that are not heavily image-driven often benefit from one. Most CMSes generate them automatically with the right plugin enabled, and the metadata adds up over time.
Up next: How to Create an Image Sitemap →
This is Module 3: Lesson 1 of The Sitemap Series, a Technical SEO series on sitemaps from first principles, built for the AI Search era.