Implement the image sitemap extension (image:image, image:loc tags) to help Google discover JavaScript-loaded images
domain: developers.google.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Add the image namespace (xmlns:image="http://www.google.com/schemas/sitemap-image/1.1") to the <urlset> tag of an existing sitemap, or build a dedicated image sitemap
Nest one or more <image:image> blocks inside each <url> entry, up to 1,000 images per URL
Populate each <image:image> block's required <image:loc> tag with the image's absolute URL
Optionally add <image:caption>, <image:title>, and <image:geo_location> for supplementary, non-required image metadata
Submit the sitemap through Search Console's Sitemaps report or API like any other sitemap
Known gotchas
Image sitemaps matter most for images only reachable via JavaScript; images already linked in normal crawlable HTML often don't need a separate entry
The image extension doesn't relax the sitemap's own 50,000-URL / uncompressed-size limits — large sites still need sitemap index files
Not every originally documented image sitemap tag is equally supported today; verify current field support before relying on lesser-used properties
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?