Merchant Center Product Issues and Diagnostics: How to Fix Them

This guide is based on Google Merchant Center Help: product visibility and status, requesting a review of your issues, and the "How to fix" articles for mismatched product price, automatic updates: mismatched price, mismatched product availability, product page unavailable, unable to check product pages, limited performance due to a missing GTIN and invalid GTIN format, all checked on 10 November 2026. It assumes your products are already in Merchant Center. For the account setup and the policies themselves, see our Google Merchant Center basics guide; for data sources and attributes, see Merchant Center product data.

Where issues show

Merchant Center collects problems in one place: the Needs attention tab, above the summary cards on the Products page. It holds two kinds of issue.

• Product-level issues. These are listed in the "All products that need attention" table. Each product links to its details page, where a "What needs attention" section explains the problem.
• Setup and policy issues. Google says these "show in a banner at the top of your Merchant Center". You can also open them from the Needs attention tab with View setup and policy issues.

Inside the tab, the filter icon above the table narrows the list to one issue, and the download icon exports a .csv of the affected products, either for one issue or for all of them. Google's help for some issues notes that the tab may open with a "Prioritized fixes" toggle on. To see every issue, turn it off and select Show all fixes.

If your products come from a file and the file itself has errors, those show in the data source instead. Our product data guide covers that report. This page covers what happens after the data is in.

The five product statuses

The Status column on the Products page shows whether Google has approved a product. Google says "There are 5 statuses", and that it "controls the approval status for products added to Merchant Center". The Visibility column is separate. It shows whether you have chosen to show or hide the product.

Two related labels can look like issues but are not statuses. "Needs Update" is "an indicator overlaid on existing statuses". Products get it 30 days after their last update, and Google warns that neglected data "can result in decreased visibility and the removal of your product from Merchant Center". Hidden products, which you control in the Visibility column, "will be automatically archived after 14 days".

Limited and Not approved are the two statuses to work on. A Not approved product earns nothing. A Limited product still shows, which makes it easy to miss.

Product issues and setup and policy issues

A product issue affects the listed products. A setup and policy issue affects your whole Merchant Center setup, and Google says it can lead to "warnings, disapprovals, or suspension". The two are handled differently.

• Product issues are fixed in the product data or on the product page. Then you request a website check or a review from the product's details page.
• Setup and policy issues come with a warning period "of 7 or 28 days". During it, Google says, "You can request one courtesy review of your account at any time". If the issues aren't resolved, your products keep showing until the period ends, and "A final review occurs at the end of the warning period." A review "will apply to all issues for the country you sell products in".

Price and availability mismatches sit between the two levels. Google's help for each says that, on enough products, they can lead to account suspension. Treat a long list of either one as an account problem, not a product problem. Our basics guide covers the policies and suspensions, including Misrepresentation.

Price mismatches

Google says Googlebot "routinely crawls your website landing pages and compares the price [price] attribute in your data source with the prices on your landing page or in your structured data markup (if implemented)". A product whose prices don't match "may be disapproved".

Two details from Google's help catch many stores:

• It reads the HTML the server returns. Google says that "If data on your website is passed dynamically with JavaScript after the page is loaded, this will trigger an error."
• It reads the structured data too. If the page shows a converted or regional price while the markup still holds the base price or default currency, the product stays disapproved. Google suggests checking the Offer block in the rich results test. Our product structured data guide covers that markup.

Google's other common causes are timing, sales and quantities:

• The website changes before the product data catches up. Google's answer is a scheduled file fetch or the Merchant API.
• A sale_price with a wrong sale_price_effective_date or time zone.
• Items sold in a minimum quantity, where "the total price for the minimum number of items sold must be submitted".

After a fix, Googlebot re-crawls disapproved products "over the next few hours or days". If the prices match, the product is approved again.

Automatic item updates can correct the price from your page, but they don't clear the problem. In Google's words, "we continue to treat products with mismatches as critical errors that can lead to account suspension." Their settings are on the Automations tab of Products.

Availability mismatches

The rule is the same as for price. The availability value in your product data and the information on the landing page "must be the same", and "Too many products with incorrect availability can lead to account suspension." Google again names the usual cause as the time difference between website and data updates. Its advice is to schedule product data updates to match your store's updates, or to use automatic item updates if prices and stock change often.

Don't use out_of_stock to take products off Google. Google says to "use the pause [pause] attribute to temporarily pause your products for up to 14 days". For longer, it points to the excluded destination attribute.

Landing page errors

Two issues are about Google not being able to load the page at all.

Product page unavailable. Google says it disables products whose landing page is unavailable, and they "stop showing in ads and free listings until Google can access the landing page". Its list of common crawl errors:

• Page not found (404).
• Too many redirects. The URL should have no more than 2 redirects.
• Couldn't connect, or an HTTP 5xx response.
• The robots.txt file couldn't be reached.
• The hostname couldn't be resolved, which is a DNS problem.
• The URL doesn't start with http:// or https://, or doesn't use the domain you verified in Merchant Center.

Unable to check product pages. Here robots.txt blocks the crawler, or the page returns an HTTP error. Google asks that robots.txt allow both "'Googlebot' (used for landing pages) and 'Googlebot-image' (used for images)" to crawl the full site. It says changes "may take 24–72 hours to be reflected" on the Needs attention page.

For both, Google suggests testing the page with the URL Inspection tool, fetched as desktop or smartphone. Our guides to URL Inspection, robots.txt and 404s and redirects cover those checks. Pages that go down now and then are a hosting matter; see uptime monitoring.

Missing and invalid GTINs

"Limited performance due to missing value: GTIN" is a typical Limited issue. Google shows it when you've submitted products "in a category that we suspect should have a GTIN" without one. It says products with an assigned GTIN but submitted without it "may have limited visibility". The value must be the one "allocated by the manufacturer". You can't make one up.

"Invalid GTIN in unsupported format" means the number itself is wrong. Google's reasons are characters that aren't numerals, a format that doesn't match a standard GTIN type, the wrong length ("GTINs are 8, 12, 13, or 14 digits"), or a failed check digit. If your product has a barcode, Google says the GTIN is normally on the packaging.

Some products have no GTIN at all, such as custom or handmade goods. When to leave the GTIN out and how identifier_exists works are covered in GTIN, brand and identifier_exists in our product data guide.

Fixing issues and requesting a review

Google's fix steps follow the same pattern for each of these issues:

• One product. In Needs attention, filter to the issue, open the product, select Edit product, correct it and save.
• Many products. Download the .csv for the issue, correct those products in your data source, then upload the data again or wait for the next fetch.

Next, tell Google. Your options depend on whether you fixed the issue or think Google got it wrong.

Three rules from Google's review article are worth knowing before you click:

• Some steps come first. The review button may be greyed out until you finish merchant verification. Your data source also can't be empty.
• Failed reviews lead to a cool down. If issues aren't resolved by the second review attempt, "a one-week cool down period may begin". Google says support "can't bypass or shorten" it, and that it "may increase with each unsuccessful review".
• Approval isn't instant. Google says the whole review "may take up to 2 weeks". Approved products "will be eligible to show across Google within 24 hours".

Since a failed review costs time, check the fix on the live page before you ask. For a Misrepresentation or store transparency suspension, Google's checklist is merchant verification, business details on the site that match Merchant Center, clear return and shipping policies, and product data that "exactly match[es] your online store". Our ecommerce launch checklist covers those pages.

How we work through the list

This part is our own practice, not Google's guidance.

• Setup and policy banners come first. They put every product at risk, so we read the email and the issue page before we touch any product.
• Then the largest product issues. We download the .csv and look for what the products have in common, such as one template, one category or one sale.
• We fix the source, not Merchant Center. A price fixed with Edit product can be overwritten by the next fetch, and the page may still be wrong. So we correct the store or the feed, then confirm one product with the URL Inspection tool and the rich results test before we request a check.
• Limited products get a turn as well. Missing GTINs on branded goods are usually quick to add.
• We check the tab again a few days later. Then we keep an eye on it after any change to the product templates or prices.

Once products are approved, what they earn in ads depends on the campaign. See our guides to Shopping campaigns and Performance Max.

Frequently asked questions

What is the difference between Limited and Not approved in Merchant Center?

A Limited product is showing on Google, but only in some places or without all its data, for example in some countries but not others. A Not approved product can't be shown on Google at all until the errors are fixed.

Where do I find product issues in Merchant Center?

In Products, open the Needs attention tab. Product issues are listed in a table you can filter and download as a .csv. Setup and policy issues show in a banner at the top of Merchant Center and under View setup and policy issues.

How long does it take for a fixed product to be approved again?

Google says a website check may take up to 12 hours, and that Googlebot re-crawls price-disapproved products over the next few hours or days. A policy review can take 7 business days or more. Approved products become eligible to show within 24 hours.

Why does Merchant Center say my price doesn't match when it looks right?

Google compares your data with the HTML your server returns and with your structured data. A price added by JavaScript after the page loads, or markup that still holds a different price or currency, can cause the mismatch. The mismatch may also have been recorded at an earlier time, so check the timestamp.

Can I set products to out of stock to pause them on Google?

Google says not to. Use the pause attribute to pause products for up to 14 days, and the excluded destination attribute for longer.

Most Merchant Center issues are fixed on the website, not in Merchant Center. See our website development and website maintenance services and all our services, or email [email protected].