How to request a Google Merchant Center review after fixing WooCommerce issues

How to request a Google Merchant Center review after fixing WooCommerce issues

Correcting a WooCommerce product does not always require a manual Google Merchant Center review.

Many product data errors are evaluated again after corrected information reaches Google. Other issues, especially certain policy, account-level and preemptive item disapproval conditions, may present an explicit Request review, I fixed the issue or equivalent action.

The correct process is not simply:

• Edit a WooCommerce product
• Click Request review
• Wait for approval

Before using a review opportunity, the merchant must confirm that the complete problem has been corrected in every relevant system.

That can include:

• WooCommerce product data
• Individual variation data
• Product landing pages
• Structured product data
• Cart and checkout
• Business information
• Contact information
• Shipping settings
• Return and refund information
• Merchant Center account settings
• Product data sources
• Merchant API submissions
• Automatically found products
• Supplemental data sources
• Target countries
• Marketing methods
• Website accessibility

A review request asks Google to evaluate the affected issue again. It does not correct the underlying data, guarantee approval or replace a complete WooCommerce and website audit.

Repeated unsuccessful requests can lead to a cooldown period during which another review cannot be requested. For this reason, the review button should be treated as the final step of a verified correction process, not as a diagnostic test.

The short answer

To request a Google Merchant Center review after correcting WooCommerce issues:

1. Open the affected Merchant Center account.
2. Record the account ID.
3. Go to Products.
4. Open Needs attention.
5. Select View setup and policy issues when investigating an account-level condition.
6. Open the exact issue.
7. Confirm whether the issue affects a product, a group of products or the account.
8. Read the current issue-specific Google instructions.
9. Record every affected country and marketing method.
10. Download the complete affected-product list when available.
11. Match every Merchant Center offer to the correct WooCommerce product or variation.
12. Correct the authoritative WooCommerce, website or Merchant Center source.
13. Check for competing and obsolete product sources.
14. Clear relevant caches.
15. test the public store while logged out.
16. Confirm that product pages, cart and checkout work.
17. Confirm that structured data matches the visible offer.
18. Submit or synchronise the corrected product information.
19. Confirm that the update operation succeeded.
20. Confirm that Merchant Center processed the new value.
21. Allow ordinary product reprocessing to occur.
22. Determine whether a manual review is still required.
23. If the issue is fixed, select I fixed the issue.
24. If the decision is genuinely believed to be incorrect, select the disagreement option provided by Google.
25. Read the confirmation and consequences.
26. Submit the review once.
27. Record the submission date and visible status.
28. Avoid unnecessary changes while the review is in progress.
29. Monitor Merchant Center and the account email address.
30. If the review is unsuccessful, do not immediately submit the same unchanged account again.
31. Use any cooldown period to conduct a wider audit.
32. Request another review only after substantive additional corrections.

Google’s current review request guidance distinguishes between merchants who have corrected an issue and merchants who disagree with Google’s finding.

Choose the response that accurately represents the situation.

Not every correction requires a manual review

A manual review and ordinary product reprocessing are different processes.

A product data issue may be re-evaluated automatically after Google receives corrected information. Examples can include certain:

• Missing attributes
• Invalid attribute values
• Price updates
• Availability updates
• Image changes
• Identifier corrections
• Product category corrections
• Variation-data corrections
• Landing-page corrections
• Data-source formatting errors

The exact behaviour depends on the issue.

Some issues provide a review action. Others disappear only after the corrected product has been submitted, processed and re-evaluated.

Do not search for a Request review button before reading the instructions attached to the specific issue.

A missing review button can mean:

• A manual review is not required.
• The corrected product has not been processed.
• The issue is still being evaluated.
• The action is available on a different issue page.
• The issue must be resolved at account level.
• The account is already under review.
• A cooldown period is active.
• A warning period has not ended.
• The current user lacks sufficient account permissions.
• Google does not currently make another review available.

Creating another data source or deleting the affected products will not necessarily make a review action appear.

Understand the four processes that merchants often confuse

Several different Google processes may look similar from a WooCommerce merchant’s perspective.

They should be recorded separately.

Initial review

When products are added to a Merchant Center account for the first time, Google may conduct an initial review of the products and website.

Google’s current Merchant Center issue documentation lists requirements that can apply before a data source is ready for review, including:

• Required shipping settings
• A data source for the target country
• A verified and claimed website
• A verified business address
• Applicable tax settings for the United States

Google states that the initial review for Shopping ads can take up to three to five business days and may take longer for other programmes.

Products can remain pending during this process.

This is not the same as requesting a new review after an account suspension.

Repeatedly changing products or the website during the initial review may delay completion.

Automatic product reprocessing

When corrected WooCommerce product information is submitted, Google processes the new data.

The resulting product may then move from disapproved or pending to approved without a separate manual review request, depending on the issue.

This is a data-processing and eligibility evaluation cycle.

A successful Merchant API operation confirms that the request was accepted for processing. It does not guarantee that the processed product will be approved.

Requested issue review

Some product or account issues provide an explicit review action.

The merchant indicates either:

• The issue has been corrected.
• The merchant disagrees with the finding.

Google then evaluates the affected issue again.

This is the process addressed by this guide.

Product Reviews and Merchant Reviews

Merchant API contains resources named Product Reviews and Merchant Reviews.

These resources concern customer review content and ratings. They are not the mechanism used to appeal a product disapproval or request the re-evaluation of an account suspension.

Do not use customer-review API documentation when looking for a Merchant Center policy review.

The same word, “review,” describes two unrelated functions.

Start with the exact issue

A review request should always be attached to an identified issue.

Before making any changes, record:

• Merchant Center account ID
• Issue title
• Issue code where available
• Issue type
• Severity
• Product-level or account-level scope
• Affected products
• Affected countries
• Affected marketing methods
• Warning date
• Warning deadline
• Suspension date
• Review availability
• Review status
• Cooldown end date where applicable
• Official documentation link
• Examples supplied by Google

Open:

• Products
• Needs attention
• The relevant issue card
• The Issue Details Page
• View setup and policy issues for account-level conditions

Do not request a review based only on an email subject line or a general dashboard count.

One account can have several unrelated issues. A successful review of one issue does not automatically resolve the others.

Separate product-level and account-level reviews

The scope of the problem determines the required correction.

Product-level issues

A product-level issue affects an individual offer or defined group of offers.

Examples may include:

• Price mismatch
• Availability mismatch
• Invalid GTIN
• Missing required attributes
• Image policy problems
• Landing-page errors
• Invalid condition
• Variation-data inconsistencies
• Preemptive item disapproval

The correction may require editing:

• A simple WooCommerce product
• An individual variation
• A product custom field
• A global attribute
• An integration mapping
• A product image
• A submitted landing-page URL
• Structured product data
• A product data source

Google notes that products targeting multiple countries can receive different warnings or disapprovals because requirements can vary by location.

A product approved for one country may still require correction or review for another country.

Account-level issues

An account-level issue can affect all or many products.

Examples may relate to:

• Business identity
• Website verification and claiming
• Contact information
• Website quality
• Checkout functionality
• Shipping configuration
• Return and refund information
• Policy compliance
• Misrepresentation
• Prohibited business practices
• Account setup
• Linked services
• Repeated product-data problems

Changing one product description does not resolve an account-wide issue.

Before requesting an account review, inspect the entire purchasing experience and every requirement connected to the issue.

Google explains that account-level issues can appear in a banner, in the Needs attention summary or under View setup and policy issues.

Understand warnings before requesting a review

An account warning usually includes a period in which the merchant can correct the problem.

During the warning period, products may continue appearing, although visibility can be limited.

Google states that if identified violating products are removed or the account is corrected during the warning period, the account may be reviewed automatically at the end of that period. The exact issue instructions should determine whether a manual action is required.

Do not assume that every warning must be followed immediately by a manual request.

Record:

• When the warning began
• When the warning period ends
• What Google asked to be corrected
• Whether products remain active
• Whether a manual review option is displayed
• Whether Google states that an automatic review will occur
• Whether the issue applies to all products
• Whether the account has another independent warning

Waiting until the final hours of a warning period is risky. Website crawling, product synchronisation and Merchant Center processing require time.

Complete corrections early enough to verify the resulting public and processed data.

Understand suspensions

An account suspension prevents affected products from appearing through the applicable Google programmes.

Some serious account-level violations can result in immediate suspension without a warning period.

Before requesting re-evaluation of a suspended account:

• Read the exact policy named in Merchant Center.
• Audit the whole website.
• Audit the Merchant Center account.
• Audit the product catalogue.
• Check every target country.
• Check Shopping ads and free listings separately.
• Verify business information.
• Verify contact information.
• Verify shipping and return information.
• Complete any required identity verification.
• Confirm the website is fully functional.
• Confirm that all affected products were corrected or removed.
• Confirm that the data-source updates completed.
• Confirm that no duplicate source restores the old data.

An account suspension review is not limited to the few example products displayed in the interface.

Example products can reveal a pattern. They should not be interpreted as the complete scope of an account-level problem.

Choose “I fixed the issue” only after correcting it

Google’s review flow may ask whether the merchant fixed the issue or disagrees with it.

Choose I fixed the issue only when:

• The reported condition was understood.
• The complete affected scope was identified.
• The authoritative data was corrected.
• The corrected website is publicly available.
• Corrected products were submitted.
• Merchant Center processed the new data.
• Related account settings were updated.
• Competing product sources were addressed.
• All affected countries were checked.
• Every relevant marketing method was checked.
• The correction can be demonstrated with current evidence.

Clicking I fixed the issue is a factual statement.

It should not be used to mean:

• “I do not know what is wrong.”
• “I changed a few pages.”
• “My developer says the site is fine.”
• “The plugin displayed a success message.”
• “I deleted the example product.”
• “I want Google to explain the issue.”
• “I hope the next review will show what remains wrong.”

If the issue has not actually been corrected, another unsuccessful review can consume a limited opportunity and produce a longer cooldown.

Choose the disagreement option carefully

A merchant may believe that Google’s finding is incorrect.

Use the disagreement route only when there is concrete evidence that:

• The product complies with the named requirement.
• The submitted value is correct.
• The landing page confirms the value.
• The policy was interpreted against the correct product.
• The correct country and marketing method were evaluated.
• The website is accessible to Google.
• No competing source supplies contradictory data.
• The business information is verifiable.
• The issue does not apply to another product or page.
• The evidence is current and publicly accessible.

Disagreement is not a substitute for a correction that is difficult or time-consuming.

If the issue is valid, select the correction route and fix it.

If the issue is genuinely incorrect, record the evidence before submitting the disagreement.

Depending on the issue, the review flow may request additional confirmation or information. Answer only what is requested and keep all information accurate.

Complete a WooCommerce product audit before requesting review

For product-related issues, inspect the exact WooCommerce source.

Simple products

Confirm:

• Product ID
• SKU
• Offer ID mapping
• Title
• Description
• Regular price
• Sale price
• Sale dates
• Currency
• Tax treatment
• Stock status
• Quantity
• Backorder configuration
• Product condition
• Brand
• GTIN
• MPN
• Product category
• Google product category
• Main image
• Additional images
• Landing-page URL
• Product visibility
• Purchasing availability

Variable products

Each submitted variation can be a separate Merchant Center offer.

Confirm for every affected variation:

• Variation ID
• Offer ID
• SKU
• GTIN
• MPN
• Price
• Sale price
• Availability
• Image
• Colour
• Size
• Material
• Pattern
• Gender
• Age group
• Item group ID
• Variation URL
• Correct default selection
• Structured-data representation

Correcting the parent product does not necessarily correct its variations.

If three variations are disapproved, checking only the first variation is not a complete correction.

Check the public product page

Merchant Center evaluates the customer-facing experience, not only the WordPress administration screen.

Open the exact submitted landing-page URL:

• While logged out
• In a private browser window
• Without an old currency cookie
• Without an old language cookie
• On desktop
• On mobile
• With the affected variation selected
• With any submitted URL parameters
• Through the public HTTPS address

Confirm that:

• The URL loads successfully.
• The claimed domain is retained.
• The correct product is shown.
• The correct variation is selected.
• The title identifies the same product.
• The displayed price matches the submitted price.
• The currency matches.
• The availability matches.
• The product image loads.
• The product can be added to the cart.
• Required options can be selected.
• The checkout is accessible.
• The payable price remains consistent.
• Shipping information is available.
• Return information is accessible.
• No login is required to view essential information.
• No maintenance or placeholder content is present.

An administrator seeing the correct page does not prove that a logged-out visitor or Google crawler receives the same response.

Check structured product data

WooCommerce themes and extensions can generate Product structured data independently of the Merchant submission.

Inspect:

• Product name
• Offer URL
• Price
• Price currency
• Availability
• SKU
• GTIN
• Brand
• Condition
• Variation identity
• Seller information

Look for:

• Duplicate Product schema
• Different prices in separate schema blocks
• Parent-product data applied to every variation
• Cached sale prices
• Incorrect currency
• Outdated availability
• Schema describing a different product
• Theme and plugin schema conflicts

Correcting WooCommerce without clearing the schema-generating cache can leave old public evidence accessible.

Audit the complete website before an account review

Account-level reviews can examine more than products.

Review:

• Business name
• Legal business identity
• Physical address
• Telephone number
• Business email address
• Contact page
• About page
• Shipping policy
• Return and refund policy
• Privacy policy
• Terms of use
• Payment information
• Product information
• Cart functionality
• Checkout functionality
• HTTPS
• Domain consistency
• Broken links
• Placeholder content
• Unsupported claims
• Promotions
• Stock statements
• Delivery promises
• Refund promises
• Language consistency
• Currency consistency
• Mobile usability
• Customer support access

Information should be consistent across:

• Website header and footer
• Contact page
• Policy pages
• Checkout
• Merchant Center business information
• Shipping settings
• Return-policy settings
• Public business records where relevant

Do not manufacture business details, reviews, certifications, addresses or trust signals merely to influence a review.

All published information should be authentic and verifiable.

Verify the data source update

A saved WooCommerce product does not prove that Google received the correction.

Record:

• WooCommerce save time
• Synchronisation method
• Synchronisation time
• Merchant Center account
• Product data source
• Offer ID
• Submitted values
• Operation result
• Rejected fields
• Processed-product update time
• Processed values
• Current item-level issues
• Current country status
• Current marketing-method status

If a Merchant API request fails, the correction may remain only inside WooCommerce.

If a Merchant API request succeeds, the product still requires Google processing and eligibility evaluation.

Do not submit a policy review while Merchant Center still displays the old incorrect product value.

Check for duplicate and competing sources

Merchant Center can receive product information through:

• Merchant API
• Legacy Content API integrations
• Uploaded files
• Scheduled files
• XML data sources
• CSV or TSV files
• Google Sheets
• Ecommerce-platform integrations
• Automatically found products
• Supplemental data sources
• Manual product entry
• Manual Merchant Center edits

Before requesting review, determine whether an older source still controls or supplements the affected product.

Check:

• Source name
• Source type
• Last update
• Target language
• Feed label
• Countries
• Offer ID
• Primary or supplemental role
• Source schedule
• Source status
• Manual overrides
• Accepted automatic fixes

A corrected WooCommerce product can be overwritten by an obsolete source before Google begins the review.

Do not delete a source only because its name looks unfamiliar. First determine which products, countries and attributes it controls.

Allow corrected data to be processed

Do not click Request review immediately after pressing Update in WooCommerce.

First confirm that:

1. WooCommerce stored the correction.
2. The public page displays it.
3. Structured data displays it.
4. Caches were cleared.
5. The synchronisation ran.
6. The product operation succeeded.
7. Merchant Center processed the new information.
8. The relevant issue still requires a manual review.

Processing times vary.

Google states that review requests may take several business days, but product-data processing, website crawling, initial review and account-policy review are separate processes.

Do not promise an exact completion time.

Where to request the review

The exact interface can vary by account and issue.

Common paths include:

• A Fix button in an account banner
• Review and fix on the Merchant Center home page
• An issue card in Products → Needs attention
• View setup and policy issues
• The Issue Details Page
• A Request review action
• An I fixed the issue action

Follow the action attached to the exact issue.

A general path is:

1. Sign in to Merchant Center.
2. Select the correct account.
3. Open Products.
4. Open Needs attention.
5. Open the affected issue.
6. Select View setup and policy issues for an account-level problem.
7. Read the issue details.
8. Select the available correction or review action.
9. Choose whether the issue was fixed or is disputed.
10. Complete any required confirmations.
11. Submit the request.
12. Record the displayed confirmation.

Menu labels can change. The issue-specific action is more reliable than instructions based on an old screenshot.

Third-party applications and review requests

Google notes that merchants using a third-party platform may be able to request a review through that application.

This does not mean every WooCommerce Google Merchant Center plugin can submit policy reviews.

Google’s current Merchant API Issue Resolution guidance explains that an application can display Google-provided issue information and actions.

However, Google also states that access to the triggeraction method is restricted to an allowlist.

A third-party application may therefore:

• Display supported account issues
• Display supported product issues
• Show Google-provided explanations
• Show the current action status
• Redirect the merchant to Merchant Center
• Provide an available review link
• Support an in-application action only when the required Google access and implementation are present

Do not assume that OAuth access to product data automatically authorises a plugin to submit account-policy review requests.

How PW Merchant API fits into the review workflow

PW Merchant API is designed to support controlled product communication between WooCommerce and Google Merchant Center through Merchant API.

Depending on the installed version, connected account and available functions, it can help merchants:

• Connect an authorised Google account.
• Select an accessible Merchant Center account.
• Prepare supported WooCommerce product data.
• Submit corrected products.
• Update simple products.
• Update individual variations.
• Preserve controlled offer identities.
• Record supported operation results.
• Display supported product statuses.
• Display supported product issues.
• Help match a Google offer with its WooCommerce source.
• Schedule controlled synchronisation.
• Verify whether an applicable correction reached Google.

This can support the evidence required before requesting a review.

PW Merchant API does not automatically prove that:

• The entire website complies with Google policies.
• Business information is accurate.
• Shipping settings are complete.
• Return information is compliant.
• Checkout works for every customer.
• All competing sources were removed.
• Google processed every corrected product.
• The account is ready for review.
• The review will succeed.

Unless a version explicitly provides a currently authorised Google review action, the merchant should complete the review through the action Google displays in Merchant Center.

PW Merchant API cannot:

• Guarantee product approval.
• Guarantee account reinstatement.
• Guarantee review completion time.
• Bypass a cooldown.
• Create additional review opportunities.
• Override Google’s policy decision.
• conceal an unresolved policy violation.
• Submit false business evidence.
• Determine Google’s private review signals.
• Make an unsupported product eligible.
• Remove an account suspension independently.
• Replace the Merchant Center account administrator.

The plugin can support product correction and status verification. Google retains independent responsibility for account, product and policy evaluation.

What happens after the review is submitted

After submission:

• The issue may display that a review was requested.
• The review action may become unavailable.
• Products may remain disapproved.
• The account may remain suspended.
• Merchant Center may continue displaying the issue.
• Google may crawl the website again.
• Google may process product information again.
• Additional verification may be requested.
• The merchant may receive an email after completion.
• The issue may disappear if the review succeeds.
• A new or more specific issue may appear.
• The review may be unsuccessful.
• A cooldown may begin.

Do not interpret the continued presence of the issue immediately after submission as a failed review.

Record:

• Submission date and time
• Account ID
• Issue title
• Selected review reason
• Confirmation message
• Expected communication method
• Current affected-product count
• Current account status
• Current product status

Take screenshots where appropriate, but do not expose customer, payment or credential information.

How long can a review take?

Google states that review requests typically take approximately three to seven business days, depending on the relevant process and issue.

Google’s general review guidance also warns that completion can take up to seven business days.

These are guidance ranges, not guaranteed deadlines.

The duration can be influenced by:

• Issue type
• Product-level or account-level scope
• Required website crawling
• Catalogue size
• Target countries
• Marketing methods
• Additional verification
• Data-processing state
• Changes made during the review
• Review workload
• Complexity of the account

Do not repeatedly contact support or submit another action while the first review is still active unless Google specifically instructs you to do so.

Avoid unnecessary changes during the review

Material changes made while a review is in progress can make the account harder to evaluate.

Avoid unnecessary:

• Domain migrations
• Theme replacements
• Checkout replacements
• Business-name changes
• Currency changes
• Language changes
• Data-source replacements
• Offer ID changes
• Bulk product deletions
• Plugin changes
• Shipping-policy changes
• Return-policy changes
• URL restructuring

Essential corrections should not be withheld merely because a review is active. However, record every required change and confirm how it affects the submitted evidence.

Do not make random cosmetic edits in an attempt to restart crawling.

Understand the cooldown period

Google can apply a cooldown after unsuccessful account re-reviews.

During a cooldown:

• The review button is disabled.
• Another review cannot be requested.
• The account may remain suspended.
• A preemptive item disapproval can remain active.
• Product visibility may remain restricted.
• Support options may be limited.
• The cooldown end date may be displayed in Merchant Center.

Google states that the cooldown period may increase following subsequent unsuccessful reviews.

The end date can be checked under:

• Products
• Needs attention
• View setup and policy issues

Do not attempt to bypass a cooldown by:

• Creating another Merchant Center account
• Recreating the same products under new offer IDs
• Connecting a different plugin
• Using a different Google account
• Moving the same store to another data source
• Submitting identical information through another method
• Opening duplicate support requests
• Creating a new domain only to avoid the decision

A cooldown should be used to investigate why the previous correction was incomplete.

What to do during a cooldown

Create a fresh audit that does not assume the previous work was complete.

Review:

• The exact issue wording
• All official documentation
• Every account-level requirement
• Every target country
• Every marketing method
• All example products
• The complete affected-product list
• Product variations
• Public landing pages
• Structured data
• Cart and checkout
• Contact information
• Business information
• Shipping information
• Return and refund information
• Privacy and terms pages
• Domain verification
• Business verification
• Data-source history
• Competing sources
• Automatically found products
• Manual Merchant Center edits
• Automatic fixes
• Cached website content
• Mobile behaviour
• Crawler accessibility
• Supplier and ERP imports

Record what was changed after the unsuccessful review.

Another request should be supported by substantive additional corrections, not the passage of time alone.

If the review is successful

A successful review can result in:

• The issue disappearing
• The account warning being removed
• The account suspension being lifted
• Products entering a new processing stage
• Products becoming eligible again
• Some products remaining affected by independent issues

Do not consider the entire catalogue healthy merely because one account issue disappeared.

After success:

1. Open Needs attention.
2. Turn off filters that hide lower-impact issues.
3. Review remaining account issues.
4. Review remaining product issues.
5. Check affected countries.
6. Check Shopping ads.
7. Check free listings.
8. Inspect representative processed products.
9. Confirm product counts.
10. Confirm that scheduled synchronisation does not restore old data.
11. Check the account again after the next full product update.

Approval is not a guarantee of impressions, clicks or sales.

It indicates that the relevant issue no longer prevents eligibility in the evaluated context.

If the review is unsuccessful

An unsuccessful review does not prove that the review system failed.

It can mean:

• The original issue remains.
• Only example products were corrected.
• A website-level condition remains.
• Business information is inconsistent.
• The corrected product data did not reach Google.
• Merchant Center processed the old value.
• A competing source restored the old value.
• A variation remains incorrect.
• Another country remains affected.
• Another marketing method remains affected.
• Checkout does not work for Google’s test.
• A crawler is blocked.
• Policy pages are incomplete or inaccessible.
• Verification is incomplete.
• The merchant selected the wrong response.
• The account has an additional independent issue.

Before contacting support, collect:

• Account ID
• Issue title
• Review submission date
• Review completion date
• Current issue status
• Current cooldown status
• Changes completed before the review
• Additional corrections completed afterwards
• Example offer IDs
• Public product URLs
• Data-source results
• Processed product values
• Relevant screenshots
• Any Google reference number

Do not include passwords, access tokens, payment details or customer information.

When to contact Google support

Consider support when:

• The review is complete but the result is unclear.
• The issue page provides no actionable information.
• Corrected processed data is visible but the same issue persists.
• The cooldown end date has passed but no review action is available.
• Required verification cannot be completed because of a technical error.
• The account displays conflicting status information.
• The account was reviewed under an incorrect domain.
• The merchant cannot identify which issue controls the suspension.
• Google explicitly directs the merchant to support.

Support should not be used to avoid completing the listed corrections.

Provide a precise account and issue history instead of a general statement that the store is compliant.

Common mistakes

Requesting a review immediately after editing WooCommerce

The corrected information may not yet have reached or been processed by Google.

Assuming every product error needs a review

Many data errors are reprocessed after corrected product information is submitted.

Correcting only Google’s example products

Examples may represent a larger account or catalogue pattern.

Editing only the parent variable product

Individual variations can retain separate price, availability, identifier, image or attribute issues.

Checking only one target country

Product and policy status can differ by country.

Checking only Shopping ads

Free listings and other marketing methods can have different issue states.

Using “I fixed the issue” without verifying the processed data

A WooCommerce save or API success message does not prove that Google sees the correction.

Selecting disagreement because the cause is unclear

Disagreement should be based on evidence, not uncertainty.

Making temporary manual Merchant Center edits

Manual values can conceal an unresolved WooCommerce or integration problem.

Ignoring structured data

Google may see outdated or contradictory offer information on the landing page.

Ignoring checkout

A product page can look correct while the purchasing process remains inaccessible.

Leaving obsolete sources active

An old integration can restore incorrect product data after the correction.

Submitting repeated unchanged reviews

Repeated unsuccessful attempts can result in longer cooldown periods.

Creating another account to escape a suspension

This does not correct the original policy or website problem and can create additional account risk.

Frequently asked questions

Where is the Request review button in Merchant Center?

Open the exact issue under Products → Needs attention. Account-level conditions may be listed under View setup and policy issues. The action may also appear in an account banner or Issue Details Page.

Why can I not see a Request review button?

The issue may not require manual review, processing may still be underway, another review may be active, a cooldown may apply or the current user may lack the required permission.

Should I request a review after every WooCommerce correction?

No. Many product-data issues are automatically reprocessed after corrected information is submitted.

What is the difference between “I fixed the issue” and “I disagree”?

Use I fixed the issue when the reported condition existed and has been corrected. Use the disagreement option when evidence shows that the finding is incorrect.

Can I select “I disagree” if Google has not explained the issue clearly?

Lack of clarity alone does not establish that the decision is incorrect. Audit the named policy and collect evidence before choosing the disagreement route.

How soon after updating WooCommerce should I request a review?

Wait until the public page is correct, the synchronisation has succeeded and Merchant Center displays the processed corrected information. The required interval varies.

Does a successful Merchant API request mean the product is ready for review?

Not by itself. It confirms the operation was accepted for processing. Check the processed value and current issue status.

Does a successful review approve every product?

No. It resolves the reviewed issue when successful. Other product, country, marketing-method or account issues can remain.

How long does a Merchant Center review take?

Google states that review requests commonly take approximately three to seven business days. Actual processing can vary.

Can I change my website during the review?

Necessary corrections can be made, but avoid unrelated material changes. Record any essential changes and keep the public evidence consistent.

What happens during a cooldown?

The review action is disabled and another request cannot be submitted. The account or affected products can remain suspended or disapproved.

How long is the cooldown?

Use the end date displayed for the issue in Merchant Center. Google can increase cooldown periods following subsequent unsuccessful reviews.

Can Google support remove the cooldown?

Do not assume that support can remove or shorten it. Follow the current issue instructions and use the period to complete a wider audit.

Can I open another Merchant Center account during the cooldown?

Creating another account does not correct the underlying problem and should not be used to bypass an enforcement decision.

Can a WooCommerce plugin request the review?

Only if the application provides that specific Google-supported function and has the necessary access. Otherwise, complete the action in Merchant Center.

Does normal OAuth product access include review submission permission?

Not automatically. Google restricts the Merchant API triggeraction method used for certain in-application issue actions.

Are Merchant API Product Reviews used to appeal disapprovals?

No. Product Reviews and Merchant Reviews refer to customer ratings and review content, not policy appeals.

Can PW Merchant API guarantee that a review will succeed?

No. It can support product correction, submission and applicable status checks. Google independently evaluates products, websites and accounts.

Why did the old issue return after the review succeeded?

A scheduled import, obsolete source, manual override, automatic fix, cache or supplier integration may have restored the old value.

Should I delete all disapproved products before requesting review?

Not automatically. Correct or remove products according to the actual issue and legitimate catalogue strategy. Deleting products does not resolve an account-wide website or policy problem.

What evidence should I keep?

Keep issue details, affected offer IDs, WooCommerce IDs, public URLs, corrections, submission results, processed values, review dates and Google communications.

Should I send Google a long explanation?

Follow the form presented for the issue. Provide concise, factual and requested information. A long statement cannot replace incomplete corrections.

What should I do if the review fails?

Do not submit the same unchanged account again. Identify what remained unresolved, complete additional corrections and respect any cooldown.

Final pre-review checklist

Before selecting Request review, confirm that:

• The correct Merchant Center account is open.
• The account ID is recorded.
• The exact issue is open.
• The official issue documentation has been read.
• Product-level and account-level scope has been identified.
• Affected countries are recorded.
• Affected marketing methods are recorded.
• Warning and suspension dates are recorded.
• The review action is applicable to the issue.
• The complete affected-product list has been reviewed.
• Example products were not treated as the complete scope.
• Merchant Center offer IDs are recorded.
• WooCommerce product IDs are recorded.
• Variation IDs are recorded.
• Every affected variation has been checked.
• The authoritative data source is identified.
• WooCommerce data is corrected.
• Integration mappings are corrected.
• Global attributes are corrected.
• Product custom fields are corrected.
• The public landing page is correct.
• The submitted URL loads while logged out.
• The correct variation is selected.
• Price matches.
• Currency matches.
• Availability matches.
• Product identity matches.
• Images are accessible.
• Structured data matches.
• Duplicate Product schema has been investigated.
• Cart works.
• Checkout works.
• Required payment methods are accessible.
• Shipping information is accurate.
• Return and refund information is accurate.
• Business information is accurate.
• Contact information is consistent.
• Policy pages are publicly accessible.
• HTTPS works.
• The claimed domain is correct.
• Mobile access works.
• Google crawlers are not blocked.
• Placeholder content has been removed.
• Broken links have been repaired.
• Relevant caches have been cleared.
• Competing sources have been identified.
• Obsolete data sources have been addressed.
• Supplemental sources have been reviewed.
• Automatically found products have been reviewed.
• Manual Merchant Center edits have been reviewed.
• Automatic fixes have been reviewed.
• Corrected products were synchronised.
• The operation result was successful.
• Rejected operations were investigated.
• Merchant Center processed the corrected values.
• The issue was allowed a reasonable reprocessing period.
• A manual review is still required.
• The correct “fixed” or “disagree” route has been chosen.
• Supporting evidence has been recorded.
• No unrelated major site change is planned during the review.
• The review is being submitted only once.
• The account email address is monitored.
• The submission confirmation will be recorded.
• Any cooldown will be respected.

A Google Merchant Center review should be the conclusion of a WooCommerce correction process.

The process begins by identifying the exact issue, its scope, affected countries, marketing methods and products. It continues by matching every Google offer to the correct WooCommerce product or variation and correcting the system that legitimately controls the affected information.

The merchant must then confirm that the public landing page, structured product data, cart, checkout and Merchant Center processed values all reflect the correction.

Only after this evidence is complete should the merchant determine whether the issue requires a manual review.

If the condition has been corrected, the merchant should use the fixed-issue route. If current evidence demonstrates that the finding is incorrect, the disagreement route may be appropriate. Neither option should be used experimentally.

PW Merchant API can support controlled WooCommerce product updates, offer identity, synchronisation evidence and applicable status inspection. It cannot guarantee approval, bypass a cooldown or replace Google’s independent account and policy evaluation.

WooCommerce remains the customer-facing commercial source, PW Merchant API supports applicable product communication, and Google Merchant Center independently determines the resulting product and account eligibility.

A carefully prepared review protects limited review opportunities, gives Google consistent evidence to evaluate and reduces the risk that an old data source, incomplete variation correction or unresolved website problem will reproduce the same issue.