A Merchant Center image is both a photograph and a URL that Google needs to fetch. A beautiful file can fail if the URL expires, requires a login or points to a page instead of the image itself.
Check the visual asset and the delivery path together. This guide focuses on the primary image_link attribute and a practical review process for stores sending product data to Google.
At a glance
- Google announces a 500 × 500-pixel minimum for all products from January 31, 2027; it recommends 1,500 × 1,500 or larger.
- Use a clear image of the exact variant, without promotional overlays.
- Supply a stable, publicly reachable image URL and monitor Merchant Center diagnostics.
Prepare for the announced size change
Google’s image_link documentation announces a 500 × 500-pixel minimum from January 31, 2027, and recommends 1,500 × 1,500 or larger. It also lists limits of 64 megapixels and 16 MB. Preparing sharp 1,500-pixel-plus assets now avoids relying on older, smaller thresholds. Google Merchant Center image_link specification.
As of this guide’s review date, some older troubleshooting pages still describe the previous 100-pixel general and 250-pixel apparel minimums. Use the primary attribute specification and the current account diagnostics when planning an update. Keep the original source, so a future dimension change requires a new export rather than a new shoot.
A square 1,500 × 1,500 export contains 2.25 megapixels. That simple calculation helps distinguish pixel dimensions from compressed file size. A file can be small in megabytes while still containing many pixels; lowering JPEG quality does not change the image’s width or height.
Make the exact product easy to identify
Use the real item and the variant represented by the offer. A neutral background makes color and shape easy to read. Google’s best practices recommend a clean white or light neutral core image and useful additional views; lifestyle photography can serve a separate role. Google’s image best practices.
Create a variant audit with one row per SKU. Check the product title, chosen color, landing-page option and image together. A blue item illustrated by a black version remains confusing even when every technical image check passes. For bundles, make sure the photograph shows what is actually sold together.
Give each supporting image a purpose: another angle, a relevant detail, a scale reference or a use scene. Keep backgrounds and processing coherent enough that a buyer can tell they are looking at the same product.
Keep promotional artwork out of the primary asset
Google disallows promotional overlays and watermarks in the primary image. A logo physically printed on the product is different from one added over the photo. Its specification also describes category exceptions and metadata requirements for generative AI imagery. Google Merchant Center image_link specification.
Use a dedicated clean export for the product feed. Store banners, social ads and sale graphics often contain prices, shipping statements or calls to action that belong in other placements. Naming those exports clearly reduces the chance of a campaign graphic becoming the feed’s main photograph.
Test the image URL outside your account
Copy the image URL from the actual feed and open it in a private browsing window. It should resolve to the intended image without your store administrator session. A product page URL, a temporary editing preview or a signed link that soon expires is a poor source for a durable feed.
- Confirm the URL returns the image rather than an HTML error page.
- Keep the link stable across routine feed refreshes.
- Check that the hosting service permits crawler access.
- Ensure the stated extension matches the real encoded format.
- Preserve required provenance metadata when using generated imagery.
If you work with a developer, ask them to check the response status, content type and crawler access for the exact URL. A successful image in your browser is useful evidence, but a browser with saved access or a cached file can conceal a delivery problem.
Update a rejected image in a controlled way
Read the specific issue in Merchant Center before editing. An image that is too small needs a better source or different export. A crawl issue needs a reachable asset. An inaccurate variant needs correct mapping. Changing unrelated details can make it harder to determine which action fixed the problem.
When replacing an asset, keep the approved source and record the new URL or export version. Confirm the store page and feed agree. Avoid changing URLs on every scheduled refresh, while making deliberate updates traceable. Recheck diagnostics after processing; immediate acceptance is not something a local file review can establish.
Build a small feed-image release checklist
Before updating a large catalog, test several different product shapes and variants. Open the direct image URLs, inspect the landing pages and review the resulting Merchant Center status. Include a pale product, a reflective item and a multipack if your range contains them.
Save the working settings beside your image export preset. That record should include dimensions, format, background treatment, SKU naming and the system that owns the final URL. A predictable handoff between photography, catalog operations and development prevents many avoidable mismatches.
Sources and further reading
Sources reviewed October 14, 2026. Check the linked documentation and your product category before publishing.