Free check

Google Shopping image issues: what needs fixing?

Image issues fall into two groups: Google can't fetch or use the file, or the image breaks the image rules. Check the link and crawler access first, then size and format, then what is in the picture: text overlays, watermarks, added logos, placeholders and borders are the usual reasons.

Check my product feed

Symptom

Products are disapproved or limited with an image issue, such as an image that couldn't be crawled, is too small, or contains promotional overlays. Sometimes only the main image is flagged, sometimes a whole collection.

The direct answer: open the exact image_link from the feed in a browser. If it doesn't load as an image, fix access first. If it loads, compare it with the requirements in Google's image link help, which we summarise below as read on the review date.

What Google's image help says now

Google's image link help, read on 17 November 2026, states:

These rules change. Check the current page before acting, especially the size requirement and its date.

Possible causes

  1. The image can't be fetched. The link is broken, redirects to an error, or robots.txt blocks Googlebot or Googlebot-image.
  2. The image is too small. Older product photos or thumbnails used as the main image.
  3. Promotional overlays. "Sale", "Free delivery", prices or badges added to the photo. Google's help lists these as reasons for disapproval.
  4. Watermarks or added logos. A stock watermark or your store logo laid over the product.
  5. A placeholder. "Image coming soon", a logo or one generic photo used for several products.
  6. Wrong file type. A PNG saved with a .jpg extension can cause an unsupported image type error.

How to check

  1. Group the issues. In Merchant Center, open Products, then Needs attention, and note which image issue each product has. Different issues need different fixes.
  2. Open the image link. Paste one flagged image_link into a private browser window. Check it loads directly as an image, without a login or a redirect to a page.
  3. Check robots.txt. Open /robots.txt on the domain that serves the image. Make sure Googlebot and Googlebot-image are not blocked from the image path.
  4. Measure it. Save the image and check its pixel size, file size and real format.
  5. Look at it. Is there any text, badge, watermark, border or logo added after the photo was taken? Does it show the actual product?
  6. Check the source. Find which store image the feed uses as the main image. On many platforms it is the first image in the product's media list.

Illustrative example, with invented values: a product's first image is a 400 x 400 PNG with a "20% OFF" banner, served as banner.jpg. That one file has three problems: below the size Google lists, a promotional overlay, and an extension that doesn't match the format.

What the result means

A limitation: Google's help mentions automatic image improvements that can fix some minor overlay issues. If they are on, an image may show differently in Google than in your feed, which can confuse the investigation. Check that setting before drawing conclusions.

How to fix it

Get help when many products are affected and the images come from an app, a CDN or a separate image source that is hard to trace.

What not to do

When to request help

Our product-feed fixes service checks image links, access and content across the catalogue and corrects the source. If image issues sit alongside wider disapprovals, see Merchant Center disapprovals.

Related guides: products disapproved, missing GTIN and the Merchant Center feed checklist.

Sources and updated date

Last checked against official documentation: 18 November 2026. Google has announced changes to image requirements, so check its current help before acting on any size.

Not sure what's wrong?

Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.

Get a free check