Fix Disapproved Products in Google Merchant Center: Step-by-Step

What a disapproved product means in Google Merchant Center

A disapproved product is blocked from showing across Google until the issue behind it is fixed. Merchant Center groups problems by severity, and the difference decides how urgent your fix is:

One habit saves hours: read the count by issue, not by product. A few thousand disapproved products usually trace back to a handful of root causes, such as one price setting, one missing field mapping, or one image template. Fix the cause once and the whole group clears.

How to find your disapproved products

1. Open Merchant Center and go to Products under Products & store.
2. Select the Needs attention tab. It lists every product with an issue.
3. Filter by impact, status, label, title or attention type to isolate one issue at a time.
4. Click an issue name to open its detail page, which lists the affected products and the recommended action.
5. Download the list as a CSV if you plan to fix products in bulk in your store or feed.

Work top-down by the number of products affected, and clear account-level issues before touching individual items.

The most common disapproval reasons and how to fix each

These are the product data issues that show up most often, with the fix that actually resolves them:

How to fix a mismatched price disapproval

Price mismatch is the issue that returns most often, because it is a timing and consistency problem rather than a one-off typo. Google compares the price in your feed with the price on the landing page or in your structured data. Google's own list of causes is worth checking in this order:

1. Timing gaps. Your site changed price but Merchant Center still holds the old value, common when prices change often.
2. Wrong structured data. The markup on the page shows a different price than the visible one.
3. Crawler sees a different page than customers. Geo redirects, currency switchers or scripts that only run for browsers can show Googlebot another price.
4. Sale price errors. Start and end dates or timezones in sale_price_effective_date do not line up with the site.
5. Bulk pricing. The total price for a minimum order quantity was not submitted.
6. Already fixed. The mismatch was resolved after the notification was generated.

The fix itself is direct. Make the feed price match the website price in the correct currency, and make sure the price and currency match the amount shown prominently on the page. Then align your markup with the same figures:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Running Shoe",
  "offers": {
    "@type": "Offer",
    "price": "49.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}

The rule I apply is to generate the page, the markup and the feed from the same database field. Three separate copies of a price will drift apart eventually, and Merchant Center will find it before you do. Availability mismatches follow the same logic: one source of truth, three outputs.

If the same catalog is synced to several channels and the mismatches keep coming back, the problem is usually the sync pipeline rather than individual products. That is the situation product feed management is built for. Otherwise, once the fix is live, Google re-crawls disapproved products over the next few hours or days, and its documentation says a website review can take up to 12 hours. You can also follow Google's mismatched price guide for the full cause list and request a website check for faster reapproval.

How to fix GTIN, brand and image issues

Identifiers. If a product has a manufacturer GTIN, use exactly that. If it is custom-made or has none, tell your platform so instead of typing a made-up number. An invented GTIN turns a missing-data warning into a conflicting-data disapproval, which is harder to clear.

Brand. Use the real brand. If the product has none, use the manufacturer or your store name. In Shopify the brand comes from the Vendor field, so a blank Vendor across a collection creates the same disapproval for every product in it.

Images. Fix them at the source file. Merchant Center has an automatic image improvements setting that can strip some overlays, but do not rely on it for watermarks and promo banners; a clean product shot on a neutral background passes reliably and also converts better.

How to fix disapproved products in bulk

• Fix at the source, not in Merchant Center. Edits made only inside Merchant Center on a product that comes from a feed can be replaced the next time the feed is fetched. Treat your store or feed as the source of truth.
• Group by issue. Use the Needs attention filters, then fix one issue across all its products before starting the next.
• Use the CSV. Download the affected list, correct the values, and re-upload or apply the change in your platform.
• Verify a sample before you request a review. Open three or four affected product pages and confirm the fix is live on the page and in the data source.

How to request a review after fixing

Do not request a review until the fix is live. If a review fails, Merchant Center starts a cool down period during which the review button is disabled, the cool down grows with repeated failures, and Google support cannot shorten it. One premature click can cost you days.

Before you request a review, Google requires the following, as described in Google's review request guide:

• Complete identity verification if you are prompted for it, using a government-issued ID or business registration documents.
• Make sure your data source is not empty; add at least one product to All products if needed.
• Resolve the other required actions listed under Needs attention.

Then request the review:

1. Go to Products and open the Needs attention tab.
2. Select I fixed the issue and read the acknowledgment.
3. Select Request review.

If you believe the issue is wrong, choose I disagree with the issue instead and attach your reasoning or documents. As of September 2026, Google says a review can take up to 7 business days, and approved products appear within 24 hours. You get a notification when the review is requested and when it completes.

How to stop products getting disapproved again

• Generate price, availability and structured data from the same database field.
• Check your pages as a crawler would see them: geo redirects, currency switchers, cookie walls and login gates can all change what Googlebot sees.
• Validate identifiers, brand and image size when products are imported, not after Google flags them.
• Set sale dates with explicit timezones and remove expired sale prices.
• Open the Needs attention tab weekly. Warnings are cheap to fix and expensive to ignore.

If your catalog is large, spans several platforms, or disapprovals keep returning after every fix, it may be faster to hand the feed over. You can request a free quote and describe your store and the issues you are seeing.