Disapproved Products in Google Merchant Center: 10 Reasons and How to Fix Them

A disapproved product stops showing on Google. A product with a warning keeps showing, but its performance may be limited.

Do you have disapproved products in Merchant Center and don't know where to look for the error? It may sit in the data your product feed sends, on the landing page, or in your account settings.

I'll go through ten disapproval reasons with you and show what to fix for each one. I take the process and the recovery times from current Google Help.

10 reasons why Merchant Center disapproves products

Merchant Center shows product issues on the Needs attention tab. The reason listed for a product tells you where the fix starts. The order below is not a frequency ranking.

1. Missing or incorrect GTIN

Cause: The GTIN is missing from the feed, or it doesn't match. According to Help on GTIN, Google recommends it for all products that have a GTIN assigned by the manufacturer.

Fix: Only submit a GTIN when you know for sure it's correct. If in doubt, leave it out.

2. Goods without manufacturer identifiers

Cause: The product has no GTIN, MPN or manufacturer brand. As examples, Help lists custom or one-of-a-kind goods, such as custom-printed T-shirts, artwork or handmade goods.

Fix: For such a product, submit the identifier exists [identifier_exists] attribute with the value no [no] or false [false]. Example: a hand-sewn leather handbag from your own workshop has none of the identifiers, so identifier_exists with the value no goes into the feed.

3. Brand [brand]

Cause: The brand [brand] attribute is missing for a product that has a clearly associated brand or manufacturer. Or the attribute contains a guessed or made-up value.

Fix: For a product with a clearly associated brand or manufacturer, fill in the brand. Only submit it when you know it's correct. Don't guess the value or make it up. If a product lacks the manufacturer brand as well as a GTIN and MPN, follow the previous point with the identifier_exists attribute.

4. Price mismatch [price]

Cause: Googlebot regularly crawls landing pages and compares the price [price] attribute in the data source with the price on the page and in the structured data. Example: the feed sends CZK 1,290, the page shows CZK 1,190 after a discount.

Fix: Align the price in all three places: in the feed, on the page and in the structured data. As a safety net, use automatic item updates for price, availability and condition on the Automations tab (Products & store → Products). They update the product price based on the landing page.

5. Outdated availability [availability]

Cause: The feed reports different availability than the website shows. Example: the feed is generated once a day at night and the product sells out in the morning. Until the next generation, the feed reports in stock and the page says sold out.

Fix: Set a temporarily sold-out product to out_of_stock in the availability [availability] attribute. Don't delete the product from your data. According to Merchant Center Help, the landing page must not return a 4xx or 5xx error code. Automatic updates on the Automations tab can also align availability with the website.

6. A landing page Google can't reach

Cause: Google verifies the price by crawling the landing page. If it can't reach the page, it has nothing to compare the feed price with.

Fix: Check the landing page URL of the disapproved product in Search Console with the URL Inspection tool. The tool shows whether Google can reach the page. If it can't, pass the finding to your developer. In this case, the fix belongs on the website.

7. Shipping and returns

Cause: The disapproval refers to your shipping or returns settings. You'll find both settings in the left navigation of Merchant Center under Shipping and returns, and the return policy on the Return policies tab.

Fix: Check that you have both shipping and a return policy filled in. Shipping costs must match what the customer sees on the checkout pages of your website. According to Help on inaccurate shipping costs, align them with the website. If you can't submit exact shipping rates, you can slightly overestimate the costs in Merchant Center. The return policy must meet the minimum requirements for the target country. Until it does, the product stays disapproved.

8. Restricted products

Cause: The product falls under a policy that restricts its promotion. Merchant Center policies restrict, for example, the promotion of alcohol and have their own rules for healthcare and pharmaceutical products.

Fix: Find the policy the disapproval refers to and meet its conditions. If you think the disapproval is wrong, request a review. It can take up to 7 business days.

9. Apparel: gender [gender] and age group [age_group]

Cause: The attribute is missing or has a value outside the allowed list. Gender [gender] has only the values male, female and unisex, entered in English. It is required for free listings in the Apparel & Accessories category. For paid ads, it is required only in selected countries, and Czechia isn't among them.

Age group [age_group] has five values: newborn (0–3 months), infant (3–12 months), toddler (1–5 years), kids (5–13 years) and adult (13 years and older).

Fix: Rewrite the values to allowed ones. Example: women → female, a kids' jacket for a four-year-old → toddler. If your e-commerce store can't generate the attributes right away, a supplemental feed adds them without a developer.

10. Small images

Cause: The product image has a lower resolution than Help allows. According to Help on images that are too small, the minimum is 100 × 100 px, and 250 × 250 px for apparel.

From January 31, 2027, Google requires a minimum image size of 500 × 500 pixels for all products.

Fix: Go through the image dimensions of the disapproved products and replace those below the minimum with a higher-resolution image.

After the fix: crawling, review requests and monitoring

A fix doesn't show up in Merchant Center right away. According to Merchant Center Help, crawling after a fix usually takes 24 to 48 hours. If you request a review, the review can take up to 7 business days. Approved products then start showing on Google within 24 hours.

Help distinguishes between item-level and account-level issues. But it doesn't give a percentage of disapproved products that triggers an account suspension. I cover account-level action under the Misrepresentation policy separately.

You don't have to check the status after a fix by hand. Daily monitoring of disapproved products can be automated, and my public open-source monitor is on GitHub. You can hand the work over when disapprovals keep coming back after a fix or when you don't know which policy to meet.

Summary

1. For disapproved products, start on the Needs attention tab. The disapproval reason tells you whether to work on the feed, the website or the account settings.
2. Only submit manufacturer identifiers you're sure are correct. Mark goods without a GTIN, MPN and manufacturer brand with the value no in the identifier_exists attribute.
3. The website and the feed must say the same thing. Googlebot compares the price on the landing page. Automatic updates from the Automations tab align price and availability with it, as long as Google can reach the page.
4. Apparel needs gender in English and an age group from the five values Help allows.
5. Recovery times: crawling after a fix usually takes 24 to 48 hours, a review after a request up to 7 business days, and approved products show within 24 hours.
6. Account suspension has no percentage threshold in Help. Action under the Misrepresentation policy is covered in a separate article.

Every disapproval has its own rule in Help, and the fix starts with reading it.

Open the Needs attention tab, fix the reason with the most disapproved products and after 48 hours check whether their count dropped.