Images
Main image
feed attribute: image_link
One required image per item: a full https URL to a crawlable product photo in an accepted format.
Google Merchant Center
Required attribute. The URL must be crawlable, in a supported image format, and show the product without promotional overlays.
Meta
Required for a catalogue item as the primary image; unreachable image URLs stop the item being approved.
What the requirement says
- image_link is required: a full URL to the product's main image, up to 2000 characters, in a format the platform can read (JPG, PNG, GIF, WebP, BMP, TIFF).
- The URL has to be publicly crawlable. An image behind a login, blocked by a hotlink rule or stuck in a redirect loop is not usable, no matter how it looks in a browser.
- The image should show the product itself on a plain background, without promotional text, watermarks, borders or placeholder graphics.
- Spaces and special characters in a URL have to be encoded; a raw space is enough to break the link.
- The address should be a secure (https) one, like the rest of the product page: an http:// image URL is blocked as mixed content on an https page.
- The URL must point at a real image file, not at a stand-in: a theme's "no image" graphic, a spacer file or an inline data: URI is not a product photo.
Why products lose visibility when it fails
- No image is a required-attribute failure: an item without an image cannot serve.
- A URL that is not a full http/https address, or that carries unencoded spaces or exceeds 2000 characters, fails the attribute even if the file exists.
- An image the platform cannot fetch commonly causes disapproval — this is the failure merchants find hardest to spot, because the page looks fine to them.
- Placeholder or logo images on the whole catalogue are treated as missing product images and pull the whole feed down.
- A placeholder URL is the worst version of this: the field looks filled in, every check that only counts values passes, and the shopper still sees a grey box or the shop logo instead of the product.
- An http:// image URL works in a browser today but breaks as mixed content the moment it is embedded in an https page, and it is the first thing to go wrong in a move to https.
The checks we run on it
Straight from the audit engine, with the basis each one is judged on. “Commonly suppresses” means the failure is the kind that stops a product serving, so it is weighted more heavily in your score.
| Check | Basis | Requirement | What to do |
|---|---|---|---|
Main image missing criticalcommonly suppressesimage_link_missing | required | Image_link is required — a product with no image cannot serve. | Add an https URL to the product's main image. |
Image URL is not a usable URL importantimage_link_invalid | required | Image_link must be a valid http/https URL in a supported image format. | Use a full https URL to a JPG, PNG, GIF, WebP, BMP or TIFF file, with spaces URL-encoded. |
Main image not reachable importantcommonly suppressesimage_link_unreachable | required | The image must be crawlable — Google has to be able to fetch image_link; this URL did not respond successfully. | Re-upload the image or fix the URL (check it isn't behind a login, a redirect loop, or a hotlink block). |
Image served over http://, not https:// minorimage_link_insecure | data quality | The image URL is an http:// address. Products are browsed on https pages and every modern platform serves images securely, so an insecure image URL is fetched over a weaker connection and is blocked as mixed content in the browser — it is the first thing that breaks when a store moves to https. | Point image_link at the https address of the same file (storefronts and CDNs normally serve both). FeedGuard does not rewrite it for you: the https copy has to exist, and we will not invent a URL that may not answer. |
Image URL is a placeholder, not the product importantimage_link_placeholder | data quality | The image URL points at a stand-in file rather than a photo of the product: a theme's "no image yet" graphic, a spacer, or an inline data: URI. Google's Product structured data guidelines ask that the image represent the item it is attached to, and a placeholder is not the product — shoppers are shown the stand-in. | Upload a real photo of the product (on a plain background, at least 500 × 500 for Meta) and point image_link at that file. A product with no photo yet is worth photographing before it goes into a feed. |
Want to know which of your own products fail this requirement?
Audit my image link free →How to fix it in Shopify
- Images live on the product: Admin → Products → Media. Shopify serves them from its CDN as https URLs.
- Store scans read the variant's featured image, or the product's first image when the variant has none.
- Check password-protected storefronts and app-based image proxies: if we can't fetch the image, the platform can't either.
- Bulk re-check images after a migration or a CDN change — this is when image URLs break most.
How to fix it in WooCommerce
- Products → edit product → Product image (featured image) is the main image. The gallery supplies the additional images.
- Media-library URLs are https by default in a modern WordPress install; older sites still serve http and images that redirect can time out.
- Image-optimisation plugins that rename or inline images are a common cause of feeds pointing at URLs that no longer exist.
Worth knowing
- FeedGuard samples image reachability (the first 30 distinct URLs per scan) and says how many it checked. A sampled check that passes is not a guarantee for the 31st image.
- An image URL that works in your browser but not for a crawler usually means bot protection, a signed URL, or a hotlink block.
- We never rewrite an http:// image URL to https:// for you: the secure copy has to exist, and inventing a scheme the server does not answer on would hide the problem rather than fix it.
- A placeholder is detected from the URL itself ("placeholder", "no-image", "missing", a spacer file, a data: URI). If your theme names its stand-in something else, the URL will pass — check what the file actually contains.
How FeedGuard checks it
- We validate the URL as a full http/https address within 2000 characters with no unencoded spaces, then make a real request to it (HEAD, falling back to a ranged GET) for the first 30 distinct image URLs.
- The report always states how many images were sampled, so a pass is never presented as a guarantee for images outside the sample.
Every failure names the field and shows the value at fault, counted over up to 250 products per scan. A requirement that does not apply to an item is left out of both sides of the score rather than counted as a pass, and a requirement our source cannot see at all is excluded from the score and listed as “not checked from this source” with the reason. Where a value can be corrected without inventing anything, the row is fixed in the corrected CSV you can download; anything we would have to make up (a real barcode, a brand, a price, a category) is listed for you to supply instead.
What each kind of scan can see
A store scan reads the public catalogue the store itself publishes (Shopify's /products.json). A pasted feed URL or an uploaded CSV is the file the shopping platform reads, so every attribute can be judged against it. This is the difference that decides whether a check can run at all.
| Attribute | Store scan (Shopify) | Your feed URL or CSV upload |
|---|---|---|
| image_link | read from the store the variant's or product's first image | read from your file read from your file |
Read the engine's own rules for this requirement on the results page: every failing row links back to this guide. All 49 checks are listed on what we check.
Run the free audit on your store
Paste your store domain, paste your product feed URL, or upload a product CSV. You get a scored report of every requirement above, the products failing each one, the exact fields at fault, and a corrected CSV to download. No account, no card.
Run the free audit on your storeA store scan reads the public catalogue and skips the attributes it cannot see (barcodes and platform-only fields among them); a feed URL or CSV gets the full audit.
Other images requirements
- Additional images
Optional, recommended: extra angles and in-use shots that improve matching and conversion.