Why Does My Image-License Structured Data Refer to the Wrong Product Photograph After the CDN Generates Another Image URL?

Identify the photograph described by each metadata record

Open the product page and list the actual image resources it publishes: main product view, detail crop, lifestyle scene and any responsive derivatives.

Google's image metadata documentation uses ImageObject and identifies contentUrl as the preferred image identifier for the metadata's target.

Record the exact image URL associated with each metadata object. Do not place the product page's HTML URL in contentUrl when the property is intended to identify the photograph itself.

Also distinguish the licensing destination. A page explaining usage rights is not the same resource as the image bytes to which those rights statements apply.

Compare the image URL with the actual delivered asset

Inspect the final rendered structured data and the image URLs used by the page. If a CDN transformation changes the public image address, determine which image the metadata identifies and whether that address remains accessible.

Different resolutions of the same approved photograph may be related derivatives, while a detail crop or a different product angle may be a materially different image. Do not assume that all images in one product family share the same licensing record.

Compare the actual photograph, its version and the rights information authorized for it. A valid URL is not evidence that the named creator or license terms are correct.

Keep source ownership and publication permissions outside the markup generator's assumptions. The metadata can describe recorded information; it cannot establish legal rights that the merchant has not verified.

Hypothetical bottle page with two photographs

Hypothetical illustration—not a Google Images inspection: a fictional bottle page publishes a front photograph and a close-up of the cap. The front photograph is served through a 1200-pixel CDN derivative, while the cap image has a different public URL.

The proposed metadata record for the front photograph mistakenly uses the cap image's URL as contentUrl. The licensing page URL is otherwise unchanged.

The diagnostic compares each ImageObject's contentUrl with the visible image and the merchant's approved asset register. Correcting the mismatch means identifying the intended front image, not changing the license destination to the product page.

The example does not establish that Google has indexed either photograph or displayed licensing information.

Maintain image identity through publishing changes

When the storefront changes image URLs or replaces an approved photograph, update the corresponding image metadata mapping. Do not assume that an unchanged product page URL means the image identity is unchanged.

Verify the public response for each referenced image and the current structured data on the published page. Compare against the authorized image-rights record.

If the same photograph appears on multiple pages, maintain a consistent identity record where practical. If the creative is replaced with a different photograph, review the metadata rather than copying the old creator and licensing fields automatically.

Accept the implementation only when the metadata points to the intended actual image and its licensing information is supported by the relevant records. Google controls whether any supported enhancement appears.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• Google Search Central — Image Metadata in Google Images: Documents ImageObject contentUrl as the preferred identifier for the image associated with licensing metadata.