Guide
Image Sitemaps: How to List Images for Google
An image sitemap lists page URLs and the image files on them. Add image:loc, keep the namespace, and validate the file before you submit it.
By Abid Ali, maintainer of OG Scope
Published

An image sitemap tells Google about pictures that a normal page list can miss, including images a site reaches with JavaScript. Google says you can add the image tags to a sitemap you already have, or put them in their own file. Either approach is fine. The page URL stays in loc. Each picture sits in image:loc inside image:image.
The short note on the sitemap generator covers what that tool writes. This page is the markup, the limits, and the checks that sit around that file.
When a page list is not enough
A standard sitemap lists pages. Google can find many images by reading those pages. A Google image sitemap is for the rest: a gallery that loads pictures after a script runs, an image URL that is not in the first HTML, or a file you want named explicitly. Google's image sitemap documentation, last updated 10 December 2025, describes that job. It does not promise that every listed file will be indexed.
The same size rules as other sitemaps still apply. Google's build-a-sitemap documentation caps one file at 50,000 URLs or 50 MB uncompressed. Image entries sit inside a page URL, so the 50,000 count is page URLs, not pictures. One page URL can hold up to 1,000 image:image tags.
Listing a picture does not replace a page that should be indexed. The loc value is the page you want Google to know. The image URL is extra information about that page. List a file under the page where it appears. A header logo can be listed once, or left out when it is only chrome. A file that is only an image, with no page, is not the pattern in Google's example.
The tags Google still reads
The image sitemap tags use the namespace http://www.google.com/schemas/sitemap-image/1.1. Declare it on urlset, usually as xmlns:image. Google's required pair is image:image, which wraps one picture, and image:loc, which is the absolute URL of that file.
<?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://example.com/field-notes</loc>
<image:image>
<image:loc>https://example.com/images/field-notes.jpg</image:loc>
</image:image>
</url>
</urlset>Use a full https address. A path such as /images/field-notes.jpg is not what the example shows. Escape characters that XML treats as markup, the same way a normal sitemap escapes a page URL.
Paste the finished file into the sitemap validator. It counts image:image entries and flags an image: prefix that has no matching namespace declaration. It does not decide whether Google will index the pictures.
Tags Google removed
Google removed image:caption, image:title, image:license, and image:geo_location from its documentation. Older examples still show them. A new file does not need them, and adding them does not restore a feature Google has taken out of the docs. The generator writes only image:loc for that reason.
A caption that matters to readers belongs on the page, next to the picture. The sitemap is a list of addresses, not a place to store the article text.
Images on another host
Google allows an image URL on a different domain, including a CDN, when both properties are verified in Search Console. The host that serves the file also has to allow crawling. A robots.txt rule that disallows the image path keeps Google from fetching the file you listed.
Check the image address in a browser that is not logged in. A 404, a login page, or an HTML error is not an image, even when image:loc is well formed. The same fetch problems are covered for share images in the missing image guide. An image sitemap does not bypass them.
Pictures inserted only after JavaScript runs are a common reason to write the list by hand. The generator reads img tags in the HTML it fetched. It does not run scripts, and it does not add og:image. A background image in CSS is also outside that pass. For those files, put the public image URL in image:loc yourself. The JavaScript meta tags guide is the same limit applied to tags in the head.
What the generator writes
With images turned on, each crawled page can include up to 200 image URLs from src or data-src on img. Data URLs are skipped. A Next.js image optimizer URL of the form /_next/image?url=... is rewritten to the source file when that source can be read. The namespace is added only when the file contains image entries.
That automatic list is a start for pages whose pictures are already in the HTML. It is not a complete Google image sitemap for a gallery that never prints img in the first response, and it stops at 200 images on a page even though Google allows 1,000. After the download, open the XML and confirm the URLs are the files you meant, not icons, tracking pixels, or a resized duplicate of the same photo.
Submit the file you checked
Host the sitemap on the site, then submit it the same way as any other sitemap. The Search Console submission guide walks through the report and the robots.txt line. If Search Console reports that it could not fetch the file, that status is explained on the sitemap errors guide linked from those steps.
After the file is public, submit the address you checked, not a draft path. One image sitemap, or image tags inside the sitemap you already submit, is enough. A second copy of the same URLs does not add a stronger hint.
Check the live URL
Paste the page into the Open Graph checker to see the tags the server sends.
Open the Open Graph checker

