Image Sitemap: How to Create One in 2026

An image sitemap is an XML sitemap, or an extension of your existing one, that lists your images so Google can find and crawl them even when standard crawling misses them. That happens most often with JavaScript-rendered galleries, lazy-loaded images, and pictures served from a separate CDN domain. Building one is simpler than most guides make it sound, and in 2026 it requires fewer tags than it used to.

Key takeaways

• An image sitemap only needs two tags now: <image:image> and <image:loc>. Google removed the rest from its documentation.
• Up to 1,000 images per URL entry is the hard limit Google's sitemap spec allows.
• It helps discovery, not rankings directly. Alt text and page context still do the ranking work.
• You do not always need one. Skip it if your images already sit in plain HTML on pages Google crawls easily.
• Add it to your existing sitemap or build a separate one. Google says both approaches work equally well.

What is an image sitemap?

An image sitemap is a way of telling Google directly where your images live, either as a standalone XML file or as extra tags added inside your regular sitemap. It exists because normal crawling does not always reach every image on a page, especially when a site relies on JavaScript to render galleries, lazy-loads pictures as the user scrolls, or hosts images on a separate CDN subdomain that Google has to be told about explicitly.

It is a discovery tool, not a ranking tool. Listing an image in a sitemap tells Google the image exists and where to find it; it does nothing to make that image rank higher once found. The two jobs are separate, and mixing them up is the most common misunderstanding people bring to this topic.

Do you actually need an image sitemap?

Not every site benefits equally. An image sitemap earns its place when one or more of these apply to your site:

• Your image gallery or product images load dynamically through JavaScript after the initial page load.
• Images use lazy-loading and sit far down a long page Google may not fully render.
• Images are served from a separate CDN domain rather than your main domain.
• You run a large ecommerce catalog with thousands of product photos, where on-page SEO for ecommerce already has to work harder to get every product page crawled and indexed.

If none of that describes your site, meaning your images sit in ordinary HTML on pages Google already crawls without trouble, a dedicated image sitemap adds little. Google's own guidance treats it as a discovery aid for images that would otherwise get missed, not a requirement for every site.

What tags does an image sitemap need in 2026?

Only two, and this is the part most guides online still get wrong. Google's Search Central documentation, last updated 2025-12-10, states plainly that it removed <image:caption>, <image:geo_location>, <image:title>, and <image:license> from its documentation. What remains is the minimum: <image:image> to wrap each entry, and <image:loc> to give the image's full URL. If you are following an older tutorial that walks you through captions, licensing, or geo-location tags, you are building for a spec Google no longer documents.

The other hard number worth knowing: a single <url> element can carry up to 1,000 <image:image> tags. That is generous for most pages, but a product listing page with more than 1,000 unique images needs to either split across multiple URL entries or prioritize which images actually matter for image search.

How do you create an image sitemap?

The structure is a small addition inside a standard XML sitemap, not a separate format to learn from scratch.

1. Decide standalone or combined. Add image tags inside your existing page sitemap, or build a dedicated image-only sitemap if your image count is large enough to warrant separating it.
2. Wrap each page's images in the <url> block. Inside the existing <loc> entry for the page, add one <image:image> element per image, each containing an <image:loc> with the image's full absolute URL.
3. Use absolute URLs. Every <image:loc> needs the complete URL, including the domain, not a relative path.
4. Keep it under the limits. Stay within 1,000 image entries per URL and the general size limits that apply to any sitemap, covered in our guide to how to make a sitemap.
5. Generate or hand-code it. Small sites can write this by hand; larger catalogs usually generate it programmatically or through a CMS plugin. Our free XML sitemap generator handles the base sitemap structure you would extend with image tags.
6. Submit it in Search Console. Add the sitemap URL under Sitemaps in Google Search Console so Google knows to fetch it, the same as any other sitemap.

A minimal entry looks like this in practice:

<url><loc>https://example.com/product-page</loc><image:image><image:loc>https://example.com/images/product-1.jpg</image:loc></image:image></url>

Does an image sitemap improve your rankings?

Not on its own, and it helps to be honest about that upfront so you spend effort in the right place. An image sitemap solves a discovery problem: getting Google to notice an image exists. It does not solve a relevance problem, which is what actually determines whether that image ranks once Google has found it.

Ranking in Google Images still comes down to the fundamentals: descriptive, honest alt text, a file name that reflects the image content instead of a random string, fast-loading compressed files, and surrounding page text that gives the image real context. Build the sitemap to fix discovery, then invest the bulk of your time in those on-page signals, since that is where the ranking outcome is actually decided.

Common image sitemap mistakes to avoid

• Following outdated tag lists. Tutorials still teaching <image:caption> or <image:license> are working from a spec Google has since removed from its documentation.
• Using relative image paths. <image:loc> requires the full absolute URL; a relative path will not resolve correctly.
• Listing images blocked by robots.txt. If your robots.txt disallows the image path, listing it in a sitemap will not override that block; check the two agree.
• Treating the sitemap as a ranking lever. It is a crawling aid. Skipping alt text and file-name cleanup while relying on the sitemap alone leaves the real ranking work undone.
• Forgetting to resubmit after big catalog changes. A stale image sitemap on a site that adds hundreds of new products monthly quietly stops reflecting what is actually live.

Frequently asked questions

What is an image sitemap? An image sitemap is an XML sitemap, or an extension added to your existing XML sitemap, that lists the images on your pages so Google can discover them even if they load through JavaScript, lazy-loading, or a CDN it would otherwise miss during a normal crawl. It does not directly boost rankings; it improves discovery.

Do I need a separate image sitemap? Only if your images are hard for Google to find normally: heavy JavaScript rendering, lazy-loaded galleries, images served from a different CDN domain, or a large product catalog. If your images sit in plain HTML on pages Google already crawls easily, a dedicated image sitemap adds little. Google says both a standalone image sitemap and adding image tags to your existing sitemap work equally well.

What tags does an image sitemap need in 2026? Only two: <image:image>, which wraps the entry, and <image:loc>, the image's URL. Google's Search Central documentation, last updated 2025-12-10, states it removed <image:caption>, <image:geo_location>, <image:title>, and <image:license> from its documentation, so building an image sitemap around those older tags today is wasted effort.

How many images can one URL have in an image sitemap? Up to 1,000 <image:image> entries per <url> element, per Google's official sitemap documentation. A page with more images than that needs to be split, or you only list the images that matter most for image search.

Does an image sitemap improve my rankings? Not directly. An image sitemap helps Google discover and crawl images it might otherwise miss; it does not carry ranking weight on its own. What actually ranks an image is descriptive file names, real alt text, surrounding page context, and page speed, the same fundamentals Google lists for general image SEO.

How do I create an image sitemap? Add an <image:image> block containing an <image:loc> tag for each image inside the relevant <url> entry of your XML sitemap, using the full absolute image URL. You can hand-code this for a small site, use a sitemap generator plugin, or add it programmatically for a large catalog, then submit the sitemap in Google Search Console.

Do I still need alt text if I have an image sitemap? Yes, always. An image sitemap only helps Google find the image file. Alt text is what tells Google (and screen readers) what the image actually shows, and it is still one of the strongest on-page signals for ranking in Google Images. A sitemap without alt text on the images themselves accomplishes very little.

Should ecommerce sites use image sitemaps? Often, yes, especially for large catalogs where product images load through JavaScript frameworks or a separate CDN domain. If Google Images traffic matters for your product discovery, an image sitemap covering your highest-value product photos is a low-effort way to close a crawling gap most storefront platforms leave open by default.

What to do next

Check whether your images actually need help being found: if your site uses JavaScript-rendered galleries, lazy-loading, or a separate CDN, add image tags to your sitemap using only <image:image> and <image:loc>, submit it in Search Console, then put your real effort into alt text and file names, since that is what determines whether those images rank once found.

If you want a full technical crawl to see exactly what Google can and cannot find on your site, request a free Rankite SEO audit and we will show you the gaps worth fixing first.