How to fix Google Merchant Center product disapprovals in WooCommerce
A Google Merchant Center product disapproval means that an offer cannot appear in at least one affected Google destination, country or reporting context.
The product may still exist inside Merchant Center. Its information may have been submitted successfully, and it may even remain eligible for another destination. However, the issue prevents or restricts the product from appearing in the affected context.
For a WooCommerce store, correcting the problem requires more than pressing a resynchronization button.
The store administrator must identify:
- Which product is affected
- Whether the issue applies to one product or the entire account
- Which country and destination are affected
- Which submitted attribute caused the issue
- Whether the problem originates in WooCommerce, the public website, Merchant Center or the account configuration
- Which data source owns the product
- Whether the corrected information has reached Google
- Whether Google has processed the correction
- Whether a manual review is required
The correct objective is not to make the warning disappear temporarily. It is to correct the authoritative source of the problem and prevent the same issue from returning during the next WooCommerce product update.
Understand what a product disapproval means
Merchant Center evaluates products after receiving their submitted information.
A technically accepted product input can later become:
- Approved
- Pending
- Limited
- Disapproved
- Affected by an account-level restriction
- Ineligible for a particular country
- Ineligible for a particular marketing method
- Hidden because it has no intended destination
Google’s processed product information can contain destination statuses and item-level issues. Destination statuses show whether an offer is approved, pending or disapproved for the relevant countries and destinations. Item-level issues can identify the severity, affected attribute and supporting documentation. Google’s Merchant API product issue guide explains this status structure.
This distinction prevents a common misunderstanding:
- API submission accepted means Google received the operation.
- Product processed means Google evaluated the submitted information.
- Product approved means the product is eligible in an applicable context.
- Product visible depends on eligibility, relevance, account settings and other Google systems.
A WooCommerce Google Merchant integration should therefore avoid describing every accepted submission as an approved product.
Separate product issues from account issues
The first diagnostic step is determining the scope of the problem.
A product-level issue normally affects one product or a group of products with similar information.
Examples include:
- Missing price
- Invalid availability
- Mismatched price
- Mismatched availability
- Missing product image
- Image processing failure
- Broken landing page
- Invalid GTIN
- Unsupported attribute value
- Missing shipping information
- Incorrect variation information
- Restricted product content
An account-level issue can affect many or all products, including products whose individual data is otherwise correct.
Examples include:
- Account suspension
- Misrepresentation
- Website verification or ownership problems
- Missing business information
- Inconsistent contact information
- Unsupported checkout conditions
- Missing or inaccurate shipping settings
- Missing return and refund information
- Policy violations
- Account access or authorization problems
Merchant API provides account-level issues separately from individual product issues. Account issues can include their severity, affected destinations and documentation. Google’s account issue documentation describes this separation.
Correcting ten individual products will not resolve an account suspension. Likewise, rebuilding the entire Merchant account is rarely an appropriate response to one missing product image.
Record the exact issue before changing anything
Do not begin with random product edits.
Create an issue record containing:
- WooCommerce product ID
- WooCommerce variation ID, when applicable
- Merchant offer ID
- Merchant account
- Data source
- Content language
- Feed label
- Affected country
- Affected destination
- Google issue title
- Issue code
- Severity
- Affected attribute
- First detected time
- Last checked time
- Submitted value
- Processed value
- Public website value
- Proposed correction
- Review requirement
Google Merchant Center groups affected products under the “Needs attention” area. Filters and downloadable product lists can help identify products affected by the same issue. Google’s Merchant Center issue guidance explains how disapproved products are reviewed in this section.
Recording the issue before editing creates a reliable comparison point. It also helps determine whether hundreds of affected products share one WooCommerce configuration problem.
Use WooCommerce as the correction point
For an integrated store, WooCommerce should normally remain the source of truth for commercial product information.
This means permanent corrections should usually begin in:
- The WooCommerce product
- The relevant variation
- WooCommerce inventory settings
- Product attributes
- Product media
- Shipping classes
- Tax configuration
- Public product templates
- Structured data
- Checkout configuration
- Store policies
Editing a product directly inside Merchant Center may appear to solve the issue, but the next synchronization can overwrite the correction with the unchanged WooCommerce value.
A safe correction process is:
- Identify the affected offer.
- Inspect its current WooCommerce information.
- Inspect the exact variation when applicable.
- Open the public landing page.
- Confirm the cart and checkout result.
- Compare the submitted Merchant value.
- Correct the authoritative WooCommerce or website source.
- Clear relevant caches.
- Submit the updated information.
- Check the processed Merchant product.
- Request a review only when required.
- Confirm that the issue remains resolved after later synchronization.
This process corrects the cause instead of treating Merchant Center as an isolated product database.
Fix price mismatch disapprovals
A price mismatch occurs when Google cannot confirm that the submitted price matches the product landing page or purchase process.
Possible WooCommerce causes include:
- An outdated regular price
- An expired sale price
- A sale start or end time interpreted incorrectly
- Product page caching
- Object caching
- CDN caching
- Variation prices loaded incorrectly
- Currency conversion
- Location-based pricing
- Tax display differences
- Mandatory fees added during checkout
- Dynamic pricing extensions
- Member-only prices
- Structured data containing an old price
- A default variation showing a different amount
- A “starting from” price submitted as the final price
Google requires the submitted amount and currency to match the landing page and checkout. The price should be clearly visible, and the product must be purchasable for that amount by users in the target country. Google’s price attribute requirements provide the applicable rules.
For a simple WooCommerce product, verify:
- Regular price
- Current sale price
- Sale schedule
- Currency
- Tax display
- Visible product-page price
- Structured-data price
- Cart price
- Checkout price
For a variable product, verify the exact variation associated with the Merchant offer ID.
Do not compare the submitted variation price with the lowest price displayed for the parent product. Select the exact colour, size or other options and confirm the resulting amount.
After correcting the price:
- Save the WooCommerce product.
- Regenerate product lookup data if required.
- Clear the product, page and CDN caches.
- Confirm the price in a private browser window.
- Confirm the structured data.
- Add the product to the cart.
- Confirm the checkout amount.
- Send the current price to Merchant Center.
- Wait for processing.
- Inspect the issue again.
Automatic item updates can help Google correct some temporary price and availability differences, but Google states that they are not a replacement for regularly submitting accurate product information. Google’s product approval recommendations confirm this limitation.
Fix availability mismatch disapprovals
Availability must represent whether the customer can actually purchase the product.
WooCommerce provides several related states:
- In stock
- Out of stock
- On backorder
- Purchasable
- Not purchasable
- Published
- Draft
- Private
- Catalogue visibility
- Variation-level stock
- Parent-managed stock
A product can appear as “in stock” in the WooCommerce administration area while remaining impossible to purchase.
Possible causes include:
- Every variation is unavailable
- A required option has no valid selection
- Backorders are disabled
- The product is catalogue-only
- The add-to-cart button is removed
- The product is restricted by country
- A minimum quantity cannot be met
- A variation is disabled
- Stock is stored in an external system
- The page cache shows an old state
- Checkout rejects the product
- The submitted availability belongs to the parent rather than the variation
Google requires the submitted availability to match the landing page and the customer’s ability to receive the product. Delivery restrictions should also be stated clearly. Google’s availability specification explains these requirements.
To correct an availability mismatch:
- Open the exact public product URL.
- Select the relevant variation.
- Confirm the visible availability message.
- Test the add-to-cart action.
- Check the cart.
- Continue to checkout.
- Confirm that delivery is possible to the target country.
- Compare WooCommerce stock settings.
- Correct the source value.
- Clear caches.
- Submit the new availability.
- Confirm Merchant Center processing.
Google advises updating the landing page, submitted product information and applicable structured data at the same time. Prompt submission reduces the period during which the store and Merchant Center disagree. Google’s inaccurate-availability guidance supports this approach.
Do not mark an available product as out of stock merely to stop advertising it. Availability and promotional visibility are different concepts.
Fix landing-page problems
Google must be able to access and understand the product landing page.
A landing-page disapproval can result from:
- HTTP 404 or 500 responses
- Redirect loops
- Excessive redirects
- Country blocking
- Security-plugin restrictions
- Bot protection
- Cookie walls
- Login requirements
- Maintenance mode
- Slow server responses
- Missing product information
- A URL that opens the wrong variation
- Mobile rendering problems
- JavaScript-dependent information
- A page that changes according to IP address
- Different desktop and mobile prices
- A product that cannot be purchased
The page should show the same product represented by the submitted data. It should clearly display the product title, price, currency, availability and purchase action.
Google recommends including important product structured data, particularly price and availability, in the initial HTML whenever possible. This reduces dependence on later rendering and makes the information easier to retrieve. Google’s landing-page requirements explain this recommendation.
Check the page under realistic conditions:
- Logged out of WordPress
- Private browser window
- Mobile device
- Target-country connection where practical
- Cookies cleared
- Exact variation selected
- Cart and checkout tested
- Security and firewall logs reviewed
- Google crawlers not blocked
A page loading successfully for the administrator does not prove that it is accessible to Google.
Fix missing or rejected images
Every Merchant product requires an accessible main product image.
Common image problems include:
- Missing featured image
- Broken image URL
- HTTP access restriction
- Expired signed URL
- Hotlink protection
- Unsupported format
- Image URL redirect failure
- Incorrect SSL configuration
- Image blocked by robots rules
- Placeholder image
- Very small image
- Promotional text
- Watermark
- Logo-only image
- Variation using the parent’s incorrect image
- Image changed without updating its URL
Google requires the main image URL to use a supported format, begin with HTTP or HTTPS and remain crawlable. Google’s image link specification provides the detailed requirements.
For each affected WooCommerce product:
- Confirm that the featured image exists.
- Open the original image URL while logged out.
- Verify its HTTP response.
- Confirm that the image represents the exact product.
- Check the variation image.
- Remove promotional overlays and inappropriate watermarks.
- Confirm that Googlebot and Googlebot-Image are not blocked.
- Replace unstable or expiring URLs.
- Save the corrected product.
- resubmit the image URL.
Google has also announced a minimum requirement of 500 × 500 pixels for all product images, with enforcement scheduled to begin on 31 January 2027. Stores should therefore improve smaller images before enforcement begins. Google’s current product data specification contains the announcement.
Replacing an image at the same cached URL may delay recognition. When an urgent correction is required, using a stable new image URL can help Google identify that the asset changed.
Fix GTIN, brand and MPN issues
Unique product identifiers help Google understand which commercial product is being offered.
The appropriate identifier depends on the product.
A manufacturer-assigned product may require:
- Brand
- GTIN
- MPN when applicable
A custom, handmade, vintage or genuinely identifier-free product may require different handling.
Common WooCommerce identifier errors include:
- A random number used as a GTIN
- The internal WooCommerce product ID submitted as a GTIN
- SKU copied into the GTIN field
- Invalid check digit
- A GTIN belonging to another variation
- Parent GTIN submitted for every variation
- Store name used as the manufacturer brand
- Missing MPN for products that have one
- The same identifier reused across unrelated products
- An identifier invented to remove a warning
Do not create fictional GTINs.
If a product legitimately has no manufacturer-assigned identifier, describe it truthfully and follow the applicable product-data rules. An invented identifier can create a more serious data-quality problem than a missing optional field.
For variable products, confirm that each commercial variation uses its own correct identifier when the manufacturer assigned separate identifiers.
Fix variation disapprovals independently
Every purchasable WooCommerce variation can become a separate Merchant offer.
A variation may have its own:
- Offer ID
- Price
- Availability
- Image
- GTIN
- MPN
- Colour
- Size
- Material
- Pattern
- Product URL or URL parameters
A parent product may remain healthy while one variation is disapproved.
For every affected variation, check:
- The Merchant offer ID maps to the correct WooCommerce variation ID.
- The variation is enabled.
- Its price is defined.
- Its stock is accurate.
- Its attributes are complete.
- Its image represents the selected option.
- Its landing page opens with the correct selection.
- Its identifier belongs to that variation.
- Its item group ID connects it to related variations.
- The submitted colour and size match the page.
Do not resolve one invalid size by changing every variation or deleting the parent product.
If a shared parent description, title template or image rule caused the issue, all related variations may need to be rebuilt and submitted again.
Fix shipping and return inconsistencies
Product approval can also depend on whether the customer receives clear and accurate delivery information.
Check for consistency between:
- WooCommerce shipping zones
- WooCommerce shipping classes
- Product-level shipping restrictions
- Merchant Center shipping settings
- Target countries
- Delivery time
- Shipping costs
- Free-shipping thresholds
- Carrier rates
- Remote-area surcharges
- Return period
- Return cost
- Product exceptions
The customer-facing website should clearly explain shipping and returns. Merchant Center settings should not promise a delivery service that WooCommerce cannot provide.
Google recommends keeping return policies consistent between Merchant Center and the website, including the footer and dedicated policy pages. Google’s shipping and return guidance emphasizes this consistency.
If one product category has different return conditions, document the exception clearly and use the appropriate Merchant configuration instead of publishing conflicting general statements.
Investigate misrepresentation carefully
Misrepresentation is generally an account-level concern rather than an ordinary missing product field.
Potential contributing areas can include:
- Unclear business identity
- Missing contact information
- Inconsistent business name or address
- Incomplete shipping information
- Incomplete return and refund terms
- Unclear payment conditions
- Misleading promotions
- Products that cannot be purchased
- Prices that change unexpectedly
- Unsupported claims
- Missing legal information
- A website that appears unfinished
- Broken navigation
- Policy pages that contradict checkout behaviour
Do not respond by repeatedly resubmitting the product catalogue.
Review the complete customer journey:
- Homepage and business identity
- Contact page
- Physical or registered address where applicable
- Terms and conditions
- Privacy policy
- Shipping information
- Return and refund policy
- Product information
- Cart
- Checkout
- Payment methods
- Order confirmation
- Merchant Center business settings
- Payment profile information
The business name, address and contact details should be consistent across the website and relevant Google settings.
Google’s review guidance recommends auditing website transparency, standardizing business information and confirming that product prices and availability match the landing pages before requesting a review. Google’s review request guidance describes these preparation steps.
PW Merchant or another WooCommerce Google Merchant API plugin can help inspect product data, but no plugin can guarantee that Google will approve an account affected by a policy issue.
Check for competing product sources
A corrected WooCommerce product can become incorrect again if another active source submits an older value.
Possible competing sources include:
- An older WooCommerce integration
- An XML feed
- A scheduled file
- Google Sheets
- Manual Merchant products
- Automatically found products
- A previous Content API connection
- Another Merchant API application
- A supplemental source
- An external inventory system
For the affected offer, verify:
- Merchant account
- Data source ID
- Offer ID
- Content language
- Feed label
- Last update time
- Source that currently owns the product
If the corrected API source sends a price of 80 but an old scheduled source later submits 75, the mismatch can return even though WooCommerce is correct.
Do not delete sources without identifying their purpose. First determine which system should remain authoritative, stop the unwanted submission process and then manage the old source deliberately.
Resubmit corrected information safely
After correcting WooCommerce, submit only current verified information.
The operation may involve:
- A full product reinsertion
- A partial update
- A variation update
- An image URL update
- A stock update
- A deletion followed by controlled insertion
- A scheduled refresh
Do not send an outdated job created before the correction.
The synchronization worker should rebuild the product from its current WooCommerce state immediately before submission. This prevents a delayed queue item from restoring the incorrect price, stock status or image.
Record:
- Correction time
- WooCommerce modification time
- Submission time
- Operation type
- Submitted attributes
- API response
- Processing status
- Remaining issue
- Final outcome
Repeated submissions of unchanged incorrect data do not improve the result and may make diagnosis more difficult.
Verify the processed result
Do not stop after receiving a successful API response.
Inspect the processed product and confirm:
- The offer ID is correct.
- The product belongs to the intended source.
- The corrected value appears.
- The product has been processed.
- The affected destination status changed.
- The affected country is no longer disapproved.
- The item-level issue disappeared.
- No new issue was introduced.
- Related variations remain correct.
- No duplicate-looking offer was created.
Merchant API also provides aggregate product status information for monitoring approved, pending and disapproved products. Google notes that aggregate results can be delayed by more than 30 minutes after a product is inserted or updated. Google’s aggregate product status guide documents this delay.
A short processing delay should not be mistaken for a failed correction.
Request a review at the correct time
Some corrected product-data issues are reviewed automatically after updated information is processed. Other issues provide a website check, review request or appeal option.
Request a review only when:
- The source problem has been corrected.
- The public website reflects the correction.
- Caches have been cleared.
- The corrected data has been submitted.
- Merchant Center has received the updated information.
- Supporting policies and business details are consistent.
- The review option is appropriate for the issue.
If the issue is genuinely incorrect, use the available disagreement or appeal process and provide accurate evidence.
Do not state that an issue is fixed when the website still displays the conflicting information.
Google explains that merchants can request a review after correcting applicable product or account issues, while some product updates can trigger automatic reconsideration. Google’s disapproval correction guidance describes the available paths.
Account reviews commonly require more time than ordinary product processing. Google notes that some account reviews typically take around seven business days and may take longer in complex cases. Google’s misrepresentation policy guidance provides this timing information.
Avoid submitting repeated review requests before completing a full correction. Review opportunities may be limited depending on the issue and account history.
Prevent the disapproval from returning
A corrected product should remain under observation.
Create automated or scheduled checks for:
- Price differences
- Availability differences
- Broken landing pages
- Missing images
- Expiring image URLs
- Invalid identifiers
- Variation mapping
- Source ownership
- Products with no destinations
- New account issues
- Products approaching expiration
- Queue failures
- Expired authorization
- Stopped scheduled workers
Repeated issues often indicate a system-level cause.
Examples include:
- Price mismatches after every scheduled sale
- Availability mismatches for all variable products
- Image failures after CDN URL changes
- Broken pages after permalink updates
- Shipping problems for one country
- Identifier errors after bulk product imports
- Old values restored by another data source
When several products share an issue, correct the shared WooCommerce rule, template, importer or integration instead of editing every product manually.
How PW Merchant supports issue resolution
PW Merchant is designed to provide a controlled connection between WooCommerce and Google Merchant Center through Merchant API.
Depending on the configured store and account environment, it can support:
- WooCommerce product inspection
- Missing product data detection
- Product and variation relationships
- Merchant account connection
- API data source selection
- Price and availability submission
- Controlled background processing
- Product submission history
- Google-side issue visibility
- Approved, pending and disapproved status separation
- Safe product refresh
- Reconnection and reset workflows
PW Merchant does not replace Merchant Center policies, website compliance or Google’s review process.
It cannot guarantee:
- Product approval
- Account approval
- Advertising visibility
- Free-listing visibility
- Policy acceptance
- Campaign performance
- Sales results
The store owner remains responsible for product accuracy, business transparency, landing pages, pricing, stock, shipping, returns and checkout.
The purpose of a WooCommerce Google Merchant API plugin is to make the technical product workflow easier to inspect, control and verify.
Frequently asked questions
Why are my WooCommerce products disapproved in Google Merchant Center?
Common causes include mismatched price or availability, missing images, inaccessible product pages, invalid identifiers, incomplete shipping information, restricted products and account-level policy issues.
Does a successful API submission mean that the product is approved?
No. A successful submission means Google accepted the input operation. The product must still be processed and evaluated for the applicable country and destination.
Should I edit the product in Merchant Center or WooCommerce?
Permanent product facts should generally be corrected in WooCommerce. A direct Merchant Center edit may be overwritten by the next synchronization.
How do I fix a price mismatch?
Compare the submitted price with the exact public variation, structured data, cart and checkout. Correct WooCommerce, clear caches, submit the current price and verify the processed product.
How do I fix an availability mismatch?
Confirm that the exact product or variation can be added to the cart and delivered to the target country. Correct WooCommerce stock and purchasability settings before submitting the updated availability.
Why does Merchant Center still show an issue after I corrected WooCommerce?
The corrected product may not have been submitted yet, Google may still be processing it, an old cache may remain visible or another product source may have restored the incorrect value.
Can I request a review immediately?
Request a review only after the problem is corrected, the public website is updated and Merchant Center has received the new information. Some product changes are reviewed automatically.
Will resynchronizing the whole catalogue fix disapproved products?
Not if the source information remains incorrect. Full resynchronization can resend the same problem across the entire catalogue.
Can a cache cause Merchant Center disapproval?
Yes. WooCommerce may contain the new value while the public page, structured data or CDN still provides the old price or availability.
Should every WooCommerce variation have its own Merchant product?
Every independently purchasable variation should generally have a unique offer ID and its own accurate price, availability, image and identifiers.
Can two Merchant plugins cause product problems?
Yes. They can create competing sources, restore outdated values or produce duplicate-looking offers. One authoritative system should normally control each product identity.
Does automatic item updating replace synchronization?
No. It can reduce some temporary price and availability mismatches, but current product information must still be submitted regularly.
Can PW Merchant guarantee that Google will approve my products?
No. PW Merchant can support inspection, submission and issue visibility. Google controls processing, policy decisions and destination eligibility.
Final disapproval checklist
Before considering a Merchant Center product issue resolved, confirm that:
- The exact issue and severity were recorded
- Product and account issues were separated
- The affected country was identified
- The affected destination was identified
- The Merchant account is correct
- The owning data source is known
- The offer ID is stable
- The WooCommerce product is the source of truth
- The exact variation was inspected
- The submitted value was compared with the public page
- The cart and checkout were tested
- Price and currency match
- Availability reflects real purchasability
- Structured data contains current information
- Product and page caches were cleared
- The landing page is publicly accessible
- Security tools do not block Google
- The main image is accessible
- The variation image is correct
- Product identifiers are genuine
- Shipping information is consistent
- Return information is consistent
- Business details are transparent
- Competing product sources were reviewed
- The corrected product was resubmitted
- Outdated synchronization jobs were prevented
- The processed Merchant product was inspected
- The destination status changed
- The item-level issue disappeared
- A review was requested only when appropriate
- The correction was recorded
- Recurrence monitoring was enabled
Conclusion
Fixing Google Merchant Center product disapprovals in WooCommerce requires a structured diagnostic process.
The Merchant Center issue identifies the affected offer, attribute, country or destination. WooCommerce and the public website reveal the underlying cause. The integration then delivers the corrected information, while the processed Merchant product confirms whether Google accepted the resolution.
Random edits, repeated full-catalogue submissions and premature review requests can make the problem harder to understand.
A dependable workflow begins by separating account-level restrictions from product-level errors. It compares the submitted value with the exact WooCommerce product, variation, landing page, structured data, cart and checkout. It corrects the authoritative source, clears stale caches and submits only current verified information.
The process is complete only after the corrected product has been processed and the affected issue has disappeared.
When product identity, data source ownership and correction history remain traceable, WooCommerce store administrators can resolve Merchant Center disapprovals more efficiently and reduce the risk of the same problems returning.