Google Merchant Center Disapproved Products: 12 Errors and Fixes

What does "disapproved" mean in Google Merchant Center?

A disapproved product, shown with the status Not approved, can't appear anywhere on Google: not in Shopping ads, not in Performance Max, and not in free listings. The cause is either a policy violation or product data that doesn't meet Google's product data specification.

Every product in Merchant Center sits in one of five statuses. Reading the status correctly tells you whether to wait or act:

Where do I find disapproved products, and what should I fix first?

Go to Products and open the Needs attention tab. Issues are grouped by name, each with a count of affected products. Fix account-level issues first, then work down the item-level list from the issue that affects the most products.

One root cause, such as a wrong currency or a broken feed column, can take down hundreds of products at once. A price issue hitting 400 items outranks an image issue hitting three. Use this order:

1. Check scope Is there an account-level issue? Resolve it first; fixing items in a suspended account changes nothing.
2. Rank issues Sort Needs attention by number of affected products, largest first.
3. Find the source Is the bad value coming from the feed (Shopify app, WooCommerce plugin, XML file, API) or from the website itself?
4. Fix at the source If you edit a product directly in Merchant Center, the next feed sync can overwrite your change.
5. Reprocess or review Data errors clear once the feed refreshes; policy disapprovals need a review request.

What are the 12 most common disapproval reasons?

The twelve issues below are among the disapprovals online stores run into most often. The table pairs each issue name with its usual cause and the durable fix.

The five issues below cost merchants the most time, so they get a closer look.

How do I fix a price mismatch in Merchant Center?

A price mismatch appears when the price in your feed differs from what Googlebot sees on the landing page. The fix is to make three things agree: the feed, the visible page price and the page's structured data.

According to Google, Googlebot reads the price from the HTML your server returns and from structured data markup. If the price is injected by JavaScript after the page loads, Google treats that as an error. Cart-level discounts, variant prices that swap via JavaScript and geo-based currency switching are frequent culprits, along with sale dates set in the wrong time zone.

Tax: the US and UK rules are opposite

In the US and Canada, the price attribute must exclude sales tax; you configure tax in the account instead. In most other countries, including the UK and EU markets, the price must include VAT and match the landing page. A store selling to both markets from one feed without separate country handling will trigger mismatches in one of them.

Worked example

You cut a product from $129 to $99 on your site at 10:00 a.m., but your feed only refreshes nightly at 3:00 a.m. When Googlebot crawls that day it sees $99 while the feed still says $129, and the product is disapproved. Two ways out:

• Add the discount to the feed in advance with sale_price and sale_price_effective_date, so the feed flips at the same moment as the site.
• Fetch the feed several times a day, or push changes through the Merchant API if your platform supports it.
• Run the Rich Results Test on the product page and confirm price and priceCurrency in the Product markup match the visible price.
• Check that the currency Googlebot sees is the one you submitted, not a converted one chosen by the visitor's location.

After you fix it, Google says it re-crawls disapproved products over the next few hours or days, and a website review can take up to 12 hours, during which you can't submit a new request.

How do I fix a misrepresentation suspension?

Misrepresentation is an account-level issue, not an item issue: Google has decided your business or products could mislead shoppers, and usually every product stops showing. You fix it by genuinely improving the site's trust signals and only then requesting a review.

Google's policy cites examples such as listing items as available when you can't fulfil the orders, giving false or hidden business identity and contact details, not disclosing the total price including taxes, fees and shipping costs, denying returns despite a stated return policy, and miracle-cure claims. For most violations Google sends a warning email with 7 or 28 calendar days to fix the problem before suspension; egregious violations can lead to suspension without warning.

Site trust checklist

• Contact: A physical address, phone number and email. A contact form alone may not be enough. Show the legal business name in the footer.
• Returns and refunds: A clear page with the return window, conditions and who pays return shipping, linked from the footer.
• Shipping: Delivery times and costs visible before checkout.
• Checkout: HTTPS, working, and the cart price matches the product page.
• Legal pages: Terms of service and a privacy policy that reflect how you actually operate.
• Claims: Remove "guaranteed results", "lowest price anywhere", fake countdown timers and unproven health claims.
• Consistency: Business name in Merchant Center, the logo on the site and the domain all line up.

Why is my GTIN invalid, and what if a product has no barcode?

An invalid GTIN error means the number is malformed, sits in a range Google rejects, or is valid but belongs to another product. If the manufacturer never assigned a GTIN, don't make one up; submit brand and mpn instead.

Google accepts UPC (GTIN-12), EAN (GTIN-13), JAN, ISBN-13 and ITF-14 (GTIN-14). Convert 8-digit UPC-E codes to 12 digits and ISBN-10 to ISBN-13. Google rejects:

• Restricted-range codes starting with 02, 04 or 2 (in-store scale and internal codes land here)
• Coupon-range codes starting with 05, 98 or 99
• Codes with a wrong check digit
• Guessed or randomly generated numbers

Private-label and handmade products often have no GTIN, and that's fine: if you are the only seller or it's a store brand, you don't need to submit one. The classic mistake is putting the SKU into the platform's "Barcode" field so it flows to the feed as a GTIN. With variants, each size and color has its own GTIN; copying the parent's barcode to every variant causes incorrect-GTIN warnings.

How do I avoid image disapprovals?

Your main image must be a clean product photo: no price, promo text, call to action, watermark, border or promotional logo. From January 31, 2027, Google requires every product image to be at least 500 x 500 pixels.

In practice the problem is usually a platform sending a thumbnail URL. Open one image_link from your feed in a browser and check its real dimensions. During sales, "30% OFF" badges added to storefront images also leak into the feed and trigger mass disapprovals. Keep the main product image text-free and use promotional artwork elsewhere.

How do I fix availability and landing page errors?

Availability errors happen when the feed's availability value contradicts the product page; landing page errors happen when the link is broken or points to the wrong page. Both are fixed by making the feed reflect the live site.

availability accepts four values: in_stock, out_of_stock, preorder and backorder. For the last two you must also send availability_date and show that date on the landing page. Don't delete a product just to stop it showing: an item added back after deletion can take a long time to show again. Use out_of_stock when you can't take orders, or the pause attribute or excluded_destination when you only want to hide it.

For landing pages, check that the URL returns 200, robots.txt doesn't block Googlebot, there's no geo-redirect to another domain, and the right color or size is preselected. For a feed structure with correct variant links, see our Performance Max feed setup guide.

Where do I fix feed errors on Shopify, WooCommerce and other platforms?

The durable fix almost always belongs in the system that generates the feed. A manual edit in Merchant Center can be wiped out by the next sync.

Disapproved products are invisible on the ads side too. After clearing disapprovals, check whether impressions and revenue actually recover across channels; Marpany's ad performance view puts Google, Meta and store data side by side so you can see the rebound.

How do I request a review or appeal in Merchant Center?

For data errors (price, availability, GTIN) you usually don't need a review: the product reprocesses once the feed is fixed. For policy disapprovals, use the Request review option on the product's or account's issue.

Merchant Center gives you two routes: after fixing a problem such as a price mismatch, request a website check to speed up reapproval; if you believe the decision is wrong, click I disagree with the issue and then Request review. A simple rule:

• If you changed the feed or site: confirm the change is visible in the product details, then request a review.
• If you changed nothing and the product complies: appeal with a short, evidence-based explanation.
• If the account has a misrepresentation issue: don't appeal until every trust page is complete; account reviews typically take about 7 business days.

Once products are approved, deciding how to advertise them matters just as much. Our Standard Shopping vs Performance Max comparison and the Google Ads optimization guide cover the next step.

What should I do today?

1. Scan Open the Needs attention tab under Products and list issues by number of affected products.
2. Check the account If there's an account-level issue, work through the trust checklist above.
3. Fix the feed Correct price, availability and GTIN errors at the source platform.
4. Clean images Replace images with overlays or small dimensions; audit for 500 x 500 before 2027.
5. Request a review Submit one reasoned review for policy disapprovals and track the result.