Top 10 GMC Disapproval Reasons (2026)

The top GMC disapproval reasons are the recurring policy and data failures that Google's automated checks flag most often. Across the scans we have run on more than 100 ecommerce stores, these ten causes are the ones that show up again and again. Dozens of other long-tail issues exist, but they only matter in niche categories.

This article covers those 10 causes, ordered as a general guide by how often we see them, names the fix path for each, and gives realistic time-to-reapproval estimates. Use it as a triage list: when your store has multiple disapprovals at once, work top-down by impact, not by what looks easiest to fix.

How we chose these 10

The ordering below draws on FeedShield's audit history:

• 306 scans run across more than 100 ecommerce stores between April and September 2026
• Roughly 168,000 individual check results logged across those scans
• Stores spanning fashion, electronics, jewelry, supplements, home goods, and B2B

We don't publish exact failure percentages or per-issue counts from this period. The scan engine that ran through mid-2026 had a high false-positive rate, which is why we rebuilt it, and we would rather say that plainly than hand you a precise-looking number we can't stand behind. The top 10 below are ordered, as a general guide, by how often our team saw each issue, not by a percentage breakdown.

1. Missing GTIN in structured data

One of the most common audit failures. GTIN (Global Trade Item Number) is the 8-14 digit identifier that maps a product to Google's knowledge graph. Without it, Google cannot confirm what the product is, and impressions drop noticeably even when the product is technically approved.

Why it happens so often: Shopify hides the Barcode field by default in the product editor; WooCommerce requires a plugin to expose GTIN; bulk imports frequently miss the GTIN column.

Fix: populate GTIN in both the feed and Product JSON-LD on the landing page. For Shopify, use the Barcode field. For WooCommerce, use the Google Listings & Ads plugin's GTIN metafield. For products genuinely without a GTIN (handmade, private-label, custom), set identifier_exists=false.

Time to reapproval: 24 hours after feed sync.

2. Product JSON-LD missing or invalid

Even with a clean feed, Google cross-checks against page-level structured data. Missing or invalid Product JSON-LD triggers "landing page requirements" disapprovals. Common patterns: theme bug, dual-emit conflict from an SEO plugin, JSON-LD that validates but is missing required offers properties.

Fix: add schema.org/Product [4] to every product page with at minimum: name, image, brand, offers.price, offers.priceCurrency, offers.availability. Validate with Google's Rich Results Test. Resolve duplicate schema blocks by disabling the redundant plugin.

Time to reapproval: A few days (requires page recrawl).

3. Brand missing from Product schema

Google increasingly weights the brand attribute for Shopping eligibility and ranking. Missing brand on a branded product reads as either an error or a misrepresentation signal. The disapproval message is often vague: "missing required attribute," with no explicit brand mention.

Fix: populate the brand attribute in both the feed and Product JSON-LD. For Shopify, use the Vendor field. For WooCommerce, use a Brand taxonomy plugin. For your own private-label products, set brand to your business name as it appears in Merchant Center.

Time to reapproval: 24-48 hours.

4. Performance Max landing page not ready

PMax pulls landing-page signals harder than standard Shopping. The required signals: mobile speed (LCP under 2.5s), structured data, return policy text, return-window declaration, contact info accessible from the product page. A page that passes standard Shopping requirements can still fail PMax checks.

Fix: run each affected URL through PageSpeed Insights. Compress hero images, defer non-critical JS, add return-policy text or structured data to every product page. Many Shopify themes hide return-window data in the footer alone, which is not sufficient.

Time to reapproval: Longer than a standard fix (PMax-specific re-review cycle).

5. Business name inconsistency across the site

Your header says "Acme Co.", your footer says "Acme Ltd.", your Privacy page says "Acme Trading". Google's crawler extracts business names from headers, footers, contact, About, and policy pages, and inconsistencies read as fraud signals. This usually causes account-level scrutiny rather than per-SKU disapproval, but it does also trigger product-level PMax disapprovals.

Fix: standardize the business name in one canonical form across every page. Match the Merchant Center business info exactly. Include legal entity (Ltd., LLC, Inc.) consistently in the footer.

Time to reapproval: Considerably longer, on top of Google's review window (site-wide change + manual re-review).

6. Product image count below 3

Google recommends a minimum of 3 distinct product images per SKU [5]. Single-image products can still serve, but reduced CTR and increased disapproval risk in apparel, electronics, furniture. Shopify themes often hide gallery image slots until products have multiple images uploaded.

Fix: shoot or commission 3 photos per SKU: front, alternate angle, lifestyle or detail. Upload to the product gallery. The first image becomes the main Shopping image.

Time to reapproval: 24-48 hours after feed re-sync.

7. Category-specific attributes missing

Each Google product category has its own required attributes. Electronics: color, size, condition. Apparel: color, size, gender, age_group. Jewelry: material. Supplements: nutrient_info, energy. Missing the required attributes for the SKU's category triggers a category-specific disapproval.

Fix: map each SKU to the correct google_product_category [1], then populate the required attributes documented for that category. Most platforms support category-specific custom fields; use them.

Time to reapproval: 24-72 hours.

8. JavaScript-only price rendering

A recurring share of the stores we scan rely on client-side JS to render product prices. Google's crawler executes JS in some contexts but not all. When the crawler reads the page without JS execution, the price is missing or stale, and a "price mismatch" or "missing price" disapproval fires.

Fix: render the canonical price in server-side HTML or in Product JSON-LD. Use Google's URL Inspection tool to fetch the page as Googlebot and confirm the price is in the raw HTML. Multi-currency Shopify apps are a common offender.

Time to reapproval: A few days.

9. Product not available for purchase

The crawler tries to load the landing page and either gets a 404, a redirect to a category page, or a checkout flow that fails. Common causes: SKU was deleted but the URL is still in the feed; product is password-protected; checkout requires a specific country/region cookie.

Fix: verify the landing-page URL returns 200, the Add-to-Cart button works for a logged-out user from the target country, and the checkout completes with a test card. For out-of-stock items, set availability=out_of_stock rather than removing the URL.

Time to reapproval: 24 hours after the URL works again.

10. Template privacy policy

A lot of the stores we scan use unmodified privacy policies from free generators. Google's reviewers spot template language instantly. Template policies rarely cause direct disapprovals, but they contribute to low-trust classifications that cascade into PMax disapprovals and account-level review.

Fix: customize the privacy policy with your real business name, address, data-collection practices, and contact email at your domain. Date the policy. Customization does not need to be elaborate; it needs to be specific.

Time to reapproval: Considerably longer, on top of Google's review window (manual policy review).

How to use this ranking

When your store has multiple disapprovals at once, prioritize by impact (affected SKU count) × ease (time to fix), not by reason number on this list. A single GTIN fix that re-enables 200 SKUs beats five image-count fixes that re-enable 20 each.

Practical workflow:

1. Open GMC → Diagnostics. Sort issues by affected-SKU count.
2. Map each issue to the matching reason on this list to get fix path + ETA.
3. Batch all fixes into a single push (not incremental), since each push triggers a fresh review cycle.
4. Wait the longest fix's ETA (don't request review prematurely).
5. Request review on each affected category via the Diagnostics page.

The stores that get back online fastest treat disapprovals as a portfolio problem, not 10 individual problems. Find the structural cause (theme, app, bulk import) and fixing one thing resolves many disapprovals at once.

Bottom line

Disapprovals feel chaotic, but the pattern is not random. These 10 reasons are the ones we see over and over across FeedShield's audit history, and GTIN, JSON-LD, and Brand are among the most common. Audit your store against this ranking, batch the fixes, give Google one re-review cycle, and most disapprovals on this list clear within the ETA listed for that fix.