Most product disapprovals in Google Merchant Center come from three places: the data in the feed is missing or wrong (price, stock, GTIN, image), the feed and the product page do not match (a price or stock mismatch), or the product or the account runs into a policy. The first step of the fix is to classify the problem on the product issues screen in Merchant Center as "a single product, the whole feed, or the account"; the second step is to fix the problem permanently where the data comes from, that is, in your store platform or your feed rules, instead of fixing it by hand in Merchant Center.

In this guide we group the most common causes and explain what you need to check for each. Google's policy texts and field requirements change from time to time; for the definitive rule, always refer to the current product data specification in the Merchant Center Help Center.

First classify the problem: product, feed or account

In Merchant Center a product's status usually falls under one of these three headings:

  • Disapproved: The product is not shown in ads. Usually a required field is missing, a value is invalid, or there is a policy violation.
  • Limited: The product can be shown, but it does not appear on some surfaces or in some countries, or its performance is restricted. "Recommended" fields such as a missing GTIN often put products here.
  • Pending: Google has not reviewed the product yet; this is normal for newly added or substantially changed products.

If the same issue appears on hundreds of products, the cause is almost always a single source: a missing field in one category, a wrong currency format, or an image URL that broke across the whole site. So before fixing products one by one, group the issues by issue type and start with the largest group.

Price and stock mismatch

This is the most common problem and the easiest to overlook. Google compares the price and stock status in the feed with the information on the product page. When it finds a difference, it may disapprove the product or use the value it crawled itself.

Common causes:

  • The price changes on the site during the day while the feed is updated once a day.
  • A promotional price applied on the site is not reflected in the feed (or the other way round).
  • The price on the product page is loaded later with JavaScript, and the initial HTML Google sees has a different price.
  • For products with variants, the variant link in the feed opens a different variant (and price) on the page.
  • An out-of-stock product stays as in_stock in the feed.

Check: Open the links of a few disapproved products in a private window and compare the price and stock information on the page with the price, sale_price and availability values in the feed. For discounted products, make sure the price and sale_price fields are used correctly; we covered this in detail in the guide to reflecting discounted prices in the feed.

Missing or incorrect product identifiers (GTIN, brand, MPN)

For products that have a manufacturer-assigned GTIN (barcode), Google asks for this value. A missing GTIN usually does not disapprove the product outright, but it puts it in the "limited" state and reduces visibility. A wrong GTIN, or one that belongs to another product, is a more serious problem.

  • For products that have a barcode, send the real barcode; do not write an internal stock code into the GTIN field.
  • For products you manufacture yourself that have no barcode, declaring the identifier_exists field as no is a common approach.
  • Do not leave the brand field empty; use a consistent value for unbranded products.

Image problems

Google Shopping wants the product to be clearly visible in images. Common causes of disapprovals and warnings:

  • The image URL does not open, redirects, or is a placeholder image.
  • The image is very small or low resolution.
  • The main image contains promotional text, a watermark, a discount badge or a button. Google does not allow promotional overlays on the image_link image.

The last point is especially important: while a discount badge works very well in Meta catalog ads, putting the same image in a Google feed can cause problems. We explained which channels you can use badged images on in the guide to adding discount badges to ad images.

Landing page and crawling problems

If Google cannot access your product page, it cannot approve the product.

  • The product page may return a 404, redirect to the home page, or require a login.
  • robots.txt may be blocking product pages or the image folder.
  • The link field in the feed may point to a mobile or old domain.
  • The site loads very slowly, or there is a security layer blocking Googlebot.

Required and category-specific fields

Some fields are required for every product (such as id, title, description, link, image_link, price, availability). In categories such as apparel and shoes, additional fields such as color, size, gender and age_group are expected in certain countries; for products with variants these fields also serve to tell the variants apart.

Points to watch with variants:

  • The sizes of the same product should share the same item_group_id value.
  • Each variant should have its own id value, and it should not change over time.
  • Variants should differ from each other by at least one attribute (size, color).

Policy and account-level issues

Even if the product data is flawless, an account-level issue can stop all products. Warnings in the "misrepresentation" class usually relate to trust information on the site: contact details, the return and exchange policy, delivery information and the trustworthiness of the checkout page. In addition, some product groups (such as health products and alcohol) are subject to restricted or prohibited content policies. For this kind of issue it is the site and account settings that need fixing, not the feed; after the fix, a review can be requested through Merchant Center.

How to prevent issues permanently

Fixing products one by one in Merchant Center works in the short term, but the same error comes back with the next feed update. For a permanent fix:

  1. Fix the data at its source. If barcode, brand and category information is correct in your store platform, it goes into the feed correctly too.
  2. Update the feed frequently. The more often price and stock sync, the narrower the mismatch window.
  3. Do not let the problem product into the feed at all. Excluding products that are out of stock, have no image or have a zero price with a rule is cleaner than waiting for a disapproval.
  4. Do the category mapping once. Mapping your store categories to the Google product taxonomy helps category-specific fields get filled in correctly.

Where HexFeed helps in this process

Once the Google Merchant Center connection is set up in the HexFeed panel, the Merchant Center report shows the approval status of products (disapproved, limited, pending) and the most common issues on a single screen; it has search, a category filter and export to Excel. Each feed's quality score also lists issues such as a missing GTIN or a short description, with example products.

On the prevention side, you can use feed rules to keep products out of the feed by stock, price, category or size availability, map your store categories to the Google taxonomy, and bind fields such as gender, age group and material to your product tags or to a fixed value. For details see the feed filtering page; for setup on your platform, see the Google Shopping with T-Soft and Google Shopping with Ticimax pages.

Checklist

  • I grouped the issues by issue type and started with the largest group.
  • For disapproved products, I compared the price and stock on the page with the values in the feed.
  • For discounted products, price goes out as the list price and sale_price as the current price.
  • A real GTIN is sent for products that have a barcode; identifier_exists is correct for products without one.
  • image_link images contain no promotional text, badge or watermark.
  • Product links open, and robots.txt does not block product pages or images.
  • Variants are under the same item_group_id, and each has a permanent id value.
  • Contact, return and delivery information is clearly stated on the site.
  • Products that are out of stock or have no image never enter the feed.