Academy
Product feed image URL requirements
How to choose image links that a product feed can use, and how to avoid variant and access mistakes.
Checked against the sources on 4 October 20267 min read
A product feed image URL should point to a public, direct image that represents the exact product or variant in the row. The link needs to work for someone who is not signed in, remain stable enough for refreshes and match the colour, size or bundle a shopper could actually buy.
Why this matters now
Images feel like the easy field until a channel fetches a login screen, an expired transformation URL or a photo of the wrong variant. A clean image link is not merely an aesthetic detail. It connects the product record to what a customer expects to receive, which is why mismatches damage trust quickly.
What to check first
| Check | What good looks like | What to do if it is missing |
|---|---|---|
| Access | Loads without a session | Make the asset public and stable |
| Identity | Shows the item or variant described | Map variant images separately |
| Format | A normal web image URL | Avoid page URLs and expiring previews |
A practical way to do it
- Open the image URL in a private browser window.
- Check that the image is a direct public asset rather than a storefront page.
- Use the exact variant image when visual attributes change the item.
- Keep the principal product image free from unrelated text and campaign overlays where possible.
- Re-test a sample after a storefront image migration or CDN change.
Common mistakes
- Using a temporary image link generated for an internal preview.
- Pointing every variant to the same image when colour is a key selling attribute.
- Relying on a beautiful lifestyle image that does not show the product clearly.
What this does not mean
A clean product feed makes your catalogue understandable to a receiving platform. It does not guarantee approval, inclusion, ranking, sales or a particular checkout experience. Those decisions and customer-facing flows remain with the platform and the merchant.
The useful habit is simple: correct the source data, then validate the exported feed. Do not patch a one-off file and assume the next shop sync will remember your fix. That is how a tidy launch turns into a slow drift a fortnight later.
See the missing fields in a public shop catalogue before you spend time formatting a feed by hand.
Run a free store checkQuestions
Can I use more than one product image?
Where a platform supports additional images, use them to clarify the item, not to hide a weak primary image.
Why does an image work on my shop but fail in a feed?
The shop may have a signed-in session or render the asset differently from a direct public request.