Google Merchant Center suspension recovery for WooCommerce

Google Merchant Center account suspension recovery for WooCommerce stores

A suspended Google Merchant Center account cannot usually be recovered by changing a single WooCommerce product, installing another integration or submitting the same catalogue again.

Account suspension commonly indicates that Google has identified a wider problem involving the website, business information, product data, purchasing experience, account configuration or compliance with an applicable policy.

The recovery process must therefore examine the complete relationship between:

• The Merchant Center account
• The WooCommerce catalogue
• Product landing pages
• Structured product data
• Cart and checkout
• Shipping information
• Return and refund information
• Business identity
• Contact information
• Product data sources
• Target countries
• Marketing methods
• Linked services

A WooCommerce store owner should first identify the exact suspension, preserve the existing account and evidence, correct the authoritative source of every relevant inconsistency and confirm that Google has received the updated information.

Only after this work is complete should the merchant use an available review action.

Google independently evaluates each account. No WooCommerce extension, Merchant API connection, agency or website checklist can guarantee that an account will be reinstated.

The short answer

Recovering a suspended Google Merchant Center account requires a structured account-level audit:

1. Open the correct Merchant Center account.
2. Record the Merchant Center account ID.
3. Open Products.
4. Open Needs attention.
5. Select View setup and policy issues.
6. Record the exact suspension title.
7. Record every affected country and marketing method.
8. Read the current issue-specific Google documentation.
9. Determine whether the suspension originates in Merchant Center or a linked service.
10. Preserve screenshots and current account information.
11. Do not create a replacement account to avoid the suspension.
12. Do not replace the claimed domain without a legitimate business reason.
13. Audit the complete WooCommerce catalogue.
14. Audit all submitted variations.
15. Audit product landing pages.
16. Audit structured product data.
17. Test cart and checkout while logged out.
18. Verify business and contact information.
19. Review shipping settings and delivery statements.
20. Review return and refund information.
21. Check privacy and terms pages.
22. Identify every active product data source.
23. Find obsolete, duplicate and competing sources.
24. Correct the system that legitimately controls each value.
25. Clear relevant caches.
26. Submit corrected product information.
27. Confirm that the operation succeeded.
28. Confirm that Merchant Center processed the corrected values.
29. Recheck all affected countries and marketing methods.
30. Request a review only when the complete account is ready.
31. Respect any active cooldown.
32. Monitor the account after reinstatement to ensure that old data does not recreate the problem.

This is an account recovery process, not merely a product synchronisation task.

Start by identifying what is actually suspended

The first objective is to determine the scope of the enforcement action.

Merchants sometimes describe several different conditions as a “Merchant Center suspension,” including:

• An account warning
• An account suspension
• A preemptive item disapproval
• A product-level disapproval
• A suspended Google Ads account linked to Merchant Center
• A business verification restriction
• An incomplete onboarding review
• A website verification or claiming problem
• A marketing-method restriction
• A country-specific account issue

These conditions do not have identical causes or recovery procedures.

Open the exact issue inside Merchant Center and record:

• Account ID
• Account name
• Claimed website
• Issue title
• Issue code where available
• Issue severity
• Warning or suspension status
• Affected country
• Affected marketing method
• Warning start date
• Warning deadline
• Suspension date
• Review status
• Cooldown status
• Documentation link
• Example products
• Related verification requirements

Google’s current Merchant Center issue guidance explains that warnings, product disapprovals and account suspensions can have different effects and review processes.

Do not begin making broad changes before recording the issue as Google presents it.

If the wording changes later, the original evidence will help determine what was corrected and whether a new issue has appeared.

Distinguish a Merchant Center suspension from a linked account suspension

A Merchant Center account can display a linked account suspension when a connected Google Ads account is suspended.

Google’s linked account suspension information states that this status refers to a suspended Google Ads account connected to Merchant Center.

In this situation, changing WooCommerce product titles or resubmitting products will not correct the suspended Google Ads account.

Record:

• Which account is suspended
• Which account displays the notification
• The Google Ads customer ID
• The Merchant Center account ID
• The linked-account relationship
• The policy named in each platform
• Whether Shopping ads, free listings or both are affected

Do not assume that every issue displayed in Merchant Center originates from product data.

A suspension is not a product sync failure

A successful WooCommerce product submission does not remove an account suspension.

Similarly, a product synchronisation failure does not by itself prove that the account has been suspended.

These are different technical states.

A Merchant API operation can succeed while:

• The account remains suspended
• The product remains disapproved
• A country remains ineligible
• Shopping ads remain unavailable
• Free listings remain unavailable
• A policy review remains incomplete
• Business verification remains outstanding

An API operation can also fail because of:

• Invalid credentials
• Insufficient permission
• Incorrect account selection
• Invalid product data
• Incorrect resource names
• Expired authorisation
• A rejected attribute
• A temporary service condition

Record API and policy results separately.

The Merchant API can support product communication and account-issue visibility, but it does not override Google’s account evaluation. Google’s Merchant API account issues documentation explains how supported applications can retrieve account-level issues, their severity and affected destinations.

Preserve the account instead of trying to escape it

Do not immediately:

• Create another Merchant Center account
• Move the same store to a different Google account
• Register a second version of the business
• Replace the store domain
• Recreate every product under new offer IDs
• Connect another plugin merely to create a new source
• Delete all products
• Remove the existing integration
• Submit the same catalogue through another method
• Open several identical support requests

These actions do not correct the underlying website, product or business problem.

They can also make it harder to identify:

• Which account owns the claimed domain
• Which source controls each product
• Which offer IDs belong to the original catalogue
• Which account received the enforcement action
• Which corrections existed during the review
• Whether duplicate products are being processed

Preserve the original account unless Google specifically instructs the legitimate business to use a different account structure.

A domain or account migration can be appropriate for a real business change, but it should not be used as a shortcut around an unresolved enforcement decision.

Build an evidence record before making changes

Create a suspension record containing:

• Merchant Center account ID
• Google Ads account ID where relevant
• Claimed domain
• Business name
• Suspension title
• Suspension date
• Warning history
• Review history
• Cooldown dates
• Target countries
• Marketing methods
• Product count
• Disapproved-product count
• Example offer IDs
• WooCommerce product IDs
• WooCommerce variation IDs
• Product data-source names
• Source update times
• Relevant emails
• Current public URLs
• Screenshots of the issue
• Previous correction attempts

Do not include passwords, client secrets, access tokens, payment details or customer information in this record.

Evidence prevents the recovery process from becoming a series of unrecorded changes.

It also helps distinguish between:

• The original suspension
• A new issue discovered during recovery
• A correction that did not reach Google
• A correction that reached Google but was incomplete
• An old source that restored incorrect information

Classify the likely source of the suspension

Account suspensions can involve several overlapping areas.

Business and identity issues

These can include inconsistent or unverifiable information about:

• Business name
• Legal identity
• Physical address
• Telephone number
• Email address
• Company registration
• Ownership
• Customer support
• Payment recipient
• Domain ownership

Website issues

These can include:

• Broken pages
• Inaccessible product pages
• Missing contact information
• Incomplete policy pages
• Unclear purchase conditions
• Non-functional checkout
• Unsupported redirects
• Placeholder content
• Mixed business identities
• Unsecured collection of customer information
• Products that cannot be purchased directly

Product-data issues

These can include:

• Price mismatches
• Currency mismatches
• Availability mismatches
• Incorrect identifiers
• Unsupported products
• Misleading titles
• Missing required attributes
• Incorrect condition
• Variation inconsistencies
• Inaccessible images
• Duplicate offer identities

Account and programme configuration issues

These can include:

• Incorrect target countries
• Incomplete shipping settings
• Inconsistent return settings
• Unverified website
• Unclaimed website
• Outstanding business verification
• User permission problems
• Linked account enforcement

Policy issues

These can include:

• Misrepresentation
• Prohibited content
• Counterfeit products
• Unsupported Shopping content
• Editorial and professional requirement violations
• Abusive or misleading business practices

One suspension can involve more than one category.

Correcting the most visible issue does not prove that every account-level concern has been resolved.

Read the exact policy rather than relying on generic suspension lists

Generic checklists can help organise an audit, but the issue-specific Google documentation must control the final correction.

Google’s Shopping ads policies cover several independent policy areas. A requirement applicable to counterfeit goods is not interchangeable with a requirement concerning website quality, misrepresentation or unsupported content.

For the exact issue:

1. Open the Merchant Center issue.
2. Follow its official documentation link.
3. Record the named policy.
4. Identify what the policy applies to.
5. Determine whether it concerns the account, website, products or a linked service.
6. Review every example provided by Google.
7. Download the complete affected-product list when available.
8. Check the affected countries.
9. Check the affected marketing methods.
10. Separate confirmed facts from assumptions.

Do not publish policy wording invented by an agency, plugin or forum as if it were Google’s explanation.

Community discussions can describe other merchants’ experiences, but they do not replace the policy attached to the account.

Audit the complete WooCommerce catalogue

An account-level recovery should not stop with the example products shown in Merchant Center.

Examples can indicate a catalogue-wide pattern.

For every submitted simple product, check:

• WooCommerce product ID
• Offer ID
• SKU
• Product status
• Catalogue visibility
• Product type
• Title
• Description
• Regular price
• Sale price
• Sale dates
• Currency
• Tax configuration
• Stock status
• Quantity
• Backorder status
• Condition
• Brand
• GTIN
• MPN
• Product category
• Google product category
• Main image
• Additional images
• Landing-page URL
• Shipping-related information
• Return-policy label where used
• Target country
• Marketing method

Products that are private, drafts, unavailable, placeholders or impossible to purchase should not accidentally remain inside an active submission process.

Audit every WooCommerce variation

A variable WooCommerce product can create multiple Merchant Center offers.

Each submitted variation may have its own:

• Variation ID
• SKU
• Offer ID
• Price
• Sale price
• Stock status
• GTIN
• MPN
• Image
• Colour
• Size
• Material
• Pattern
• Age group
• Gender
• Item group ID
• Landing-page state

Do not assume that correcting the parent product changes every submitted variation.

Test each affected variation independently.

Confirm that the submitted variation URL:

• Opens the correct product
• Selects the intended attributes
• Displays the correct image
• Displays the submitted price
• Displays the submitted availability
• Can be added to the cart
• Remains identifiable during checkout

An account-wide pattern can remain when only the parent product or one example variation has been corrected.

Audit the public store as a new customer

The WordPress administration panel is not the customer-facing evidence evaluated by Google.

Open the public store:

• While logged out
• In a private browser window
• Without old cookies
• Without an administrator session
• On desktop
• On mobile
• In each relevant language
• In each relevant currency context
• From the exact submitted product URLs

Confirm that:

• The website loads through HTTPS.
• The claimed domain remains in the address bar.
• Product pages return successful responses.
• No maintenance page appears.
• No login is required to view essential product information.
• The correct product is displayed.
• The correct variation can be selected.
• Price and currency are visible.
• Availability is visible.
• Images load.
• Product information is understandable.
• Add to cart works.
• Cart totals are correct.
• Checkout can be completed.
• Payment options are available.
• Shipping costs are disclosed at the appropriate stage.
• Return information is accessible.
• Contact information is accessible.
• No unexpected redirect interrupts the purchase.

Google’s current Merchant Center account guidelines require products to be available for direct purchase, customer information to be collected securely and the website to provide a functional purchasing experience.

Verify the claimed online store

The website connected to Merchant Center should belong to the business and satisfy the applicable online-store requirements.

Check:

• The complete claimed URL
• HTTP and HTTPS versions
• www and non-www behaviour
• Canonical redirects
• WordPress Address
• Site Address
• Product URLs
• Checkout domain
• Payment return URLs
• Language-directory URLs
• Mobile URLs
• Search Console ownership
• Merchant Center verification
• Merchant Center claiming status

Google’s online store domain requirements include direct purchasing, displayed fixed prices, an available conventional payment method and clear purchasing conditions.

Do not change the domain during recovery merely to make the suspension message disappear.

If a legitimate domain migration has already occurred, make sure that every public page, product source, canonical URL, callback, policy link and business reference consistently uses the intended domain.

Verify business and contact information

Business information should be authentic, current and consistent.

Compare:

• Merchant Center business name
• Website business name
• Legal business name
• Contact-page information
• Footer information
• Invoice information
• Checkout information
• Payment-recipient information
• Public business records where applicable
• Support email address
• Telephone number
• Physical address
• Operating hours where published

Google’s guidance for missing contact information emphasises the need for accessible and consistent contact details.

Avoid:

• Invented addresses
• Virtual locations presented misleadingly
• Unmonitored support email addresses
• Telephone numbers that do not belong to the business
• Different business names across important pages
• Copied policy pages containing another company’s identity
• Unsupported certification or partnership claims
• False customer reviews
• False stock or delivery statements

Adding more trust icons cannot compensate for inconsistent or unverifiable business information.

Audit return and refund information

The return policy must describe the store’s real operating process.

Check whether it clearly explains:

• Whether returns are accepted
• The return period
• The condition required for returned products
• How a customer starts a return
• The return address or process
• Who pays return shipping
• Whether restocking fees apply
• Which products are excluded
• When refunds are issued
• How refunds are issued
• What happens with damaged or incorrect items
• Country-specific differences
• Product-specific exceptions

Even a store that does not accept returns should publish a clear policy explaining that position where legally and commercially applicable.

Compare the website policy with:

• Merchant Center return settings
• Product-level return-policy labels
• Footer links
• Checkout information
• Customer support instructions
• Promotional banners
• Product descriptions

Google’s return-policy requirements state that return information should be publicly accessible and consistent between Merchant Center and the website.

Do not create a generous policy solely for the review if the business cannot honour it.

Audit shipping and delivery information

Shipping information should match the customer’s actual purchasing experience.

Check:

• Shipping countries
• Service areas
• Shipping costs
• Free-shipping thresholds
• Handling time
• Transit time
• Delivery estimates
• Carrier restrictions
• Minimum order values
• Product-specific exceptions
• Oversized-product charges
• Remote-area charges
• Digital-product delivery
• Local pickup
• Currency
• Tax presentation

Compare:

• Merchant Center shipping settings
• Product-level shipping attributes
• WooCommerce shipping zones
• WooCommerce shipping classes
• Product pages
• Cart
• Checkout
• Shipping-policy page
• Promotional banners

A “free shipping” banner should not conflict with a charge applied at checkout.

A delivery promise should not be shorter than the store can reasonably fulfil.

Test the complete WooCommerce checkout

A product page can appear correct while checkout remains unusable.

Google’s checkout requirements should be reviewed against the live store.

Test:

1. A simple product
2. A variable product
3. A sale product
4. A full-price product
5. A low-stock product
6. A product with shipping charges
7. A product qualifying for free shipping
8. A mobile purchase
9. A guest purchase
10. Each target country where practical

Confirm that:

• Add to cart works.
• Required variation options work.
• The correct product reaches the cart.
• Quantity changes work.
• Price remains consistent.
• Currency remains consistent.
• Taxes are understandable.
• Shipping methods appear.
• The customer can provide an address.
• A conventional payment method is available.
• Required terms can be opened.
• Checkout does not redirect unexpectedly.
• No fatal WordPress error occurs.
• No unsupported country is advertised.
• The order can reach the final confirmation stage.

Do not place a real order unless it is necessary and authorised. A controlled test method can be used where available.

Inspect structured product data

A WooCommerce theme, SEO plugin, product plugin and Merchant integration can each generate structured data.

This can produce duplicate or contradictory Product and Offer objects.

Inspect:

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

Look for:

• Multiple Product objects describing different prices
• Parent-product prices applied to variations
• Old cached sale prices
• Incorrect currency
• Outdated availability
• Missing variation identity
• Schema from an inactive plugin
• Theme and plugin schema conflicts
• Different canonical and submitted URLs

Google’s Merchant Center structured-data guidance identifies price, currency, availability and condition as important Offer properties for supported automatic updates.

Structured data should reflect the public offer. It should not be altered merely to display a value that differs from what the customer sees.

Identify every product data source

A suspended Merchant Center account may contain products from several sources:

• Merchant API
• A previous Content API integration
• XML files
• Scheduled file retrieval
• Manually uploaded files
• Google Sheets
• Ecommerce-platform connections
• Automatically found products
• Manual product entry
• Supplemental data sources
• Manual Merchant Center edits

Record for every source:

• Source name
• Source type
• Last update
• Number of products
• Language
• Feed label
• Target countries
• Primary or supplemental role
• Scheduled update status
• Offer ID pattern
• Current errors
• Whether the source is still required

A corrected WooCommerce product can be overwritten by an older scheduled source.

Do not delete an unfamiliar source before determining what it controls.

If two sources contain the same offer identity, establish which source should remain authoritative and how Merchant Center combines or prioritises the submitted information.

Correct the authoritative source

A durable correction must be made in the system that will continue supplying the value.

Examples include:

• WooCommerce product fields
• WooCommerce variation fields
• Global product attributes
• Product custom fields
• Shipping zones
• Shipping classes
• Tax settings
• Theme templates
• Structured-data output
• Merchant integration mappings
• Merchant Center account settings
• Return settings
• Business information
• The legitimate primary data source

A manual Merchant Center edit may temporarily change a displayed value while the WooCommerce source remains wrong.

The next synchronisation can restore the original problem.

For every correction, record:

• Incorrect value
• Correct value
• Authoritative source
• Date changed
• Person responsible
• Public validation result
• Submission result
• Merchant Center processed result

Avoid changing unrelated fields. Broad, unrecorded edits make it difficult to determine which correction mattered.

Clear caches and verify the public result

WooCommerce updates can be hidden by:

• Page cache
• Object cache
• Server cache
• CDN cache
• Browser cache
• Database transients
• Structured-data cache
• Image optimisation cache
• Currency cache
• Translation cache
• External product-import cache

After a correction:

1. Clear only the relevant caches.
2. Open the product while logged out.
3. Test the submitted URL.
4. Inspect page source or rendered structured data.
5. Confirm the variation.
6. Test cart and checkout.
7. Test mobile behaviour.
8. Confirm that old content is no longer publicly available.

Do not assume that pressing Update in WordPress immediately changes what Google can crawl.

Submit corrected information and verify processing

After the WooCommerce and website corrections are publicly available:

• Run the supported product update.
• Record the submission time.
• Record the Merchant Center account.
• Record the offer IDs.
• Review the operation result.
• Investigate rejected operations.
• Allow Merchant Center to process the new information.
• Inspect the processed product.
• Compare the processed value with WooCommerce.
• Review item-level issues.
• Review country status.
• Review marketing-method status.

A successful API response means the operation was accepted for processing. It does not mean that the suspension has been removed.

Do not request an account review while Merchant Center still shows incorrect processed product information.

Prepare for review without repeating the same failed attempt

Once the complete account has been corrected, determine whether Merchant Center provides a review action.

Google’s review request guidance distinguishes between reporting that an issue has been fixed and disagreeing with a decision.

Use the option that accurately represents the situation.

Before submitting:

• Confirm that the whole issue scope was corrected.
• Confirm that corrected product data was processed.
• Confirm that the public website is stable.
• Confirm that business information is authentic.
• Confirm that checkout works.
• Confirm that all target countries were checked.
• Confirm that every relevant marketing method was checked.
• Confirm that no obsolete source can restore old data.
• Record the evidence.

The separate PW Feed guide covering the Google Merchant Center review request process explains review selection, submission status and cooldown handling in greater detail.

The review request should be the final step of the recovery work, not an experiment used to discover whether the account is ready.

Respect warning and cooldown periods

Google’s current warning and suspension guidance explains that review availability can be limited and that an unsuccessful process can lead to a cooldown in which the review control is disabled.

During a cooldown:

• Do not attempt to bypass the restriction.
• Do not recreate the account.
• Do not resubmit unchanged information.
• Do not replace every offer ID.
• Do not make random website changes.
• Do not assume that time alone corrects the issue.

Use the period to:

• Repeat the account audit
• Recheck business information
• Recheck the complete catalogue
• Inspect all variations
• Test checkout again
• Review country-specific conditions
• Review linked accounts
• Find competing sources
• Examine changes made after the previous review
• Collect stronger evidence

Another request should follow substantive corrections, not merely the end of the cooldown.

What PW Merchant API can support

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 information.
• Submit supported product updates.
• Update simple products.
• Update individual variations.
• Preserve controlled offer identities.
• Record supported operation results.
• Display applicable product results.
• Display supported Merchant issues.
• Schedule controlled product synchronisation.
• Compare WooCommerce products with processed Merchant information.

These functions can help verify whether a catalogue correction reached Google.

PW Merchant API cannot independently:

• Remove an account suspension.
• Guarantee product approval.
• Guarantee account reinstatement.
• Override Google policies.
• Bypass a cooldown.
• Correct false business information.
• Repair an inaccessible checkout.
• Make prohibited products eligible.
• Verify an organisation’s legal identity.
• Decide whether the website complies with every policy.
• Replace the store owner’s responsibilities.
• Reveal Google’s private evaluation signals.
• Guarantee impressions, clicks or sales.

A WooCommerce Google Merchant Center plugin can support product-data communication. It cannot serve as proof that the whole business, website or catalogue satisfies Google’s requirements.

Common suspension recovery mistakes

Installing another product plugin

Changing the integration does not correct website, business or policy problems. It may create another competing source.

Creating another Merchant Center account

A new account does not correct the original cause and can complicate domain ownership, account structure and product-source management.

Deleting all products

Removing products may be necessary when they are genuinely unsupported, but deleting the catalogue does not correct an account-wide website or business problem.

Correcting only the example products

Examples may reveal a broader catalogue pattern. Audit every affected offer and variation.

Changing only the homepage

Google can evaluate product pages, policies, cart, checkout, business information and other customer-facing content.

Adding generic policy templates

A copied policy containing inaccurate conditions or another company’s information can create additional inconsistency.

Adding unsupported trust claims

Badges, awards, reviews, certifications or partnership claims should not be published unless they are authentic and verifiable.

Requesting review immediately after a WooCommerce update

The correction may not yet be public, submitted or processed.

Ignoring structured data

Google may still detect an old price, currency or availability value in Product schema.

Ignoring duplicate sources

An obsolete import can restore incorrect information after the merchant completes the correction.

Selecting disagreement because the reason is unclear

Uncertainty is not evidence that the decision is incorrect.

Submitting repeated unchanged reviews

This can consume available review opportunities and lead to a cooldown.

Frequently asked questions

What does a Merchant Center account suspension mean?

It means that the account or affected programmes have been restricted because Google identified a problem connected to an applicable policy, requirement, website, account setting or product-data condition.

Is an account suspension the same as a product disapproval?

No. A product disapproval can affect an individual offer or group of offers. An account suspension can restrict all or many products in the affected country or marketing method.

Can I recover the account by updating one WooCommerce product?

Usually not when the issue is account-wide. Example products can indicate a larger catalogue, website or business pattern.

Should I delete the Merchant Center account and start again?

No. Starting again does not correct the underlying cause and can make account, domain and source relationships more difficult to verify.

Should I change my domain?

Not merely to escape a suspension. A domain change should reflect a legitimate business requirement and must be implemented consistently across the website, Merchant Center and all product sources.

Can changing my WooCommerce Google Shopping plugin remove the suspension?

No. A different plugin may change how product information is submitted, but it cannot remove an account-level policy decision.

Does a successful Merchant API request mean the account is reinstated?

No. It confirms only that the operation was accepted for processing. Account and product eligibility remain subject to Google’s evaluation.

Why does Merchant Center still display the old value?

The product may still be processing, an update may have failed, a cache may expose old information or another data source may control the value.

Can PW Merchant API request account reinstatement?

Do not assume that ordinary OAuth product access includes policy-review submission. Unless a version explicitly provides an authorised Google action, use the review option displayed in Merchant Center.

Can PW Merchant API guarantee approval?

No. Google independently evaluates the account, business, website and products.

Should I remove every disapproved product?

Remove products that are genuinely unsupported or that the business will no longer sell. Correct legitimate products when the problem can be resolved. Product deletion does not automatically repair an account-wide issue.

What if the suspension concerns misrepresentation?

Read the exact issue and Google’s current misrepresentation policy. Audit business identity, commercial claims, product information, policies, checkout and the complete customer experience.

What if Google provides only a few example products?

Treat them as evidence of a possible pattern. Download or inspect the complete affected-product list and audit similar products throughout the catalogue.

Why did the suspension return after reinstatement?

An old product source, scheduled import, manual override, cache, supplier integration or unresolved catalogue pattern may have restored the original condition.

Can support tell me exactly what to change?

Support availability and the amount of detail provided can vary. Prepare the account ID, exact issue, review history, public URLs, offer IDs, corrections and processed results before contacting support.

How long does recovery take?

There is no guaranteed total recovery time. Product processing, website crawling, verification, review and cooldown are separate processes.

Should I pause WooCommerce synchronisation?

Pause only when continued synchronisation would restore known incorrect information or interfere with a controlled correction. Record the decision and avoid leaving legitimate product information permanently outdated.

Can I continue selling products on my website?

A Merchant Center suspension does not necessarily disable WooCommerce. However, the business must still comply with applicable laws, payment-provider terms and platform requirements.

What should I monitor after reinstatement?

Monitor account issues, product status, countries, marketing methods, data-source updates, WooCommerce changes, structured data, checkout and scheduled imports.

Final account recovery checklist

Before requesting reinstatement, confirm that:

• The correct Merchant Center account was opened.
• The account ID was recorded.
• The exact suspension was recorded.
• The affected countries were identified.
• The affected marketing methods were identified.
• Merchant Center and linked account suspensions were separated.
• The official issue documentation was read.
• Warning dates were recorded.
• Review dates were recorded.
• Cooldown dates were recorded.
• Evidence was preserved.
• A replacement account was not created to avoid the issue.
• The claimed domain was verified.
• The claimed domain remained consistent.
• Business information was authentic.
• Business information was consistent.
• Contact information was accessible.
• Contact information was monitored.
• The privacy policy was accessible.
• Terms of use were accessible.
• Return information was accurate.
• Refund information was accurate.
• Shipping information was accurate.
• Delivery promises were realistic.
• Payment information was clear.
• The complete WooCommerce catalogue was audited.
• Every affected simple product was audited.
• Every affected variation was audited.
• Product identities matched.
• Offer IDs were preserved where appropriate.
• SKUs were checked.
• GTINs were checked.
• MPNs were checked.
• Brands were checked.
• Prices matched.
• Currencies matched.
• Sale prices matched.
• Availability matched.
• Product conditions matched.
• Images were accessible.
• Product titles were accurate.
• Product descriptions were accurate.
• Unsupported claims were removed.
• Unsupported products were removed where applicable.
• Public product URLs worked.
• The website worked while logged out.
• Mobile pages worked.
• HTTPS worked.
• Redirects were correct.
• Cart worked.
• Checkout worked.
• A conventional payment method was available.
• Shipping costs were disclosed.
• Required variation selections worked.
• Structured data was inspected.
• Duplicate Product schema was investigated.
• Structured-data prices matched.
• Structured-data currencies matched.
• Structured-data availability matched.
• All product data sources were recorded.
• Primary sources were identified.
• Supplemental sources were identified.
• Automatically found products were reviewed.
• Manual Merchant Center edits were reviewed.
• Obsolete sources were addressed.
• Competing sources were addressed.
• WordPress caches were cleared.
• Server caches were cleared.
• CDN caches were cleared.
• Corrected public pages were retested.
• Corrections were made in authoritative sources.
• Corrected products were submitted.
• Submission results were recorded.
• Rejected operations were investigated.
• Merchant Center processed the new values.
• All affected countries were rechecked.
• Shopping ads were rechecked.
• Free listings were rechecked.
• Account-level issues were rechecked.
• Product-level issues were rechecked.
• No old source could restore the incorrect data.
• The account was stable before review.
• The correct review option was selected.
• The review was not used as a diagnostic experiment.
• Any cooldown was respected.
• Post-reinstatement monitoring was planned.

A suspended Google Merchant Center account should be treated as a complete commercial-data and customer-experience problem until the evidence shows otherwise.

The recovery begins by identifying the exact account, issue, country, marketing method and policy. It continues by preserving the existing account structure, auditing WooCommerce products and variations, validating the customer-facing website and confirming that business, shipping, return and checkout information is authentic and consistent.

Every product correction must be made in the source that will continue controlling the value. The corrected information must then become publicly visible, be submitted successfully and appear in Merchant Center’s processed data.

Only after this chain is complete should the merchant use an available review action.

PW Merchant API can support controlled product communication, offer identity, synchronisation results and applicable Merchant issue visibility. It cannot remove an account suspension, bypass a cooldown or guarantee Google approval.

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

A careful recovery process protects the existing account, reduces contradictory evidence and helps prevent obsolete data sources, incomplete variation corrections or unresolved website problems from recreating the same suspension.