Fix Google Merchant Center “Needs attention” issues in WooCommerce

How to fix Google Merchant Center “Needs attention” issues in WooCommerce

When Google Merchant Center places WooCommerce products in the “Needs attention” section, the message does not identify a single type of problem.

The affected product may have a missing attribute, an invalid identifier, an inaccessible image, a price or availability mismatch, an unsupported destination, an account-level policy restriction or a landing page that Google cannot process correctly.

A product can also be approved for one country or marketing method while remaining pending, limited or disapproved elsewhere.

The correct response is therefore not to edit products randomly until the warning disappears.

A controlled correction process should identify:

• The exact Merchant Center account
• The exact issue name
• Whether it is an account-level or product-level issue
• The affected marketing method
• The affected country
• The number of affected products
• Representative product examples
• The Merchant Center product ID
• The WooCommerce product or variation
• The authoritative product data source
• The submitted attribute value
• The value displayed on the landing page
• The required correction
• The result of the next product update
• The product’s processed status after Google evaluates it

In the current Merchant Center interface, the former Diagnostics area is represented primarily by the Products → Needs attention section. Some older Google documentation, account messages and third-party tutorials may still refer to Diagnostics.

The name has changed, but the essential purpose remains the same: identifying account and product conditions that can affect eligibility, visibility or performance.

The short answer

To investigate and fix Merchant Center “Needs attention” issues for WooCommerce:

1. Open the correct Merchant Center account.
2. Go to Products.
3. Select Needs attention.
4. Review the high-impact issue cards.
5. Turn off the Prioritized fixes filter when you need to see every recorded issue.
6. Separate account-level issues from product-level issues.
7. Open the relevant Issue Details Page.
8. Record the exact issue title and affected marketing methods.
9. Record the affected countries.
10. View or download the complete affected-product list.
11. Open several representative products.
12. Record each offer ID and data source.
13. Match each Merchant Center offer to the correct WooCommerce product or variation.
14. Compare the submitted value with the public landing-page value.
15. Determine which system controls the incorrect value.
16. Correct the value in the authoritative source.
17. Avoid using a temporary Merchant Center edit when WooCommerce or an integration will overwrite it.
18. Update the affected products through the active data source.
19. Record whether the update operation succeeded.
20. Allow Merchant Center to process the update.
21. Check the product’s status separately for each country and marketing method.
22. Confirm that the issue has been removed from every affected offer.
23. Investigate competing data sources if the old value returns.
24. Request a review only when the particular issue requires or permits one.

A successful WooCommerce save or Merchant API response does not prove that Google has approved the resulting product.

It only confirms that a particular local or API operation was completed. Merchant Center processes the submitted information independently and may identify additional product, website, account or policy issues.

What the “Needs attention” section means

Google’s current Needs attention documentation explains that the section contains details about problems affecting products in the Merchant Center account.

The page can contain:

• High-impact account problems
• High-impact product problems
• Product data errors
• Policy-related conditions
• Missing or invalid attributes
• Products with limited performance
• Products disapproved from one or more marketing methods
• Suggested attribute improvements
• Automatic-fix options
• Example products
• Estimated business impact
• Status history

“Needs attention” should not automatically be interpreted as “the complete Merchant Center account is suspended.”

Some issues affect one attribute on one product. Others affect a group of products, a country, a marketing method or the whole account.

The scope must be identified before any correction is attempted.

Diagnostics and Needs attention are related names

Classic Merchant Center used the term Diagnostics more prominently.

Merchant Center Next places the corresponding product issue workflow under the Needs attention tab within Products. Google describes the change in its Merchant Center Next transition guidance.

Merchants may still encounter the word “Diagnostics” in:

• Older Merchant Center instructions
• Google emails
• Historical screenshots
• API migration documentation
• Support discussions
• Account review instructions
• Older integration interfaces

When an instruction says to open Diagnostics, first look for:

• Products
• Needs attention
• View setup and policy issues
• Issue cards
• Product details
• The Issue Details Page

Do not install a different plugin or create another data source merely because the current interface no longer uses an older menu name.

Start with the high-impact issue cards

Merchant Center displays three summary cards near the top of the Needs attention page for issues considered to have the greatest effect on the account.

According to Google, these cards can contain both account-level and product-level issues.

Depending on the issue, the available actions may include:

• Fix: Start addressing an issue that affects the account.
• View products: Open a filtered list of affected products.
• View all: Display the complete issue list.
• Learn more: Open issue-specific Google documentation.
• Apply automatic fix: Apply an available rule or correction.
• Review suggestions: Examine suggested attribute values.

The high-impact cards are useful starting points, but they should not be treated as the complete issue inventory.

A merchant should also inspect the full product table and disable filters that hide lower-impact issues.

Understand the Prioritized fixes filter

Merchant Center may provide a Prioritized fixes option.

When enabled, it focuses the Needs attention page on issues that Google estimates may have a medium or high impact on product performance and potential clicks.

This can help a large WooCommerce catalogue concentrate on important problems first.

However, Google states that issues estimated to have little or no impact may be hidden while the filter is active.

Turn off Prioritized fixes when:

• Performing a complete catalogue audit
• Confirming that every issue was resolved
• Investigating a product that appears missing from the visible issue list
• Comparing Merchant Center with API results
• Preparing an account for a formal review
• Checking low-volume products
• Auditing a newly imported catalogue
• Reviewing products for a new country
• Reviewing a new marketing method
• Investigating a persistent source discrepancy

Prioritisation is a working filter, not evidence that hidden issues no longer exist.

Account-level and product-level issues are different

This distinction determines the scope of the correction.

Account-level issues

An account-level issue can affect many or all products associated with a Merchant Center account.

Examples may relate to:

• Business information
• Website verification or claiming
• Checkout functionality
• Return or refund information
• Shipping configuration
• Policy compliance
• Account setup
• Linked services
• Programme eligibility
• Website quality
• Data quality patterns affecting the account

Correcting one WooCommerce product title will not resolve an account-wide website or policy problem.

For account-level issues, record:

• The issue title
• Severity
• Affected marketing methods
• Affected countries or regions
• Warning or review deadline
• Whether all products are affected
• The documentation link
• The account action Google requests
• Whether a review is available
• Whether a cooldown applies

Merchant API provides a dedicated account-issues resource. Google’s account issue documentation explains that account issues can include a title, severity, detailed message, affected destinations and an official documentation link.

Product-level issues

A product-level issue is associated with an individual offer or a defined group of offers.

Examples include:

• Missing image
• Invalid image
• Missing price
• Invalid price
• Price mismatch
• Missing availability
• Availability mismatch
• Missing title
• Invalid description
• Missing brand
• Missing GTIN
• Invalid GTIN
• Missing MPN
• Invalid condition
• Invalid Google product category
• Missing shipping information
• Unsupported currency
• Inconsistent language
• Incorrect variant grouping
• Missing variation attributes
• Landing-page access problems

A product-level issue may still affect thousands of products when they share the same missing field, mapping rule, theme behaviour or data source.

Do not assume that a large affected-product count automatically means the issue is account-level.

Data-source issues form another diagnostic layer

Some problems originate before Google can fully process individual products.

A data source may fail because of:

• Invalid formatting
• Authentication failure
• Expired credentials
• An inaccessible scheduled file
• An incorrect delimiter
• Unsupported encoding
• Missing columns
• Invalid field names
• A failed API operation
• Product quota restrictions
• A scheduled import problem
• An integration connection problem
• Rejected product operations
• A source that no longer updates
• An obsolete source that continues submitting old values

Google provides separate data-source troubleshooting guidance.

A data-source failure and a processed-product issue are not the same event.

For example:

• The source can fail before any product is updated.
• The source can upload successfully while individual products remain invalid.
• An API operation can succeed while Google later disapproves the processed offer.
• One source can succeed while another active source continues supplying conflicting information.

Check both the source result and the processed product status.

Read the status in its complete context

A product does not have one universal status independent of country and use.

Merchant API product status information includes destination or reporting-context status and the countries where the product is approved, pending or disapproved.

This means one offer can be:

• Approved for free listings in one country
• Disapproved for Shopping ads in that country
• Pending in a second country
• Limited in another reporting context
• Affected by an attribute warning that does not directly disapprove it

When examining a product, record:

• Reporting context or marketing method
• Country
• Approval state
• Item-level issues
• Issue severity
• Affected attribute
• Required merchant action
• Applicable documentation

Do not report a product simply as “approved” or “rejected” without recording the context in which that status applies.

Approved does not guarantee impressions

An approved product is eligible for the applicable context, but eligibility does not guarantee that the product will receive impressions, clicks or sales.

Visibility can also depend on:

• Search relevance
• Product data quality
• Customer demand
• Competition
• Campaign settings
• Bid strategy
• Budget
• Country targeting
• Language targeting
• Product exclusions
• Account configuration
• Google’s independent ranking systems

The Needs attention section identifies problems and opportunities. It is not a performance guarantee.

Pending requires observation, not repeated resubmission

A pending product is still being processed or evaluated for the relevant context.

Repeatedly editing and resubmitting the same unchanged product can:

• Restart parts of the processing cycle
• Make the diagnostic timeline harder to interpret
• Create unnecessary API operations
• Hide whether the original correction worked
• Produce multiple timestamps without improving the underlying data

Record the last meaningful correction and allow an appropriate processing period before making another change.

If the status remains pending unusually long, inspect:

• Account setup
• Website accessibility
• Data-source results
• Product expiration
• Country configuration
• Marketing-method eligibility
• Any new issue displayed by Google

Limited is not the same as disapproved

A limited product may remain eligible but have restricted performance because of a data quality or eligibility condition.

Merchant API item-level severity can distinguish between conditions such as:

• A warning with no direct serving impact
• A demotion that can limit performance
• A disapproval that prevents serving in the applicable context

The exact issue should determine the response.

Do not delete and recreate an otherwise valid product merely because its status is limited.

First identify:

• Which attribute is involved
• Whether the issue applies to all countries
• Whether it affects Shopping ads, free listings or another context
• Whether a recommended value is available
• Whether the submitted information is factually incomplete
• Whether the website confirms the corrected value

Disapproved must be investigated at issue level

A disapproved product cannot serve in the affected country and reporting context.

However, “disapproved” is a result, not the root cause.

The useful information is contained in the related item-level issue:

• Issue code
• Issue name
• Severity
• Affected attribute
• Detailed explanation
• Applicable country
• Reporting context
• Documentation
• Resolution responsibility

For example, two products can both be disapproved while requiring completely different fixes:

• One has an invalid GTIN.
• The other displays a different price on its landing page.

Replacing the GTIN will not solve the price mismatch, and changing the price will not make an invented GTIN valid.

Use the Issue Details Page

Google’s Issue Details Page consolidates information about a particular problem.

It can include:

• An overview of the issue
• A description of likely causes
• Recommended actions
• Estimated business impact
• Lost click potential
• Number of affected products
• Example products
• Documentation links
• Automatic-fix options
• Review or appeal options where applicable

Google describes these functions in its Issue Details Page guidance.

Use the Issue Details Page to define the scope of the investigation, but do not inspect only the example products.

Examples help reveal a pattern. They may not represent every affected WooCommerce product or variation.

Download or filter the complete affected-product list when correcting the catalogue in bulk.

Use click potential carefully

Merchant Center may show high, medium or low click potential.

Google explains that click potential is relative to other products and is estimated from factors including historical traffic, product data and demand.

It can help prioritise work, but it should not replace compliance and data-accuracy checks.

A low-click-potential product can still:

• Represent a valuable catalogue category
• Become more important seasonally
• Be required for a complete variation group
• Reveal a systematic mapping failure
• Share an error with high-value products
• Become eligible for another market later
• Indicate that obsolete data is still active

Use click potential to schedule corrections, not to decide which product data is allowed to remain inaccurate.

Create an issue record before editing anything

For each issue, record:

• Date detected
• Merchant Center account ID
• Issue title
• Issue code where available
• Issue type
• Severity
• Account-level or product-level scope
• Affected marketing methods
• Affected countries
• Number of products
• Example offer IDs
• Complete affected-product report
• Data source
• WooCommerce product IDs
• Variation IDs
• Submitted value
• Landing-page value
• Expected value
• Suspected source
• Correction applied
• Update date
• API or source result
• Processed status
• Review status where applicable

This record helps distinguish:

• Old issues from new issues
• Corrected products from uncorrected products
• Source failures from Google processing delays
• Parent-product problems from variation problems
• Website mismatches from submission errors
• Account restrictions from item-level errors

Without a record, repeated corrections can become impossible to audit.

Identify the authoritative data source

The authoritative source is the system that should control the affected value over time.

For a WooCommerce store, it may be:

• The WooCommerce product
• The WooCommerce variation
• A global product attribute
• A product custom field
• A currency or pricing extension
• An inventory system
• An ERP
• A supplier integration
• PW Merchant API mapping
• A Merchant Center account setting
• A return-policy resource
• A shipping configuration
• A supplemental source

The issue should normally be corrected at the highest legitimate source that will continue controlling the value.

Examples:

• A wrong product title should normally be corrected in WooCommerce if WooCommerce supplies the title.
• A wrong variation colour may need correction in the global attribute term or variation configuration.
• A country-wide shipping issue may require a Merchant Center shipping configuration rather than editing every product.
• A rejected API operation may require fixing the integration mapping or request data.
• A price mismatch may require aligning WooCommerce, cache output, structured data and synchronisation timing.

A manual Merchant Center edit can conceal the real source problem temporarily.

Understand source precedence

Merchant Center can receive product information through multiple methods:

• Merchant API
• Legacy Content API sources
• Uploaded files
• Scheduled files
• XML sources
• CSV sources
• Google Sheets
• Ecommerce-platform integrations
• Products found automatically from the website
• Supplemental data sources
• Manual product entry
• Manual product edits

Before correcting a product, determine which sources contribute to it.

Record:

• Data-source name
• Source type
• Last update
• Source status
• Country and language coverage
• Feed label
• Offer ID
• Whether the source is primary or supplemental
• Whether another source uses the same product identity
• Whether automatic website discovery is active
• Whether manual edits override source values

A corrected WooCommerce value can appear to fail if another active source continues applying an older value.

Do not edit the wrong copy of a product

Duplicate or similar products may exist because of differences in:

• Offer ID
• Content language
• Feed label
• Country
• Data source
• Online versus local channel
• Parent and variation structure
• Old and new integrations
• Staging and production stores

Record the complete processed product identity rather than relying only on the visible title.

Two products with the same title may be separate Merchant Center offers.

Similarly, one WooCommerce variable product may create multiple Merchant Center offers with different variation IDs.

Match Merchant Center IDs to WooCommerce products

The Merchant Center offer ID should remain stable and traceable.

Depending on the integration, the offer ID may be based on:

• WooCommerce product ID
• Variation ID
• SKU
• A controlled prefix
• A composite integration identifier
• A previously established mapping

Never assume that a visible Merchant Center ID is the WooCommerce post ID.

Confirm the integration’s mapping rules.

For each affected offer:

1. Record the Merchant Center offer ID.
2. Record the processed product identity.
3. Open the data-source details.
4. Identify the source that submitted the offer.
5. Locate the corresponding WooCommerce product.
6. Confirm whether it is simple or variable.
7. Record the WooCommerce product ID.
8. Record the variation ID where applicable.
9. Compare SKU, GTIN, MPN and title.
10. Open the exact submitted landing-page URL.

If an offer cannot be mapped reliably, do not edit a similarly named WooCommerce product by guesswork.

Inspect the submitted value

Merchant Center evaluates the submitted product information, not merely the current WordPress editing screen.

Compare:

• The value stored in WooCommerce
• The value generated by the integration
• The value sent in the latest update
• The value shown in the processed Merchant Center product
• The value displayed on the landing page
• The value in structured product data

These values may differ because of:

• Stale cache
• Scheduled synchronisation delay
• Mapping rules
• Currency conversion
• Tax settings
• Translation filters
• Variation inheritance
• Custom product fields
• Supplier imports
• Manual Merchant Center overrides
• A competing data source
• An unsuccessful API operation

The WooCommerce edit screen is only one part of the evidence.

Open the exact landing-page URL

Do not test only the store homepage.

Open the exact URL submitted for the affected offer.

Test it:

• While logged out
• In a new private browser session
• Without an existing language cookie
• Without a currency cookie
• On mobile
• With the submitted variation selected
• With tracking parameters where used
• From the applicable country where practical
• With JavaScript enabled
• With the initial HTML source inspected

Confirm that:

• The page returns a successful response.
• HTTPS works.
• The page remains on the claimed domain.
• The correct product is displayed.
• The correct variation is selected.
• The title is accurate.
• The price matches.
• The currency matches.
• Availability matches.
• The image is accessible.
• Customers can add the item to the cart.
• Required options can be selected.
• Checkout is accessible.
• Structured data describes the same offer.

A landing page that appears correct to an administrator may behave differently for a logged-out customer or crawler.

Review variable products separately

A WooCommerce variable product is not one indivisible offer.

Each submitted variation may have its own:

• Offer ID
• SKU
• GTIN
• MPN
• Price
• Sale price
• Availability
• Image
• Colour
• Size
• Material
• Pattern
• Landing-page parameter
• Merchant Center status

When an issue affects a variable product:

1. Identify every submitted variation.
2. Record each variation ID.
3. Confirm stable item-group relationships.
4. Check required variation attributes.
5. Check that sibling variations use distinct offer IDs.
6. Open every affected variation URL.
7. Confirm the correct variation is selected.
8. Compare its price and availability.
9. Inspect its structured data.
10. Update only the variations that require correction.
11. Confirm that the parent mapping remains stable.

Correcting the parent description will not necessarily resolve a missing size or invalid GTIN on an individual variation.

Investigate issue families systematically

The following categories help identify where to look. Each specific issue should still be resolved using its own current Google documentation.

Identity issues

Examples include:

• Missing GTIN
• Invalid GTIN
• Missing brand
• Missing MPN
• Incorrect identifier-exists value
• Duplicate offer IDs

Check:

• Manufacturer packaging
• Authorised supplier records
• WooCommerce custom fields
• Variation identifiers
• Integration mappings
• Whether the product genuinely has an assigned identifier

Do not invent identifiers or reuse a barcode from another product.

Price issues

Examples include:

• Missing price
• Invalid price
• Price mismatch
• Sale-price mismatch
• Unsupported currency
• Incorrect tax inclusion

Check:

• WooCommerce regular price
• WooCommerce sale price
• Sale dates
• Variation prices
• Currency conversion
• Tax display
• Customer-group pricing
• Cache output
• Structured data
• Submitted value
• Checkout price

The product data, landing page and purchasing journey must describe the same payable offer.

Availability issues

Examples include:

• Missing availability
• Availability mismatch
• Incorrect backorder status
• Product unavailable on the landing page

Check:

• WooCommerce stock status
• Quantity
• Backorder settings
• Variation stock
• Inventory integrations
• Cache
• Product visibility
• Add-to-cart functionality
• Submitted availability

A product marked in stock should be directly purchasable under the applicable requirements.

Image issues

Examples include:

• Missing image
• Inaccessible image
• Invalid image format
• Placeholder image
• Promotional overlays
• Image too small
• Crawler blocked

Check:

• Original WooCommerce product image
• Variation image
• Public image URL
• Response status
• Robots rules
• CDN permissions
• Hotlink protection
• Image dimensions
• Watermarks or promotional content
• Integration-selected image

Replacing an image in WordPress is insufficient if Merchant Center still receives an old cached or manually overridden URL.

Title and description issues

Examples include:

• Missing title
• Missing description
• Excessive promotional text
• Inconsistent language
• Unsupported characters
• Product mismatch

Check:

• WooCommerce name
• Short description
• Long description
• Translation
• Supplier content
• Variation name
• Integration templates
• Merchant Center processed value
• Landing-page heading

The title and description should identify the actual product accurately and use the declared content language.

Category and attribute issues

Examples include:

• Invalid Google product category
• Missing colour
• Missing size
• Missing gender
• Missing age group
• Invalid condition
• Variation-group errors

Check:

• WooCommerce categories
• Google category mapping
• Global product attributes
• Attribute terms
• Variation attributes
• Custom fields
• Product-type mapping
• Country-specific requirements

WooCommerce categories and Google product categories are related mapping concepts but are not automatically interchangeable.

Shipping and return issues

Examples include:

• Missing shipping information
• Delivery-time inconsistency
• Unsupported delivery service
• Missing return policy
• Return-policy mismatch

Check:

• Merchant Center shipping services
• Merchant Center return policies
• WooCommerce shipping zones
• Shipping-method names
• Rates
• Handling times
• Transit times
• Country availability
• Public shipping policy
• Return and refund page
• Checkout estimates

Not every shipping issue should be repaired inside the WooCommerce product editor.

Website and landing-page issues

Examples include:

• Page unavailable
• Mobile page unavailable
• Mismatched domain
• Checkout unavailable
• Crawl blocked
• Redirect loop
• Product cannot be purchased
• Website needs improvement

Check:

• Claimed domain
• HTTPS
• Redirects
• Robots directives
• Firewall rules
• Maintenance mode
• Cookie walls
• Product visibility
• Cart
• Checkout
• Payment methods
• Business identity
• Contact information
• Customer policies

Website-level issues require examination of the complete customer journey.

Correct the authoritative source

After identifying the cause:

1. Back up the existing value where necessary.
2. Correct the WooCommerce product, variation, mapping or account setting.
3. Clear relevant caches.
4. Test the public page.
5. Inspect structured data.
6. Trigger or wait for the authorised data-source update.
7. Record the update result.
8. Confirm the processed value in Merchant Center.
9. Monitor the associated issue.
10. Repeat for all affected products.

Do not change unrelated product fields merely to force a new update.

A correction should be specific, explainable and reproducible.

Be careful with automatic fixes

Merchant Center may offer automatic fixes or suggested attribute values.

Google advises merchants to confirm that suggestions are accurate by comparing them with the landing page before accepting them.

An accepted suggestion can override later values supplied by another product method. This can create confusion when WooCommerce submits one value but Merchant Center continues using an accepted edit or rule.

Before accepting an automatic fix:

• Identify the affected attribute.
• Review several affected products.
• Confirm the suggested value is factually correct.
• Confirm that it matches the landing page.
• Determine whether WooCommerce can supply the correct value directly.
• Record that an override will be created.
• Understand how to revert the edit.
• Monitor future synchronisation.

Do not apply a bulk suggestion simply because it removes a visible warning.

Avoid permanent manual corrections in Merchant Center

Direct product editing can be useful for investigation or genuinely manual products.

It is risky when WooCommerce remains the intended source.

Manual Merchant Center values may:

• Override future source updates
• Hide an incorrect integration mapping
• Become outdated
• Produce differences between WooCommerce and Google
• Make later troubleshooting difficult
• Affect only one product identity
• Leave duplicate offers unchanged

When WooCommerce is authoritative, make the durable correction in WooCommerce or in the controlled integration mapping.

Submit or synchronise the correction

After correcting the source, verify that the updated product actually reached Google.

Record:

• Submission method
• Submission time
• Offer ID
• Source name
• Operation result
• Rejected fields
• Warning details
• Processed product time
• Processed value
• Current status

A local “saved” message confirms only that WordPress stored the product.

An API success normally confirms that Google accepted the request for processing. It does not guarantee final approval.

An API failure means the correction may never have reached the processed product.

Allow for processing delay

Product status information does not always update immediately.

Google’s aggregate product status documentation warns that aggregate status data can be delayed by more than 30 minutes after a product insertion or update.

The Merchant Center interface, individual product resources and aggregate reports may also update at different times.

After a correction:

• Record the update time.
• Confirm the source operation succeeded.
• Wait for processing.
• Inspect the individual processed product.
• Recheck the issue list.
• Review status history.
• Avoid repeated unchanged updates.
• Investigate only after allowing a reasonable processing interval.

Do not promise that a specific issue will disappear at an exact time.

Use status history

Merchant Center provides a View history option for examining product status changes.

Filters may include:

• Time period
• Country
• Product type
• Ads or non-ad contexts
• Product status

Status history can help answer:

• Did the disapproval begin after a WooCommerce update?
• Did a sale-price change coincide with the issue?
• Did the number of approved products fall after activating a source?
• Did the issue return after a manual correction?
• Did one country recover while another remained affected?
• Did a theme or domain migration change product status?

Use historical evidence to investigate the cause rather than assuming that the newest visible plugin is responsible.

Understand Merchant API diagnostic resources

Merchant API provides several methods for viewing product and account status.

Google’s product and issue guidance describes the following approaches.

Detailed product statuses

The products.list and products.get methods can return a product’s productStatus.

This includes:

• Destination statuses
• Approved countries
• Pending countries
• Disapproved countries
• Item-level issues
• Severity
• Affected attributes
• Documentation

Use this when investigating a specific WooCommerce offer.

Aggregate product statuses

The aggregateProductStatuses.list method provides a high-level overview of:

• Approved product counts
• Pending product counts
• Disapproved product counts
• Common issue types
• Number of affected products
• Sample products
• Reporting context
• Country

Use this to monitor overall catalogue health and identify the largest issue groups.

Aggregate results do not replace individual product investigation.

Merchant Center reports

The productView resource in reports.search can be used to filter products according to reporting-context status.

This can help identify:

• Disapproved products
• Pending products
• Eligible products
• Eligible but limited products

Account issues

The accounts.issues.list method returns problems affecting the account.

This should be evaluated separately from item-level product issues.

Rendered issue information

Merchant API provides rendered issue methods intended to produce human-readable account or product issue descriptions and documentation links.

These can help an authorised application present useful issue information without inventing its own explanation.

Interface and API wording may not always be identical. Google notes that issue titles and descriptions can differ between aggregate API output and the Merchant Center interface.

Compare:

• Issue code
• Severity
• Attribute
• Country
• Reporting context
• Documentation
• Affected product identity

Do not match issues solely by translated display text.

How PW Merchant API fits into diagnostics

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

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

• Connect an authorised Google account.
• Select an accessible Merchant Center account.
• Prepare supported WooCommerce product data.
• Submit simple and variable products.
• Update previously submitted products.
• Preserve controlled product identities.
• Record applicable operation results.
• Review supported product status information.
• Identify supported product issues.
• Schedule controlled synchronisation.
• Resubmit corrected WooCommerce data.

As a WooCommerce Google Merchant Center plugin, PW Merchant API can help trace a processed Google offer back to its WooCommerce source and communicate corrected supported attributes.

It does not replace Merchant Center’s independent diagnostics or policy evaluation.

PW Merchant API cannot:

• Guarantee product approval.
• Guarantee account approval.
• Guarantee that an issue will disappear.
• Guarantee impressions, clicks or sales.
• Decide whether a suggested Google value is factually correct.
• Create valid GTINs for products that do not have them.
• Correct an inaccessible website without website changes.
• Resolve a legal ownership dispute.
• Override Google policy enforcement.
• Remove an account suspension.
• Bypass a review cooldown.
• Make unsupported products eligible.
• Determine private Google review signals.
• Correct a competing data source that remains outside its control.
• Replace Merchant Center account administration.

WooCommerce remains the customer-facing commercial source, PW Merchant API supports applicable product communication and Google Merchant Center independently processes and evaluates the submitted data.

When an issue returns after correction

If the old value or issue returns, check:

• Whether the WooCommerce correction was saved
• Whether the correct variation was edited
• Whether the update operation succeeded
• Whether a scheduled sync ran
• Whether another source supplies the product
• Whether a manual Merchant Center edit overrides the source
• Whether an automatic fix applies
• Whether a supplemental source changes the attribute
• Whether a supplier import restored the old value
• Whether a cache serves old landing-page content
• Whether structured data still contains the old value
• Whether another country or language version remains incorrect
• Whether the product has a different offer ID
• Whether the issue is account-level rather than product-level

Persistent recurrence usually indicates unresolved source precedence or an incomplete correction path.

When to request a review

Not every Needs attention issue requires a manual review.

Some product-data issues are reprocessed after corrected information is submitted. Other account or policy issues may provide a specific review option.

Before requesting any review:

• Open the exact issue.
• Read the current Google instructions.
• Correct the complete scope.
• Update the authoritative data source.
• Confirm the public website.
• Confirm the processed product data.
• Check all affected countries.
• Check all affected marketing methods.
• Confirm that no competing source restores the error.
• Allow the correction to process.
• Use the issue-specific review option only when applicable.

Do not request repeated reviews before resolving the underlying problem.

Review requests, cooldowns and account appeals require a separate controlled process.

Build a preventive WooCommerce workflow

Merchant Center diagnostics should not be examined only after a major disapproval.

Use a recurring internal process that reviews:

• New products
• Updated products
• Sale starts and endings
• Currency changes
• Stock changes
• Variation changes
• Image replacements
• Category mapping changes
• Translation updates
• Shipping configuration
• Return-policy changes
• Domain migrations
• Theme changes
• Structured-data changes
• Integration updates
• Source additions or removals
• Account-access changes

For each material store change:

1. Update WooCommerce.
2. Confirm the public page.
3. Inspect structured data.
4. Confirm the authoritative source.
5. Process the Merchant update.
6. Check the operation result.
7. Check the processed product.
8. Review Needs attention.
9. Record any new issue.
10. Correct systematic failures before they spread.

Common mistakes

Looking only at the three summary cards

The cards highlight major issues but may not display the complete inventory.

Leaving Prioritized fixes enabled during a complete audit

Lower-impact issues may remain hidden.

Treating every problem as a product-field error

Some issues originate in account settings, shipping, policies, website access or data sources.

Editing products before recording the exact issue

The original evidence is lost, making it harder to prove which change resolved the problem.

Using only the visible product title

Titles are not reliable product identifiers. Use the complete Merchant Center identity and offer ID.

Correcting the parent instead of the variation

Variation-specific price, availability, image or identifier problems may remain active.

Checking only one country

A product can be approved in one country and disapproved elsewhere.

Checking only Shopping ads

Free listings and other reporting contexts can have different statuses.

Assuming a successful API request means approval

Submission and policy processing are separate stages.

Making permanent manual Merchant Center edits

The next WooCommerce synchronisation may overwrite them, or the manual value may override later source updates.

Accepting automatic suggestions without verification

Suggested values should be checked against the actual product and landing page.

Ignoring duplicate data sources

An obsolete source can continue submitting old or conflicting data.

Repeatedly resubmitting unchanged products

This creates noise without correcting the underlying problem.

Requesting a review too early

A review should follow a complete correction, not replace it.

Frequently asked questions

Where is Diagnostics in the current Merchant Center interface?

The principal product issue area is now found under Products → Needs attention. Older instructions may still call it Diagnostics.

Does “Needs attention” mean my account is suspended?

No. The section contains many issue types. Some affect individual products, while others can affect an entire account.

What is the difference between an account-level and product-level issue?

An account-level issue affects account eligibility, setup or a broad group of products. A product-level issue is associated with individual offers or product attributes.

Why can I see only a few issues?

The Prioritized fixes filter may be hiding issues estimated to have little or no performance impact. Turn it off for a complete audit.

What are high-impact issue cards?

They summarise issues that Google estimates have the greatest effect on the account and show the number of affected products.

What is click potential?

It is Google’s relative estimate of how likely a product is to receive clicks compared with other products, based on factors such as traffic, product data and demand.

Should I ignore products with low click potential?

No. Click potential can help schedule work, but product data should remain accurate and compliant.

Why is a product approved in one place and disapproved in another?

Status can differ by country and marketing method. Check the reporting context and applicable countries.

Is limited the same as disapproved?

No. A limited product may remain eligible but have restricted performance. A disapproved product cannot serve in the affected context.

Does approved mean the product will appear on Google?

No. Approval indicates eligibility for the applicable context. It does not guarantee impressions, ranking, clicks or sales.

Why does Merchant Center show an old value after WooCommerce was updated?

The Merchant update may not have run, processing may be incomplete, cache may be stale or another source or override may control the value.

Should I edit the product directly in Merchant Center?

Only when direct editing is intentionally part of the source strategy. If WooCommerce is authoritative, make the durable correction in WooCommerce or its controlled integration.

Can Merchant Center automatic fixes be trusted?

They should be reviewed. Google recommends confirming that suggested values are accurate and match the landing page before accepting them.

Can a manual edit override WooCommerce updates?

Yes. Merchant Center edits and accepted suggestions can override values supplied through another product method.

How do I find all products affected by one issue?

Open the issue, use View products or the Issue Details Page and download the complete affected-product list.

Why does the example list show only some products?

Examples are provided for diagnosis and may not contain every affected product. Use the full filtered or downloadable list.

How do I match a Merchant Center offer to WooCommerce?

Use the offer ID, processed product identity, source information, SKU and the integration’s documented ID mapping. Do not rely only on the product title.

Why are only some variations affected?

Each variation can have separate price, stock, image, identifier, attribute and landing-page information.

Can a data source upload successfully while products are disapproved?

Yes. A successful upload or API request does not mean every submitted product satisfies data and policy requirements.

Can one product be supplied by several sources?

Merchant Center can receive primary, supplemental, manually edited and automatically found information. Review the actual source structure and precedence.

How quickly do Merchant API status results update?

Google states that aggregate product status information can be delayed by more than 30 minutes after an insertion or update. Other processing and review times can vary.

Should I resubmit a pending product repeatedly?

No. Confirm that the meaningful update succeeded and allow processing before submitting another unchanged update.

Can PW Merchant API remove all Needs attention issues automatically?

No. It can support applicable product communication and supported diagnostic workflows, but the store owner must correct the real WooCommerce, website, account or policy cause.

Can a plugin guarantee Google approval?

No. Google independently evaluates accounts, websites and products.

Do all issues require a review request?

No. Many product-data issues are reprocessed after corrected information is submitted. Follow the exact issue instructions.

Should I request a review immediately after changing WooCommerce?

First confirm that the corrected data reached Merchant Center, the landing page is accurate and every affected product and country has been addressed.

What if the issue returns after every sync?

Investigate source precedence, manual overrides, automatic fixes, supplier imports, caches and competing product sources.

Final checklist

Before considering a Needs attention issue resolved, confirm that:

• The correct Merchant Center account was opened.
• The Merchant Center account ID was recorded.
• Products was opened.
• Needs attention was opened.
• High-impact issue cards were reviewed.
• View all issues was checked.
• Prioritized fixes was turned off for the complete audit.
• Account-level issues were identified.
• Product-level issues were identified.
• Data-source issues were identified.
• The exact issue title was recorded.
• The issue code was recorded where available.
• Severity was recorded.
• Affected marketing methods were recorded.
• Affected countries were recorded.
• Warning dates were recorded.
• Review deadlines were recorded where applicable.
• The Issue Details Page was opened.
• The official Google documentation was opened.
• Business impact was reviewed.
• Click potential was reviewed.
• Example products were recorded.
• The complete affected-product list was downloaded.
• The number of affected products was recorded.
• Every relevant offer ID was recorded.
• Processed product identities were recorded.
• Data-source names were recorded.
• Source types were recorded.
• Source update times were reviewed.
• Primary sources were identified.
• Supplemental sources were identified.
• Automatically found products were reviewed.
• Manual Merchant Center edits were reviewed.
• Automatic fixes were reviewed.
• Suggested attribute values were reviewed.
• Competing sources were investigated.
• Obsolete sources were identified.
• WooCommerce product IDs were recorded.
• WooCommerce variation IDs were recorded.
• SKUs were compared.
• GTINs were compared.
• MPNs were compared.
• Brands were compared.
• Simple products were tested.
• Variable products were tested.
• Every affected variation was tested.
• Parent and variation mappings were reviewed.
• Item-group relationships were reviewed.
• The submitted title was inspected.
• The submitted description was inspected.
• The submitted price was inspected.
• The submitted sale price was inspected.
• The submitted currency was inspected.
• The submitted availability was inspected.
• The submitted image was inspected.
• The submitted category was inspected.
• Required attributes were inspected.
• The exact landing-page URL was opened.
• The page was tested while logged out.
• The page was tested without old cookies.
• The page was tested on mobile.
• HTTPS was verified.
• Redirects were reviewed.
• The claimed domain was confirmed.
• The correct product was displayed.
• The correct variation was selected.
• The displayed title matched.
• The displayed price matched.
• The displayed currency matched.
• The displayed availability matched.
• The image was accessible.
• Add to cart worked.
• Required options worked.
• Checkout was accessible.
• Shipping information was reviewed.
• Return information was reviewed.
• Structured product data was inspected.
• Structured-data price matched.
• Structured-data availability matched.
• Structured-data product identity matched.
• Duplicate Product schema was reviewed.
• WordPress caches were cleared.
• Object caches were cleared.
• Server caches were cleared.
• CDN caches were cleared.
• The authoritative source was identified.
• The correction was made in the authoritative source.
• Unrelated fields were not changed.
• The public page was retested.
• The product update was submitted.
• The update time was recorded.
• The API or source result was recorded.
• Rejected operations were investigated.
• The processed Merchant Center value was inspected.
• Processing time was allowed.
• Individual product status was rechecked.
• Aggregate status was rechecked.
• Approved countries were reviewed.
• Pending countries were reviewed.
• Disapproved countries were reviewed.
• Shopping ads status was reviewed.
• Free listings status was reviewed.
• Limited products were reviewed separately.
• Status history was reviewed.
• The issue did not return after the next synchronisation.
• Duplicate offers were reviewed.
• Old source values no longer override the correction.
• Every affected product was retested.
• A review was requested only when applicable.
• Future WooCommerce changes will be monitored.

The Needs attention section is not simply a list of errors to hide.

It is a structured diagnostic view of the relationship between Merchant Center account settings, submitted product information, WooCommerce landing pages, marketing methods and target countries.

A reliable correction begins by recording the exact issue and its scope. It continues by matching every affected Merchant Center offer to the correct WooCommerce product or variation, identifying the authoritative data source and comparing the submitted value with the public purchasing experience.

The correction should then be made in the source that will continue controlling the value. The resulting update must be submitted, processed and checked separately for every relevant country and marketing method.

Merchant API provides account, product and aggregate status resources that can support this workflow, but API success is not equivalent to product approval. Similarly, a WooCommerce Google Merchant Center plugin can support product communication but cannot replace accurate product information, an accessible store or Google’s independent evaluation.

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

When merchants treat Needs attention as an evidence-based workflow rather than a collection of isolated warnings, they can correct systematic WooCommerce problems more accurately and reduce the likelihood that old, duplicate or competing data will recreate the same issue.