Why Google Merchant Center Disapproved Your Products (2026)

A Google Merchant Center disapproval is a per-product enforcement action that removes a specific SKU from Shopping ads and free listings while leaving the rest of the catalog running. It happens when Google's automated checks or a human reviewer flag a product as violating one of the data, policy, or sales-experience requirements that govern Shopping. Disapprovals are reversible: fix the underlying issue and the product re-approves on the next crawl or feed sync.

This guide ranks the 12 root causes we see most often across 87,976 audit checks, shows where to find the disapproval reason inside GMC, gives the fix path for each cause, and explains how to keep disapprovals from coming back.

Disapproval vs warning vs suspension

Three enforcement levels exist in GMC, in order of severity:

This guide focuses on disapprovals. For suspensions, see the misrepresentation suspension recovery playbook, which covers the harshest enforcement category.

The 12 root causes, ranked

Across the 9,515 failed audit checks in our dataset, disapprovals cluster around twelve recurring causes. They are not equal in frequency or impact, so we have ranked them by how often we see them.

1. Missing or invalid GTIN in feed or structured data

The top failure pattern by frequency, with 874 occurrences in our audit history. GTIN (Global Trade Item Number) is the 8 to 14 digit identifier that maps a product to Google's product knowledge graph. Without it, Google cannot confirm the product is what you say it is, which leads to either a hard disapproval ("missing identifier") or significantly reduced impressions.

How to fix: add the UPC, EAN, or ISBN barcode to every branded product in your feed and product structured data. For private-label or custom items that have no GTIN, set the identifier_exists attribute to false. For Shopify, the value goes in the Barcode field on each product. For WooCommerce, use the official Google Listings & Ads plugin and populate the GTIN under the product's marketing tab.

2. Product schema missing or invalid

867 stores in our data have missing or broken Product JSON-LD on their landing pages. Even when the feed is correct, Google cross-checks against the page schema. A mismatch or absence triggers a "landing page requirements" disapproval.

How to fix: add schema.org/Product JSON-LD to every product page with at minimum: name, image, brand, offers.price, offers.priceCurrency, offers.availability. Validate every URL with Google's Rich Results Test [6]. For Shopify, most themes emit valid schema by default. For WooCommerce, Rank Math or Yoast handles it. For custom builds, you write it yourself.

3. Brand attribute missing from Product schema

815 stores fail this check. Google increasingly weights the brand attribute in Shopping ranking, and missing brand for a product that has one looks like either an error or a misrepresentation signal.

How to fix: populate the brand attribute in both the feed and the page's Product JSON-LD. For Shopify, this is the Vendor field. For WooCommerce, use a Brand taxonomy plugin. For products you genuinely manufacture, set the brand to your own business name as it appears in Merchant Center.

4. Performance Max landing page not ready

730 product pages fail at least one of Google's PMax landing-page readiness checks: mobile speed, structured data, return policy, return-window declaration, contact info. PMax specifically pulls landing-page signals harder than standard Shopping does.

How to fix: run each affected URL through PageSpeed Insights. Compress hero images, defer non-critical JavaScript, and ensure Largest Contentful Paint stays below 2.5 seconds on mobile. Add return-policy and return-window data to every product page either as structured data or as visible text inside the main content.

5. Business name inconsistency across the site

667 stores show inconsistent business names across header, footer, contact page, and policy pages. While this is more often a suspension trigger than a per-SKU disapproval, it does also cause "business identity mismatch" warnings that escalate to product-level disapprovals on PMax campaigns.

How to fix: standardize the business name in one canonical form across every page (header, footer, About, Contact, Privacy, Terms, Returns, Shipping) and match it exactly to the business info in Merchant Center.

6. Not enough product images

626 product pages we have audited fall short of Google's recommended minimum of 3 distinct product images. Single-image SKUs can still serve, but they show in Shopping with reduced CTR and increased disapproval risk in categories where Google expects multiple angles (apparel, electronics, furniture).

How to fix: shoot or commission at least 3 product photos per SKU: front, alternate angle, and either a lifestyle or detail shot. Upload them to the product as gallery images. The first image becomes the main image in feed and Shopping listings.

7. Category-specific attributes missing

375 product pages we audited are missing required attributes for their Google product category. Electronics needs color, size, condition; apparel needs color, size, gender, age_group; jewelry needs material; supplements need nutrient_info and energy.

How to fix: identify the Google product category for each SKU (the google_product_category field), then add the required attributes documented for that category in the product data specification [1].

8. JavaScript-only price rendering

361 stores in our data rely on JavaScript to render product prices on the page. Google's crawler executes JS in some contexts but not all; when the crawler reads the page without executing JS, the price is missing, and a "price mismatch" or "missing price" disapproval fires.

How to fix: render the canonical price in server-side HTML or in JSON-LD structured data. Use Google's URL Inspection tool to fetch the page as Googlebot and confirm the price is present in the raw HTML.

9. Product no longer available for purchase

307 disapprovals in our data are for "product not available for purchase." This happens when Google's crawler tries to load the landing page and either gets a 404, a 410, a redirect to a category page, or a checkout flow that does not accept payment.

How to fix: verify the landing-page URL returns 200, the Add-to-Cart button works for a logged-out user, and the checkout completes successfully with a test card. For out-of-stock items, set availability to out_of_stock in the feed rather than removing the URL.

10. Privacy policy looks like a template

262 stores use unmodified template privacy policies. While this rarely causes a direct disapproval, it stacks with other signals and contributes to "low trust" classifications that lead to PMax landing-page disapprovals and account-level review escalation.

How to fix: customize the privacy policy with your real business name, address, data-collection list, and a contact email at your domain. Date the policy. The customization does not need to be elaborate; it needs to be specific to your business.

11. Misleading product claims

200 disapprovals in our data are flagged for misleading content. The most common offenders: weight-loss promises without medical disclaimers, before-and-after photos with no time disclosure, "100% money back guarantee" without a written refund policy, "FDA approved" claims on non-FDA-approved categories.

How to fix: remove unverifiable claims from product titles, descriptions, and landing-page content. Where a claim is true and necessary, attach evidence (study citation, FDA filing number, refund policy URL).

12. Image too small or low quality

165 product images we audited fail Google's image requirements. The minimum is 100x100 pixels for general products and 250x250 for apparel, but the practical minimum that actually performs in Shopping is 800x800. Below that, CTR drops 30-50% relative to peers.

How to fix: upload images at 1200x1200 or higher. Compress them as WebP or high-quality JPG to keep file size below 1MB. Use a plain white background where the category prefers it. Avoid watermarks, promotional text overlays, and logos in the main product image.

Where to find the disapproval reason in GMC

Google surfaces disapprovals in four places, in roughly this order of usefulness:

1. Diagnostics page

Go to Merchant Center → Products → Diagnostics. This page lists every active issue grouped by severity and category, with the affected SKU count, the policy name, and a link to Google's documentation. Start here.

2. Per-product Issues column

Merchant Center → Products → All products. Add the "Issues" column to the table view. Each affected SKU shows the issue name inline. Useful when you need to filter or export by issue type.

3. Account Issues email

When a new issue type appears at scale, Google emails the Merchant Center admin. The email includes the issue name, the affected SKU count, and a policy link. Do not delete these emails; they are useful for understanding when Google's enforcement changed.

4. Diagnostics API

For agencies managing dozens of accounts, the Diagnostics API returns the same data programmatically. Pull it weekly into a tool like FeedShield that aggregates issues across all clients into a single dashboard.

Fix paths for each disapproval type

The 12 root causes group into four fix-path categories:

How long does the fix take to take effect

The timeline depends on which surface needs to re-fetch the corrected data:

1. Feed-only fixes (GTIN, brand, category attributes) re-process on the next feed sync. For automatic feeds, that is typically every 24 hours. For Shopify/WooCommerce app integrations, every 12-30 minutes. You can also force a manual fetch from Merchant Center.
2. Page-only fixes (schema, price rendering, image upgrades) re-process on the next Google crawl. Crawl frequency varies from 6 hours to 7 days depending on the site's authority. You can request a faster recrawl via the Diagnostics page's Inspect URL action or via Search Console.
3. Site-wide fixes (business name, policies, contact info) require Google's policy reviewer to look at the site again. This is a manual process and takes 3-14 days.
4. Content / restricted-product fixes almost always require human re-review and take 7-21 days.

If a product is still disapproved 7 days after a confirmed fix, open the Diagnostics page, find the SKU, and click "Request review." Do not skip this step; the auto-recheck on some categories does not happen without an explicit request.

When a disapproval becomes a suspension

Disapprovals escalate to account-level suspensions when:

• More than ~20% of the catalog is disapproved for the same root cause
• The same SKU is disapproved 3+ times for the same policy in a 30-day window
• The disapproval reason is misrepresentation, restricted product, or prohibited content (these are high-severity policies that escalate from the first violation)
• A pattern of disapprovals across multiple categories suggests systematic policy avoidance

The single best way to avoid escalation is to keep the disapproval rate below 5% of the active catalog and to address misrepresentation flags within 7 days.

How to prevent disapprovals from coming back

Most disapprovals come back because the underlying cause was not fixed at the root. Common patterns we see:

1. Theme updates revert schema fixes. Whenever a Shopify theme update lands, your custom Product schema may be replaced by the theme's default. Lock the schema in a separate template file or use a schema-management app.
2. App updates re-introduce fake urgency. Countdown timers, "X people viewing" widgets, and fake stock messages get re-added by app updates. Audit your installed apps quarterly.
3. Currency apps break price rendering. Multi-currency Shopify apps frequently break the canonical price in JSON-LD. Test product pages after every currency-app install or update.
4. Bulk-edit imports replace attributes. A bulk CSV import that does not include the GTIN column will wipe GTINs on every imported product. Always export, edit, then re-import with the full column set.
5. Inventory feeds desync. When Shopify or your warehouse system gets disconnected from Merchant Center, the feed serves stale availability and price data. Set up monitoring on feed sync timestamps.

The single best preventive measure is running a weekly automated audit that flags new issues before Google's review cycle catches them. A compliance score that drops 10+ points week-over-week is a leading indicator of pending disapprovals.

What to do when the disapproval reason is wrong

Google's automated checks are not perfect. We have seen disapprovals fire on products that genuinely passed the policy, particularly in categories where Google's classifiers misread niche product types (handmade jewelry flagged as restricted gemstones, organic skincare flagged as supplements, etc.).

The escalation path when the disapproval is genuinely wrong:

1. Document the issue. Screenshot the disapproval reason, the policy page Google links to, and the relevant product page content that contradicts the flag.
2. Submit a re-review via the Diagnostics page with a short, specific note explaining why the product complies. Cite the policy section by name.
3. If the re-review fails, escalate via the Merchant Center "Get help" form. Include the documentation from step 1. This routes to a human reviewer.
4. If you advertise at scale ($1,000+/month on Google Ads), open a support case via your Google Ads rep. They can escalate to a Merchant Center policy specialist.

Bottom line

Disapprovals look chaotic when you first see them, but they cluster around twelve recurring causes that account for ~90% of every disapproved product we have seen. Find the right cause via Diagnostics, apply the correct fix path, give Google time to re-crawl, and the disapproval re-approves. If the same disapproval keeps coming back, the issue is structural (theme, app, feed sync) rather than per-SKU, and that is where to focus the next round of fixes.