Google Merchant Center AI product images · 12 min read
Google Merchant Center AI Product Images: IPTC DigitalSourceType Compliance
Google Merchant Center allows generative AI product images when they carry IPTC DigitalSourceType metadata identifying AI origin—commonly TrainedAlgorithmicMedia—and that metadata must not be stripped. The same rule applies across image_link, additional_image_link, and lifestyle_image_link. Fashion teams often lose tags in CDN resize or recompression. DIY generation rarely owns end-to-end feed compliance; a managed studio can bake metadata into approved delivery. Pair compliance with garment-fidelity QC before you scale Shopping volume.
By Surajnarayanan SUpdated
At a glance
- AI images allowed when correctly tagged — follow current Merchant Center Help
- Preserve IPTC DigitalSourceType through export, resize, and CDN
- Decide who owns feed-ready delivery: DIY ops vs managed catalogue
8M Studio is a managed production studio, not a self-serve AI tool and not a Merchant Center account manager. Follow current Google Help if it differs from this summary.
Direct answer
Follow current Google Merchant Center Help for Shopping submission. Preserve IPTC DigitalSourceType on the image URL Google crawls, then pair that tag with garment-fidelity QC before you scale.
Best for
- +Fashion ecommerce ops shipping AI on-model or AI-edited catalogue images to Shopping
- +Teams that already generate AI images and need the Merchant Center disclosure rule
- +Buyers comparing DIY exports with managed delivery that can include channel hygiene
Not designed for
- -Invented disapproval timelines, or a claim that generative AI images are prohibited
- -A substitute for the full Merchant Center product data specification
- -Consumer AI-art tutorials or prompt packs
What Google requires for AI-generated product images
Google Merchant Center allows generative AI product images. The AI-generated content Help says images created using generative AI must contain metadata indicating AI origin via IPTC DigitalSourceType, and that those embedded tags must not be removed. Google’s example of a tool whose tags must be kept is Product Studio. This page follows that Help article. It does not add a ban, a penalty rate or a disapproval timeline Google does not publish there.
Help names three NewsCodes to preserve. TrainedAlgorithmicMedia: the image was created using a model derived from sampled content. CompositeSynthetic: a composite that includes synthetic elements. AlgorithmicMedia: created purely by an algorithm not based on sampled training data. Match the tag to how the image was actually produced. Do not invent edge cases Google does not define.
The same metadata rule applies when those images are used in image_link, additional_image_link and lifestyle_image_link. The image_link specification restates the requirement not to remove DigitalSourceType, alongside the usual rules for an accurate product image. Additional image link uses the same AI metadata language.
Google Help often uses the short NewsCode name. IPTC also publishes a full concept URI. Operators should follow current Merchant Center Help for what Shopping submission expects, and use the IPTC vocabulary when they embed the metadata. This page does not invent a preferred encoding beyond those sources.
TrainedAlgorithmicMedia in plain language
Most generative on-model and AI catalogue images from models trained on sampled content map to TrainedAlgorithmicMedia, which is the value Google Help highlights and the concept IPTC defines as created using generative AI. Read the trainedAlgorithmicMedia concept for the vocabulary, and the Digital Source Type scheme for the wider list.
CompositeSynthetic may apply when a composite includes synthetic elements. AlgorithmicMedia is the code Help reserves for media created purely by an algorithm that is not based on sampled training data. Do not build a private mapping table for every brand technique. Legal and ops should match the tag to the production method the cited sources describe.
Amazon runs a separate rule for photorealistic AI-generated people: a contains-synthetic-performer keyword in XMP dc:subject, written before upload. It is a different field from DigitalSourceType, so an image sold on both channels may need both. See Amazon's AI-generated model image tag. Zalando asks for invisible AI marking in metadata or an invisible watermark without naming a field; see Zalando AI-generated product images.
A correct tag does not make a wrong garment acceptable. Print, lace, colour, neck joins and silhouette are commercial QC. That review is the AI fashion imagery QC checklist and the narrative in why DIY AI fashion images fail on garment fidelity.
Titles and descriptions are a separate track
Image metadata is the subject of this page. Titles and descriptions are a different feed attribute. The same AI-generated content Help points AI-generated titles and descriptions to structured_title and structured_description, with digital_source_type set to trained_algorithmic_media.
Keep that work on the feed spec your merchant ops already own. Do not assume an IPTC tag inside the image file also discloses an AI-written title. They travel in different fields.
Why metadata disappears before Google ever sees it
The generation step can embed the right tag and the URL in image_link can still arrive without it. Loss usually happens in the path after export. DIY routes rarely include feed-compliance ownership by default. That is an operating-model point, not a claim that every tool strips metadata.
CDN resize, recompress and auto-optimize
Many CDNs and storefront image pipelines resize, recompress or convert format unless someone configures them to keep XMP and IPTC. A tag that exists on the master and is missing on the crawled URL has already failed the delivery check, whatever the generator did.
Export, then an editor, then the storefront
Multi-hop files lose tags quietly: tool export, a retoucher, a DAM rendition, a theme optimiser. Each hop needs an explicit keep-metadata rule. Spot-check the final public URL with a metadata reader, not the file that left the generator.
You can spot-check a saved live image with the AI image label checker, which shows the DigitalSourceType value it finds.
Who owns the last mile to image_link
On a DIY route, brand feed ops usually own that verification. A managed studio can bake DigitalSourceType into delivery and check the handoff when that work is in the agreed scope. Ask who signs the live URL before you treat tagging as done.
Delivery path / Not a penalty gauge
Where the tag has to survive
Compliance is the file Google fetches, not the file you first exported.
Embed
Write the IPTC DigitalSourceType that matches how the image was produced.
Preserve
Keep XMP and IPTC through resize, recompress and every intermediate editor.
Verify
Read metadata on the public image_link, additional_image_link or lifestyle_image_link URL.
ControlFollow current Merchant Center Help if the attribute list changes.
Compliance and trust checklist for fashion feeds
- Confirm which SKUs use generative AI or AI-edited synthetic imagery.
- Embed the IPTC DigitalSourceType that matches the production method before upload.
- Verify the tag still exists on the final CDN URL Google crawls.
- Keep product-truth QC separate. A valid tag is not garment fidelity. Use the AI fashion imagery QC checklist.
- Align the apparel image with the image_link Help: the product should be shown accurately, without promotional overlays that Help disallows.
- Name who signs off feed-ready delivery.
Size hygiene is a separate rule
Size is a different rule from AI tagging. Google’s 2026 product data specification update describes a 500 by 500 minimum path, with warnings from 14 April 2026 and enforcement from 31 January 2027. Do not treat that size schedule as the metadata rule. If Help changes the dates, follow the current article.
DIY tools versus managed production on feed compliance
The split is who owns embed, the live URL and the fidelity hold. Self-serve tools are a generation category. They are not scored here. The wider operating-model criteria are in AI fashion tools versus managed production.
| Criterion | DIY or self-serve (typical) | Managed production studio (typical) | Ask before you buy |
|---|---|---|---|
| Metadata embed | Often the buyer’s job after export | Can be baked into delivery when it is in scope | Who writes DigitalSourceType? |
| CDN and image_link last mile | Brand feed or IT | Can deliver feed-ready files and say how to verify them | Who checks the tag on the live URL? |
| Fidelity QC | Buyer review bandwidth | Human QC gates within scope | What are the Accept, Rework and Hold rules? |
| Accountability | Split across the tool and brand ops | One delivery owner within the SLA | Who holds a SKU that cannot be verified? |
Where 8M Studio fits
8M Studio is not a self-serve AI tool, and it is not a Merchant Center agency of record. It is a managed AI fashion catalogue and campaign production studio. When channel hygiene is in scope, delivery can include DigitalSourceType baked into approved files and a check that the handoff still carries the tag. Account setup, feed diagnostics and policy appeals stay with the merchant or their feed partner unless a separate agreement says otherwise.
AI Catalogue Production is the route for recurring Shopping-bound catalogue images under product-truth QC. Campaign Production covers coherent families. Custom AI Production Systems is for a governed pipeline when the bottleneck is the production system itself.
If AI catalogue images are already live, or you are about to scale them, start with a representative input review. Book a production-fit call when you want managed delivery ownership inside an agreed scope. Garment fidelity still has to pass the QC checklist. A compliant tag does not repair print, lace, colour or neck-join drift. That failure pattern is why DIY AI fashion images fail on garment fidelity. When the stall is approved catalogue volume, not only the metadata tag, read fashion catalogue production bottleneck. If the same model must hold across the Shopping book, identity rules are fashion AI identity lock. Shopify brands running those images as a batch on-model programme should read Shopify batch on-model AI product photos. Visual channel rules for Shopify, Amazon Fashion and marketplace catalogues are fashion ecommerce image guidelines by channel. This page stays on Shopping metadata. When the images are a launch family rather than a Shopping catalogue, the route chooser is AI campaign vs catalogue production. When the prior question is whether this brief should use AI at all, the decision boundary is when not to use AI fashion images. When buyers mix a shopper try-on with finished on-model assets, the route distinction is virtual try-on vs on-model catalogue imagery. When the commercial question is a fashion shoot versus a managed AI programme, the cost-driver comparison is fashion shoot cost vs AI production.
Frequently asked questions
Does Google Merchant Center allow AI-generated product images?
Yes. Google Merchant Center Help states that generative AI images can be used when they contain IPTC DigitalSourceType metadata identifying AI origin, and that this metadata must not be removed. Follow the current Help article for image_link and the related image attributes. This page does not add a ban or a penalty rate.
What is IPTC DigitalSourceType TrainedAlgorithmicMedia?
It is an IPTC NewsCode for an image created using a model derived from sampled content. IPTC describes that concept as created using generative AI. Google Merchant Center Help lists TrainedAlgorithmicMedia among the DigitalSourceType values that should be preserved on generative AI images.
Which Merchant Center image attributes need AI metadata?
Per Google’s AI-generated content Help, AI-generated images can be used in image_link, additional_image_link and lifestyle_image_link. Each of those images must carry IPTC DigitalSourceType metadata, and that metadata must not be stripped before Google crawls the URL. Follow the current Help article if the attribute list changes.
What other DigitalSourceType values does Google mention?
Google Help also lists CompositeSynthetic, for a composite that includes synthetic elements, and AlgorithmicMedia, for media created purely by an algorithm not based on sampled training data. Match the tag to how the image was produced. Do not invent mappings the Help article does not give.
Why do AI image tags disappear from my feed images?
Commonly because CDN resize, recompression or a multi-step export strips XMP and IPTC. The generator can be right while the URL Google crawls has already lost DigitalSourceType. Verify the final public image_link, not only the file that left the tool.
Do DIY AI fashion tools handle Merchant Center compliance?
Many DIY routes stop at image generation. Embedding the tag and proving it survives your CDN is usually still the brand’s job, unless a vendor explicitly owns delivery. We do not publish unverified claims that a named tool always strips metadata.
Is AI metadata the same as garment QC?
No. DigitalSourceType is channel disclosure. Garment fidelity — print, lace, colour, neck joins and silhouette — is commercial product-truth QC. Shopping-ready AI catalogues need both. Use the QC checklist for the visual holds and this page for the metadata rule.
What about AI-generated titles and descriptions?
Google’s AI-generated content Help directs AI titles and descriptions to structured_title and structured_description with digital_source_type set to trained_algorithmic_media. Treat that as a separate feed-attribute track from image IPTC tags. An IPTC tag inside the image file does not disclose an AI-written title.
Is 8M Studio a self-serve AI tool or a Merchant Center setup service?
No to both framings. 8M Studio is a managed AI fashion catalogue and campaign production studio. When it is in scope, delivery can include metadata bake-in and channel-ready files. That is not a DIY dashboard and it is not full Merchant Center account management.
How should I start if my AI catalogue is already live on Shopping?
Audit which SKUs use generative AI imagery, verify DigitalSourceType on the live image URLs Google crawls, and fix the delivery step that strips tags. Align visual holds with the QC checklist. Book a production-fit call if you want managed delivery ownership inside an agreed scope.
Evidence and sources
- Google Merchant Center Help says images created with generative AI must include IPTC DigitalSourceType metadata indicating AI origin, and that this metadata must not be removed. Verified 2026-09-26.
- IPTC defines trainedAlgorithmicMedia as digital media created algorithmically using a model trained on captured content. Verified 2026-09-26.
- Commerce images must accurately display the product and meet channel image requirements. Verified 2026-08-05.
- Google Merchant Center Help: AI-generated content - Generative AI images must include IPTC DigitalSourceType metadata, and those tags must not be removed. Also the structured title and description track.
- Google Merchant Center Help: image_link - Main product image attribute, including the AI metadata requirement and product-image guidelines.
- Google Merchant Center Help: additional_image_link - Additional product images. The AI metadata language matches the main image rule.
- Google Merchant Center Help: product data specification update (2026) - Size hygiene only. Do not read this article as the AI tagging rule.
- IPTC Digital Source Type scheme - NewsCodes vocabulary for DigitalSourceType.
- IPTC trainedAlgorithmicMedia - Concept for digital media created algorithmically using a model trained on captured content.
Continue the decision
Need tagged, QC’d delivery for Shopping?
If you ship AI catalogue or on-model images to Merchant Center and need tagged, reviewed, delivery-owned files, start with a representative input review. Keep garment fidelity on the AI fashion imagery QC checklist and the metadata rule on the sources below.