ItemlumeGOOGLE SHOPPING PRODUCT IMAGES
Review the image, its metadata, and its delivery before using it in a product feed.
Preparing a Google Shopping product image involves more than choosing an attractive scene. The image must represent the sale item, meet the relevant image requirements, retain required AI-source metadata, and be reachable at the URL submitted in Merchant Center. Check the file that your storefront actually serves, not only the copy saved on your computer.
Keep Shopping images and promotional posters separate
Google’s image_link documentation specifies how the main image is supplied and describes product accuracy, image access, and promotional-overlay restrictions. A sale poster with a price badge can be useful on an appropriate promotional channel while being unsuitable as the main Shopping image.
Choose an image that makes the sale item unambiguous. Match the color and material to the selected variant, and inspect the product against the actual source. Keep a separate export for a campaign poster so an expired offer layer is not accidentally reused in the feed.
The background editing and generation comparison can help you decide whether the task calls for source photography, a masked photo, or a reviewed generated composition. A visually convincing image is not, by itself, proof that the product or the feed meets platform requirements.
Treat AI-source metadata as part of the asset
Google’s AI-generated content guidance requires generative-AI images to contain identifying IPTC metadata and says existing source-type metadata must be preserved. It identifies DigitalSourceType and TrainedAlgorithmicMedia, along with source types for synthetic composites and other algorithmic media. Follow the source type that accurately describes how the image was made.
The IPTC vocabulary defines trained algorithmic media as media made with a model derived from sampled content. The tag is information about the creation process, not a claim that the image is accurate or approved.
A filename containing “AI,” a visible disclaimer, or a paragraph on your product page is not the same as embedded image metadata. Ask your image or feed workflow to inspect the actual property in the delivered file. If it is missing, use an appropriate metadata-capable workflow before feed submission. Do not label a generated result as a camera original.
Check the final delivery path, not just the export
| Stage | What to record | Check before continuing |
|---|---|---|
| Source and creation | Product ID, source photo, generation or editing method | The visible variant and creation description are correct |
| Approved master | Accepted asset ID and reviewer | Label, material, geometry, and item count match the product |
| Exported file | Format, pixel dimensions, file size, source-type metadata | The delivered file passes the applicable requirements |
| Storefront or CDN | The actual public image URL used by the feed | The served image remains accessible and retains required metadata |
| Merchant Center | Submitted item, image URL, and reported status | Resolve the account’s actual diagnostics; do not assume approval |
Image optimization and resizing services may create a different file from the uploaded master. Keep a copy of that served file for the final check. A working product page does not prove that its image URL is accessible without a session, and an internal preview is not a feed URL.
Itemlume’s private generation results are intended for account access. Download an approved asset and publish it through your own suitable storefront or image hosting workflow. Do not place a private workspace result address into a public product feed.
Check dimensions and file limits at the time of submission
Read the current image specification and the requirements shown for your account before uploading. Google’s page announces a minimum of 500 × 500 pixels for all products beginning January 31, 2027. The page also contains size guidance in its requirements section; use the effective date and current account guidance when planning a migration.
A ratio such as 1:1 describes the shape of the canvas, not its pixel dimensions, sharpness, or file size. Inspect the exported file properties. Enlarging a small image does not restore missing label detail, and a large file can still show the wrong product.
Store one approved master and derive destination-specific exports from it. Record which export was actually uploaded so a later crop, compression change, or metadata repair can be traced without replacing every asset in the campaign.
Use a final five-part review before submitting
- Confirm the sale item.Compare the image to the actual product variant and destination. Resolve altered color, packaging, geometry, and included-item ambiguity.
- Confirm the image role.Decide whether it is the main product image or a supporting view, using the current field-specific requirements.
- Inspect the file.Check the supported format, dimensions, file size, and applicable AI-source metadata on the final served version.
- Verify delivery.Open the actual feed image URL without signing in and confirm that the correct image is returned. Have your storefront operator check crawler access where needed.
- Review the reported outcome.Submit through your Merchant Center workflow and inspect its actual item diagnostics. Record the status and fix the specific issue reported.
A feed submission, an accepted upload, and an approved listing are different states. Likewise, Shopping approval does not mean an ordinary web page has been indexed or ranked. Keep the feed record separate from Search Console or general website SEO reporting.
This checklist narrows the image handoff task; it is not a substitute for the full policies applying to the product and account. For a product hosted on Shopify, see the catalog image workflow for source preparation and storefront review.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are Itemlume editorial guidance, not independently measured results.
Frequently asked questions
Can AI-generated images be used in Google Shopping?
Google documents AI-generated images for its image attributes and requires identifying metadata. The image and product must also meet the applicable requirements. Generating or uploading an image does not establish approval.
Does Itemlume automatically add the required Google Shopping metadata?
The current workflow does not provide a verified guarantee that required IPTC source-type metadata is written or preserved through export and hosting. Inspect the final served image and complete the metadata work separately before submission.
Can I use a private Itemlume result URL in my feed?
Use your own appropriate public storefront or image hosting workflow after downloading and reviewing the asset. Private generation result URLs are not a reliable public image delivery method for a Shopping feed.
Is a square export automatically compliant?
No. The aspect ratio says nothing about the file’s dimensions, source metadata, product accuracy, accessibility, or promotional content. Check those separately against the current requirements.
BUILD FROM A PRODUCT YOU KNOW
Put this workflow into practice with your own product.
Explore the relevant tool first. AI copy and concept planning are free after sign-in. Image and video generation require available credits and the applicable account access.
Open Product images Check pricing and credits