Fix “Image too small” on Google Merchant Center

The April 2026 enforcement tightening changed the practical floor from 250x250 to roughly 500x500. Items that previously sat at 400x400 with only warnings now face blocking treatment, especially on new submissions. The change wasn't widely announced but consistent across enough accounts to be reliably observed. Google's docs still say "250x250 minimum" but the practical enforcement is at 500x500, and the recommended-for-good-performance threshold is 1080x1080. Anything between 500 and 1080 serves but with suppressed visibility in higher-quality placements.

The thumbnail-instead-of-full-size problem is the most common cause. Many catalog platforms (especially older Shopify themes, WooCommerce installations with default settings) generate multiple image sizes and may serve thumbnails by default in the feed export. The fix is at the feed-generation layer: point image_link at the original or largest available variant, not the auto-generated thumbnail. On Shopify, the URL pattern includes size suffixes (_medium, _large) — replacing these with no suffix or _2048x2048 gets the full-resolution image. On WooCommerce, the equivalent is pointing at the original upload rather than a thumbnail size.

CDN parameters can also cause the issue. Some image-hosting services downscale on the fly based on URL parameters like `?width=300` or `?w=400`. The image you uploaded is high resolution, but the served version is small because of an inherited parameter from the upload pipeline. The way to diagnose this is to audit the actual served URL, not the assumed source. Open each image_link URL directly in browser and check the served dimensions (right-click → View Image Info in most browsers). If the served image is smaller than the upload, the URL is requesting a smaller version.

The Cloudflare/Cloudinary/ImageKit angle catches modern catalogs. These CDNs serve images dynamically based on URL parameters or device detection. A feed URL like `https://res.cloudinary.com/store/image/upload/w_500/products/dress.jpg` is requesting a 500-pixel-wide image specifically. Removing the width parameter (or setting it higher) serves the original size. Most CDNs have a "no transformation" pattern that serves the original — use that for feed URLs.

For catalogs without high-res source images, the only durable fix is re-shooting at proper resolution. AI upscalers can patch in the short term but often introduce artifacts that hurt CTR more than the resolution improvement helps. Subtle artifacts on edges and gradients become noticeable at 1080x1080 even when invisible at 500x500. Original photography at 1080x1080+ is the long-term answer.

The aspect-ratio choice matters here too. Google accepts square (1:1) and landscape (4:3 or 16:9); the recommendation is square. Items submitted as portrait (vertical) sometimes get auto-cropped to square, which can remove important parts of the product. If your photography is portrait by design, pre-crop to square at the feed-generation step rather than letting Google's auto-crop choose.

AI Shopping Feeds' Audit checks every image_link URL for served resolution and flags items below thresholds across all channels (Meta wants 500x500, TikTok wants 600x600, Pinterest wants 600x900). The DPA Creative Editor can render branded creative against your existing clean images at any resolution, which extends the useful life of older imagery while you're building up the high-res catalog — though for items genuinely below 500x500, re-shooting remains the right answer.