How to Fix Google Merchant Center Image Issues in WooCommerce

Fixing WooCommerce product image problems in Google Merchant Center

Fix Google Merchant Center image issues in WooCommerce by correcting image URLs, sizes, promotional overlays, crawl access and product variation images before resynchronizing affected products.

Product images are required for products submitted to Google Merchant Center. A product may have an accurate title, price, description and stock status, but an inaccessible or unsuitable image can still cause a warning, prevent the image from appearing or lead to product disapproval.

WooCommerce store owners commonly encounter image problems after changing a theme, activating an image optimization service, moving the website to another domain, converting images to WebP, configuring a CDN or editing variable products.

Some problems are visual. The image may contain a watermark, promotional text, a border or unrelated objects. Other problems are technical. Google may receive an expired image URL, encounter a blocked request, download an unsupported file or find that the displayed file does not match its extension.

The safest solution is to identify the exact image submitted for the affected offer, correct the original WooCommerce image or integration mapping and then submit the updated product data.

The short answer

When Merchant Center reports a product image issue:

• Open the affected product under “Needs attention.”
• Record the product or offer ID.
• Identify whether the issue concerns the main or an additional image.
• Find the corresponding WooCommerce product or variation.
• Open the submitted image URL directly.
• Confirm that the URL returns the actual image without login, cookies or temporary authorization.
• Check that Googlebot and Googlebot-Image are allowed to crawl it.
• Remove promotional text, watermarks, borders and unrelated elements.
• Use a clear, high-resolution image of the correct product.
• Make sure the image represents the selected variation.
• Upload the corrected image to WooCommerce.
• Use a new image URL when replacing an existing image.
• Clear relevant WordPress, CDN and image optimization caches.
• Resynchronize the affected product.
• Allow Google time to crawl and evaluate the new image.
• Verify the result using the same offer ID.

Do not repeatedly resubmit an unchanged image URL. Google may continue using its previously crawled version until it detects that the image has changed.

Why product images matter in Merchant Center

The main product image is not simply a decorative element. It helps customers understand what is being sold before they open the WooCommerce product page.

Google uses the image supplied through the image_link attribute as the main visual for an offer. Merchant API represents this value through the imageLink product attribute. Other product images can be supplied through additionalImageLinks.

The submitted image should answer a basic commercial question immediately: “What exactly will I receive if I purchase this product?”

An unsuitable image can create uncertainty when it:

• Shows the wrong colour
• Represents another variation
• Includes accessories that are not sold with the product
• Uses a placeholder
• Displays only the store logo
• Shows a collection instead of the individual item
• Crops an important part of the product
• Contains price or campaign information
• Is too small or blurry
• Cannot be downloaded by Google

Correct product images support catalogue accuracy. They do not guarantee impressions, clicks, product approval or sales. Google independently evaluates every offer and determines where it may appear.

Understand the main WooCommerce image

A standard WooCommerce product can contain:

• A main product image
• Product gallery images
• Variation-specific images
• Images embedded in the long description
• Images added by a theme or page builder
• Structured data image references
• Social media images
• Category thumbnails

These images do not all serve the same purpose.

The main product image is normally the most appropriate source for Google’s image_link attribute. Gallery images may be suitable for additional_image_link, while a variation-specific image should represent the exact colour, material, pattern or other visible characteristic selected by the customer.

An image embedded in the product description should not automatically be treated as the primary product image. It may be a diagram, promotional banner, size guide or usage illustration rather than a clean view of the product.

A WooCommerce Google Merchant Center plugin must map the intended image fields correctly. Store owners should not assume that every image visible on the product page is automatically submitted to Google.

Google’s image URL requirements

An image URL must lead directly to a supported image file.

Google’s current image link requirements state that the URL must:

• Begin with http or https
• Point to a supported image format
• Follow valid URL formatting rules
• Use encoded characters where required
• Be accessible to Google’s crawlers
• Contain only one main image value
• Remain stable unless the image is replaced or moved

Supported formats currently include JPEG, WebP, PNG, GIF, BMP and TIFF. The file extension should correspond to the actual format.

For example, a URL ending in .jpg should not return PNG content disguised with an incorrect extension. Incorrect file types or server response headers can produce an unsupported image error even when the image opens in a browser.

The Merchant API’s official product attribute reference identifies imageLink as the URL of the main product image and additionalImageLinks as the list of additional image URLs.

Prepare for the 500 × 500 requirement

Google announced an updated minimum image resolution of 500 × 500 pixels across product categories and marketing methods, with enforcement beginning on January 31, 2027.

Warnings for images below the new resolution began on April 14, 2026. Google explains the transition in its 2026 Merchant Center product data specification update.

WooCommerce stores should not wait until enforcement begins.

A practical image preparation standard is:

• Use at least 500 × 500 pixels.
• Prefer approximately 1500 × 1500 pixels or larger when a suitable original exists.
• Do not exceed 64 megapixels.
• Keep the image file below 16 MB.
• Avoid enlarging a small thumbnail merely to change its pixel dimensions.

Artificially scaling a 150 × 150 thumbnail to 1000 × 1000 does not restore the missing product detail. It usually produces a larger but still blurred image.

The better solution is to find the original product photograph, export it at a suitable resolution and upload a properly optimized version.

Do not submit WordPress thumbnail files

WordPress can automatically create several versions of every uploaded image.

A WooCommerce media attachment may produce URLs containing size suffixes such as:

product-name-150x150.jpg

product-name-300x300.jpg

product-name-768x768.jpg

The smallest versions are useful for website layouts, but they may be unsuitable for Merchant Center.

The integration should use a sufficiently large image rather than the thumbnail rendered by a product card or theme template.

A store owner investigating an image warning should compare:

• The original attachment dimensions
• The main WooCommerce image
• The image URL submitted to Google
• The image displayed on the product page
• The version delivered by the CDN
• The file Google previously crawled

If the original image is large but the submitted URL points to a thumbnail, the issue may be caused by image mapping rather than the media attachment itself.

Make every image publicly accessible

An image can appear correctly to a logged-in store administrator while remaining inaccessible to Google.

This may happen when:

• Hotlink protection blocks external requests.
• A security plugin challenges non-browser traffic.
• The image requires a session cookie.
• A CDN blocks particular countries or user agents.
• The server returns HTTP 403 or 429 responses.
• The file is protected by basic authentication.
• A maintenance page intercepts the request.
• The image URL contains an expired signature.
• A firewall blocks Googlebot-Image.
• The media directory has restrictive permissions.
• The URL redirects repeatedly.
• The image host requires JavaScript.

Test the precise submitted image URL in a private browser window. However, a successful private-window test does not prove that Google can crawl the file.

Also review server or CDN rules and confirm that Googlebot and Googlebot-Image are permitted. Google’s documentation recommends correcting the crawl configuration, reprocessing the data source and allowing approximately 24–48 hours for relevant access changes to take effect.

Do not disable the complete security system merely to solve one image problem. Identify the exact rule affecting public product images and correct its scope.

Use stable image URLs

Image URLs should remain stable during ordinary synchronizations.

Avoid generating a new URL containing a changing timestamp, session token or temporary query value every time product information is submitted. Unnecessary URL changes can force Google to crawl and evaluate the image again.

However, a deliberately new URL is useful when the actual image has been replaced.

Google currently recommends submitting a new, unique image URL for a changed image. A new URL signals the replacement and typically prompts a recrawl within 24–72 hours.

If the file content changes but the URL remains identical, Google states that detecting and recrawling the replacement can take substantially longer—potentially up to six weeks.

For example, instead of overwriting:

blue-chair.jpg

with different content while keeping the same URL, use a controlled replacement such as:

blue-chair-v2.jpg

Do not append a random value that changes during every synchronization. The purpose is to create a stable new identity for the genuinely replaced image.

Remove promotional overlays

The main product image should present the product rather than function as an advertising banner.

Google’s image requirements prohibit promotional elements that cover or accompany the product. Problematic elements include:

• “Buy now” text
• Discount percentages
• Sale prices
• “Free shipping”
• “Best seller”
• “Limited offer”
• Warranty promotions
• Coupon codes
• Store contact information
• Retailer names
• Watermarks
• Logos added over the photograph
• Decorative borders
• Barcodes

A brand mark that physically exists on the manufactured product is different from a retailer logo digitally placed over the image.

For example, a shoe may naturally display the manufacturer’s logo. That does not mean the store should place its own large logo in the corner of every product photograph.

Merchant Center may offer automatic image improvements for some promotional overlay issues. Google explains that the system can attempt to remove overlays and replace the processed image when successful.

Automatic improvement can be useful, but it should not replace good source images. Correcting the WooCommerce image provides the store with greater control and reduces the possibility of the obsolete image returning during a future synchronization.

Show the actual product

The main image should accurately show the product being sold.

Do not use:

• A “coming soon” placeholder
• A category banner
• A manufacturer logo instead of the item
• A generic photograph unrelated to the exact product
• A plain colour square for an ordinary physical product
• A packaging mock-up that does not show the real item
• A collage containing several unrelated products
• A lifestyle image in which the intended product cannot be identified

Google permits limited exceptions for certain categories, but the normal WooCommerce product should use a real and recognizable product image.

If a product is sold as a bundle, the main image should show all items included in that bundle. If unrelated accessories appear in the image but are not included, customers may misunderstand the offer.

The image, title, description, price and product page should communicate the same commercial offer.

Match images to WooCommerce variations

Variable products require careful image mapping.

Suppose a WooCommerce jacket is sold in black, blue and red. If every variation uses the black jacket image, Google may receive an image that conflicts with the submitted colour attribute or selected landing-page variation.

Each visually different variation should normally have an image showing its distinguishing characteristics.

Review variation images when products differ by:

• Colour
• Pattern
• Material
• Finish
• Style
• Personalization
• Packaging
• Set composition

Variations that differ only by size can often share the same image because their visible appearance is essentially identical.

A reliable variation workflow should confirm that:

• Each submitted offer has its own stable offer ID.
• The colour or other variation attributes are accurate.
• The selected image represents that variation.
• The landing page opens with the intended variation selected.
• The displayed price and availability belong to the same variation.
• Related variations use the appropriate item group ID.

Do not use a photograph showing all available colours as the main image for a single colour variation. Additional images can provide wider context, but the primary image should make the selected offer clear.

Use additional images correctly

Google allows additional product images beyond the main image.

Its additional image link documentation currently permits up to ten additional images. These images can show:

• Different viewing angles
• Close-up product details
• The product in use
• Product staging
• Packaging and included contents
• Parts of a bundle
• The complete multipack
• A product worn by a model
• A real-world environment

Additional images still need to follow applicable quality and content rules. They should not be blurry, misleading or dominated by irrelevant retailer information.

The primary image and additional images should have different roles.

The main image should identify the offer quickly and clearly. Additional images should answer further purchasing questions.

For example, a furniture product could use:

• A clean front view as the main image
• A side view
• A back view
• A close-up of the material
• A photograph showing dimensions
• A lifestyle image of the furniture in a room

Do not submit the same image ten times merely to fill every available field. Additional images should provide useful new visual information.

Check WebP and image optimization plugins

WebP is a supported Merchant Center image format. Nevertheless, a WooCommerce store can still experience problems when image conversion is implemented incorrectly.

Common causes include:

• The URL ends in .jpg but the server delivers WebP unexpectedly.
• The original file was deleted after conversion.
• A CDN returns different formats based on browser headers.
• Google receives an HTML error page instead of an image.
• The optimization plugin creates temporary URLs.
• Regenerated thumbnails replace a previously submitted path.
• Lazy-loading placeholders are used as product data values.
• The CDN returns a low-resolution derivative.
• An AVIF-only workflow is used without a supported alternative.

Open the submitted URL and inspect what the server actually returns. The visible filename alone is not sufficient.

Merchant Center needs a supported image response with consistent content, a correct media type and public accessibility.

A WordPress optimization tool should improve website performance without changing the commercial identity or crawlability of the submitted image.

Do not submit lazy-loading placeholders

Lazy loading can improve page performance, but the placeholder used during page rendering should not become the Merchant Center image.

Some themes initially load:

• A transparent pixel
• A low-quality blurred preview
• A generic placeholder
• A data: URI
• A JavaScript-dependent image source

The actual image may be stored in a separate data-src or responsive image attribute.

A properly designed Merchant integration should read the WooCommerce media attachment or canonical image URL rather than extracting the initial placeholder from the front-end HTML.

If Merchant Center displays a blurred or generic image while the product page looks correct after loading, compare the submitted image_link value with the product’s real full-size media URL.

Review redirects and domain changes

Image problems frequently appear after a WooCommerce migration.

For example:

old-store.example.com/wp-content/uploads/product.jpg

may redirect to:

new-store.example.com/wp-content/uploads/product.jpg

A short, permanent redirect can work, but the more reliable long-term approach is to update the product data so it points directly to the current public image URL.

Check for:

• Redirect chains
• HTTP-to-HTTPS loops
• Incorrect domain replacements
• Staging-domain references
• Expired temporary domains
• Mixed-content problems
• Broken CDN hostnames
• Deleted year-and-month upload directories
• Database replacements that changed only page URLs

A product-page migration is not complete until the submitted product and image URLs also reflect the production website.

Why Merchant Center may still show the old image

Correcting the WooCommerce image does not mean every Google surface will update immediately.

The old image may remain because:

• Google has not recrawled the URL.
• The same URL was reused for different content.
• A CDN cache still serves the old file.
• WordPress page cache contains old product data.
• The product integration has not sent an update.
• Another data source is still supplying the old image.
• The product is under review.
• The variation mapping still points to the previous attachment.
• Google is temporarily serving the prior image during recrawling.

Google states that it may continue serving the previous image while a new URL is being processed.

Avoid repeated image replacements during this period. Every new change can make it more difficult to determine which version is being evaluated.

A controlled WooCommerce image correction workflow

Use the following sequence for each affected product.

1. Record the Merchant Center issue

Save the offer ID, issue name, source, affected destination and current submitted image URL.

2. Match the offer to WooCommerce

Confirm whether it represents a simple product, parent product or individual variation.

3. Inspect the exact image URL

Check its accessibility, HTTP response, file format, dimensions, file size and visual content.

4. Correct the source image

Use a clear photograph without overlays, misleading objects or unnecessary borders.

5. Confirm variation accuracy

Make sure the product colour, material, pattern and customization match the image.

6. Upload the replacement

Use an appropriately optimized high-resolution file and a stable, unique URL.

7. Update the WooCommerce mapping

Assign the image to the correct product or variation.

8. Clear relevant caches

Clear only the WordPress, optimization and CDN caches involved in serving the changed image.

9. Resynchronize the product

Use the active authoritative data source or Merchant API integration.

10. Allow time for processing

A new image normally requires crawling and evaluation. Do not assume that a successful submission means immediate visual replacement.

11. Verify the result

Search using the offer ID. Confirm that the correct image appears and the issue has been cleared.

How PW Merchant API fits into image management

PW Merchant API is intended to help organize supported WooCommerce and Google Merchant API product operations.

WooCommerce remains the commercial source of product information and images. PW Merchant API can read supported product data, prepare supported attributes and communicate product operations through Merchant API.

Its role can include helping users:

• Review supported WooCommerce product data
• Work with simple and variable products
• Submit supported image references
• Update product information
• Organize scheduled operations
• Review operation results
• Identify products requiring attention

The exact capabilities of the installed version should always be checked. Store owners should not assume that every gallery image, theme image or third-party variation gallery is automatically included.

PW Merchant API cannot:

• Make an inaccessible image publicly available
• Remove a watermark from the WooCommerce source file
• Correct an unrelated CDN configuration automatically
• Guarantee product approval
• Force Google to recrawl an image immediately
• Control images submitted by another data source
• Override Google’s product data requirements
• Guarantee visibility, clicks or sales

A professional WooCommerce Google Merchant Center plugin helps organize product communication. Image quality and website accessibility still depend on the store’s source data and technical configuration.

Common mistakes when fixing image issues

Replacing the file but keeping the same URL

Google may continue displaying its cached version for an extended period. Use a new stable URL for a genuinely changed image.

Uploading a larger thumbnail

Increasing the pixel dimensions of a small image does not restore detail. Start with a higher-quality original.

Removing the security plugin completely

Broadly disabling security can create unnecessary risk. Correct the specific crawler, hotlink or firewall rule affecting public images.

Using the product gallery’s first image blindly

The first gallery image may be a lifestyle photograph or promotional banner rather than the correct primary product view.

Giving every variation the parent image

This is unsuitable when variations differ visibly by colour, pattern, material or customization.

Using watermarks for brand protection

Digital retailer watermarks and logos can cause promotional overlay issues. Use clean product photography for Merchant Center.

Correcting only Merchant Center

If WooCommerce or the active source still contains the unsuitable image, the old data may return during the next synchronization.

Ignoring another product source

An old feed or plugin may continue supplying the outdated image. Identify the source shown for the affected offer.

Deleting and recreating the complete product

This can change WooCommerce IDs, offer IDs and synchronization relationships. Correct the image without unnecessarily rebuilding a valid product.

Expecting immediate replacement

New images must be crawled and evaluated. A temporary “Under review” status can be part of the normal process.

Frequently asked questions

Why is my WooCommerce product image missing in Merchant Center?

The submitted image URL may be broken, blocked, temporary or incorrectly formatted. The image may also be unsupported, too small or still awaiting Google’s crawl and processing.

What size should WooCommerce product images be for Google Merchant Center?

Prepare images at a minimum of 500 × 500 pixels and preferably around 1500 × 1500 pixels or larger when a good original is available. Google has announced enforcement of the 500 × 500 minimum beginning January 31, 2027.

Can I use WebP images in Merchant Center?

Yes. Google currently supports WebP. Ensure the URL, file extension, media type and returned content are consistent and publicly accessible.

Can I use AVIF as the Merchant Center product image?

Google’s current image-link documentation lists JPEG, WebP, PNG, GIF, BMP and TIFF. Provide a supported alternative instead of relying only on AVIF.

Can I place my store logo on product images?

A digitally added retailer logo or watermark can be treated as a promotional overlay. A manufacturer mark that is naturally part of the physical product is different.

Can the image contain a price or discount message?

No. Price information, calls to action, discount text and other promotional elements should not be placed over the product image.

Should every variation have a separate image?

Every visually different variation should use an image representing its colour, pattern, material or customization. Size-only variations can often share the same image.

How many additional product images can I submit?

Google currently permits up to ten additional images through the additional image link attribute.

Why does Google still display my old product image?

Google may have cached the previous file, the same URL may have been reused, another source may be submitting it or the replacement may still be under review.

How long does an updated image take to appear?

Google states that a new, unique image URL typically prompts recrawling within 24–72 hours. Updating the file while keeping the same URL can take considerably longer.

Should I change an image URL during every synchronization?

No. Use stable URLs. Change the URL when the image is genuinely replaced or moved, not during every routine product update.

Can a CDN cause Merchant Center image problems?

Yes. A CDN can block Google, return a small derivative, serve an unexpected format, use an expired URL or retain an old cached file.

Can automatic image improvements solve promotional overlays?

Google may attempt to remove promotional overlays when automatic image improvements are enabled. Correcting the original WooCommerce image remains the more controlled long-term solution.

Do image file names improve Google Shopping ranking?

A descriptive filename can help internal media organization, but no ranking outcome should be promised. Product eligibility and placement are independently determined by Google.

Can PW Merchant API guarantee image approval?

No. It can help communicate supported product information, but image accessibility, quality and compliance are evaluated independently by Google.

Final checklist

Before considering a WooCommerce product image issue resolved, confirm that:

• The correct Merchant Center offer was identified.
• The authoritative product source is known.
• The submitted image URL opens publicly.
• Googlebot and Googlebot-Image are not blocked.
• The URL returns an actual supported image.
• The extension and returned file format are consistent.
• The image is at least 500 × 500 pixels.
• A high-resolution original was used.
• The file does not exceed 64 megapixels or 16 MB.
• The product is clearly visible.
• Promotional text, watermarks and borders were removed.
• No unrelated products or accessories create confusion.
• The image matches the submitted product variation.
• The correct WooCommerce product or variation was updated.
• A stable new URL was used for a replaced image.
• Relevant WordPress and CDN caches were cleared.
• The active product source resubmitted the update.
• Google was allowed time to crawl and process the image.
• The warning or disapproval was checked again by offer ID.
• No older integration continues submitting the previous image.

Product images are part of the accuracy of a WooCommerce catalogue. A technically valid image URL is not enough if the photograph is misleading, too small or mapped to the wrong variation. Likewise, a perfect product photograph cannot be processed when Google cannot access its URL.

WooCommerce should remain the commercial source of truth for product images. PW Merchant API can help organize supported product operations, while Google Merchant Center independently crawls, processes and evaluates the submitted files.

A controlled workflow based on accessible URLs, clean high-resolution images, correct variation mapping and traceable synchronization makes Merchant Center image problems easier to diagnose, correct and prevent.