Image sitemap checks for missing CDN images in Google
Debug missing CDN images by testing the image sitemap, landing page, and public asset URL separately, including host verification and robots rules.
By Crawlito · 5 min read
In short
- The page URL belongs in loc and the image file belongs in image:loc.
- Google permits a separate image hostname and asks site owners to verify both domains in Search Console.
- An image sitemap can describe a file that still fails when fetched without cookies.
On this page
If an image on a CDN is missing from Google Images, inspect the page URL, the sitemap record, and the image response as three separate things. Put the containing page in loc and the actual image address in image:loc. Then fetch the asset without a browser session to see whether the CDN returns the intended picture. Google’s image sitemap specification
Follow one picture from page to file
Choose an image with an unmistakable detail, such as the label on the rear panel of a particular camera. Find its public product or documentation page. Copy the image address the browser actually requests from its Network panel. The address can differ from the CMS media-library path when a transformation service resizes the original, changes its format, or selects a different width for the screen. Save both addresses and note which one appears in the delivered HTML.
Open the copied asset in a fresh session. A person browsing the page might receive it with a referrer or an existing cookie; a request from a new client can take another path. Check whether the response is an image, whether it visually matches the intended file, and whether it survives a second fetch later. A rotating signed URL may work throughout your debugging session and expire by the time a consumer follows a saved link.
Look at the page itself as well. Is the picture a meaningful part of an accessible document, accompanied by a caption or surrounding explanation that identifies it? A CDN filename like a18492.webp carries little editorial context on its own. The image alt text guide helps you describe the image for the person using the page. A sitemap supports discovery and does a separate job from a helpful description.
Validate the XML association
An image extension can live in your existing sitemap or in its own sitemap. The example associates a single file with a single documentation page. The image namespace matters. A filename in a custom tag named picture is insufficient to express the documented extension, even if an XML parser considers the sitemap well formed.
<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/repairs/camera-back-panel</loc>
<image:image>
<image:loc>https://media.example.com/repairs/back-panel.webp</image:loc>
</image:image>
</url>
</urlset>Inspect the generated XML from the public hostname. A CMS preview can use different media origins from a published build. Check for staging hosts, placeholder thumbnails, dashboard preview links, and transformed URLs that need query strings. XML requires an ampersand in a text value to be escaped. A correctly encoded XML representation should decode to the exact intended URL when parsed. Test the decoded address rather than copying an escaped string into the browser.
If several images illustrate different steps on a repair page, pair the appropriate files with that page. A generator that blindly lists the header logo and shared social preview on every URL produces a misleading sample for your audit. Start with images the article actually relies on, then compare the output on a second template. The XML sitemap guide covers the surrounding file and submission workflow.
Inspect the CDN as its own host
Google's documentation allows image URLs on another domain and asks you to verify both domains in Search Console. Work out who controls each public host, including the media domain. A hostname owned entirely by a vendor can have different verification options from a custom host under your organization's domain. Check ownership before selecting a long-term public image address for thousands of pages.
curl -sSL -D image-headers.txt -o image-sample.bin https://media.example.com/repairs/back-panel.webp
file image-sample.binThe file inspection is important. A CDN can send a small HTML challenge with a success status, or return a generic image placeholder with a valid image content type. Check the decoded dimensions and appearance if the returned bytes are an image. Try a known working sibling from the same host. An entire host returning challenges suggests a broader access rule; only one missing size suggests a transformation or origin-path problem.
Check the robots.txt on the asset host for the path you intend to expose. An allowance on the page host covers a different request. If a security or hotlink rule denies requests lacking a referrer, agree with the asset owner on what should be public. Keep authenticated product manuals and customer images in the protected location, and give public illustrations a stable route only when that is how they are meant to be shared. See how to investigate crawler challenge pages.
Prove the repair on a small set
Select a representative page for each image delivery pattern: an ordinary uploaded file, a resized product image, and a diagram served by a separate documentation system. For each, record the public page URL, the fetched image URL, the sitemap association, the file type received, and the time tested. Include a second product with a similar filename so the test catches cases where the CDN delivers the wrong product's image.
Fix the failing layer and rerun the whole path. Updating an expired address in a sitemap leaves a broken on-page image if the template still emits the old URL. Changing the template alone leaves a stale sitemap if that file comes from a different publishing job. Replacing the origin image may leave the old transformed version cached under the same public address. The acceptance test is a complete, reproducible route from a specific public page to the intended bytes.
Search Console can report sitemap processing problems and Search performance by search type. Keep technical acceptance distinct from appearance: the XML is valid, the page is accessible, and the asset downloads successfully are observations you can make today. Whether a search result appears for a chosen query is a separate observation with its own date.
Test a transformed image with a query string
Suppose the original workshop photograph is permanent but the page serves a resized copy using width and format parameters. Extract the image address from the parsed sitemap and compare it character for character with the URL selected on the page. If a generator percent-encodes the entire query or leaves a literal XML entity in the resulting address, the CDN may receive a different transformation request and return a fallback picture. One well-formed XML file can therefore contain a perfectly legal but incorrect image URL.
Compare the fetched images by their content and intended use. A high-resolution diagram with legible part labels and a small blurred preview can both be valid image files delivered successfully by the same service. For a troubleshooting guide, use a representation that a reader can actually inspect. Keep the original reference picture beside the retrieved result during testing. If the transformation service intentionally negotiates a format, record what your request received and judge its content independently of the extension in the path.
Frequently asked questions
Must the CDN use the same hostname as the page?
Google accepts another image domain. Check its ownership and crawl access as documented, along with the page where the image is used.
Can I submit a media-library preview link?
Use a durable public URL that retrieves the intended image. Preview links commonly depend on a session or expire after a short period.
Will a valid image sitemap fix a blocked asset?
It can expose the URL for discovery. The asset server still has to supply the image when requested.
Check the page that supplies the context
Run the free page check on the public landing page. Pair its HTML findings with the separate asset download when you hand the issue to the CDN owner.
Filed under Structure and schema. Topics: sitemaps, images, google, cdn