AI Product Image Metadata: A Merchant Center Delivery Check

By Dave TanguayPublished Updated Editorial draft

Quick Answer

For AI-generated images submitted through Google Merchant Center, preserve the embedded metadata identifying their digital source. Google specifies IPTC DigitalSourceType and identifies trainedAlgorithmicMedia for generative AI. Verify the actual image file delivered at the submitted URL after editing, resizing, conversion and CDN processing. A caption, alt text or internal asset note does not replace embedded image metadata.

The file in a designer’s working folder may differ from the one a shopping feed supplies. Image optimization can create another format or derivative, so the review needs to follow the image through that delivery route.

Start with the Merchant Center requirement

Google’s AI-generated content guidance requires identifying metadata for generative-AI images and says not to remove embedded source tags. It names image_link, additional_image_link and lifestyle_image_link among the image attributes that can use AI-generated images.

The guidance also distinguishes source types such as compositeSynthetic and algorithmicMedia. Preserve appropriate existing source information instead of replacing every value with a generic label. Have the person responsible for the imagery verify how it was created and edited.

Keep the image requirement separate from Google’s structured attributes for AI-generated product titles and descriptions. A text-field setting does not insert metadata into a picture.

Map the file’s actual journey

Choose one representative product image and identify its source file, editing export, website upload, generated derivatives, CDN delivery and submitted feed URL. Include any background-removal or image-transformation service that creates a new file.

Record which system controls each step. A spreadsheet column saying “AI-generated” can be useful for asset management, but it does not establish what the delivered binary contains.

Checkpoint Evidence to inspect
Source and editing export The actual file, creation record and embedded DigitalSourceType information.
Website derivative The resized or converted file, including the format the feed actually references.
Delivery URL The response’s image file and its metadata after any CDN transformation.
Product data The intended image attribute and exact URL supplied for the correct product or variant.
Repeat verification The responsible owner and a check after export, optimizer or feed changes.

Inspect metadata with a tool that reads the property

Use a metadata inspection tool that supports the relevant IPTC DigitalSourceType information. Inspect a copy of the final delivered image, not only a screenshot of it. Record the URL, time, file format and observed source property.

If the property disappears between two checkpoints, investigate that transformation. Review the exporter or optimizer’s supported metadata-preservation controls, produce a corrected file and check it again. Do not infer successful preservation from an option’s label or from the fact that the picture still looks the same.

A browser or CDN may serve different image formats under different conditions. Confirm which response the submitted URL delivers and review any relevant alternate delivery path. Preserve the original source and the configuration needed to reproduce the intended file.

Check the image as product information too

Google’s image_link requirements cover the submitted image beyond AI metadata. Review the current rules for the actual product, image type and delivery URL. A source tag alone does not establish that a picture accurately represents the item or meets the other listing requirements.

For an illustrative generated lifestyle scene, verify that the represented product, variant and visible features remain accurate. Do not let the generation add an accessory or finish that the customer will not receive. Keep usage rights and asset approvals with the source record.

Make the check repeatable

Keep a short handoff containing the source, export settings, final URL, inspection result and owner. Repeat it when replacing an image, changing formats or introducing a new optimization service. Do not treat one checked file as proof that every product image passed.

Our Shopify development service can scope feed and image-delivery work. For ordinary website image preparation, use the WordPress image sizing guide, while keeping Merchant Center’s separate requirements attached to the feed workflow.

Key Takeaways

  • Preserve the correct embedded digital-source metadata.
  • Follow the file through exports, derivatives and CDN delivery.
  • Inspect the image supplied by the exact feed URL.
  • Review product accuracy and other image requirements separately.

Frequently Asked Questions

Can alt text disclose the source instead?

Alt text serves a different purpose. It does not replace the embedded image metadata required by the Merchant Center guidance.

Does conversion to WebP preserve the property automatically?

Verify the actual tool and delivered output. A format conversion or optimization step can change the file’s metadata even when the visible image looks unchanged.

Does the source tag guarantee approval?

No. The image and product data still need to meet all applicable requirements. This metadata check does not establish listing approval or publication rights.

Archives