Google Merchant Center Feed Disapprovals: How to Fix Price, Availability, and Data Quality Issues

Feed disapprovals are the most solvable category of Google Merchant Center problems. Unlike account suspensions — which involve subjective human review and complex appeal processes — feed disapprovals have specific, identifiable causes and clear fixes. But 'fixable' doesn't mean 'trivial.' Widespread feed disapprovals can escalate to account suspension, and fixing them systematically requires understanding how Google's feed validation works.

Feed Disapprovals vs. Account Suspension

Feed disapprovals are product-level issues. When a product is disapproved, it's removed from Shopping ads but doesn't affect your other products or your account status. Account suspension affects all products and requires a formal appeal. The escalation path: if a large percentage of your products are disapproved — typically above 20-30% of your catalog — or if disapprovals are concentrated in a category that suggests a systemic practice issue, Google may escalate from product-level disapproval to account-level suspension. This means fixing feed issues promptly isn't just about those specific products — it's about preventing the account from being reviewed holistically.

The Three Categories of Feed Issues

• Data quality issues — required attributes are missing, malformed, or use incorrect values. These are purely technical and fixable entirely within your feed.
• Policy violations — product content (title, description, images) violates Google's Shopping Ads content policies. Fixing these requires changing either the feed data or the underlying product page.
• Landing page mismatches — the feed data differs from what Google finds on the landing page. Fixing these requires synchronizing your feed with your website.

Price Mismatch: The Most Common Feed Disapproval

Price mismatch means the price in your feed doesn't match the price Google's crawler finds on the product's landing page. This is detected automatically on every crawl. The threshold is extremely tight — even a $0.01 difference triggers disapproval.

Why price mismatches happen

• Feed is cached: your feed is fetched once a day (or less frequently), but your website prices change in real time. The feed has yesterday's price and the website has today's.
• Sale price expired: you ran a sale with a sale_price attribute, the sale ended, but the website reverted to the regular price while the feed still shows the sale price.
• Tax inclusion difference: your feed sends prices exclusive of tax, but your website displays prices inclusive of tax for the customer's country (or vice versa).
• Currency issue: your feed sends prices in USD, but your website shows local currency prices for some visitors.
• Rounding difference: your website shows $19.99 and your feed sends $20.00 due to a rounding rule in your feed generation logic.

How to fix price mismatches

1. After any price change on your website, trigger a manual feed re-fetch in GMC: Products > Feeds > [your feed] > Fetch now. Don't wait for the next scheduled fetch.
2. For sales: use the sale_price attribute and the sale_price_effective_date attribute with start and end dates. When the sale ends, the feed automatically reverts to the regular price_attribute value without requiring a re-fetch.
3. For tax: in your GMC account settings, go to Tax and configure whether your prices include or exclude tax for each country. This must match your website's price display.
4. For currency: ensure your feed sends prices in your store's base currency. If you use multi-currency on your website, use the feedLabel attribute and create separate feeds per market with the correct currency for each.

Availability Mismatch

Availability mismatch means your feed says a product is 'in_stock' but the landing page shows it as out of stock (or vice versa). This is especially common during flash sales, product launches, and end-of-season inventory clearances.

The availability attributes

How to fix availability mismatches

• Set your feed to re-fetch at least daily. For high-turnover inventory, use the Content API for real-time synchronization.
• Add availability_date to all preorder products. This attribute signals to Google that the unavailability is temporary and expected.
• If you cannot sync in real time, mark items as out_of_stock earlier than they actually run out — before you sell the last unit — to prevent the mismatch window.
• Use Google's automatic item updates feature (available in GMC settings) to let Google's crawler automatically update availability values based on structured data on your landing pages.

Missing Required Attributes

Every product in your GMC feed needs a minimum set of required attributes. Missing any of these will cause the product to be disapproved.

Title Optimization That Avoids Disapprovals

Product titles are one of the most common sources of policy violations in feeds. Google has clear rules: no promotional text, no ALL CAPS (for more than one word), no special characters (!, *, $) used as emphasis, and no generic phrases like 'click here,' 'on sale,' or 'limited time.' The optimal title structure is: Brand + Product Type + Key Attributes (size, color, material, spec).

• Good: 'Nike Air Max 270 Men's Running Shoes Size 10 Black/White'
• Bad: 'BEST DEAL!! Nike Shoes - Buy Now - LIMITED TIME OFFER'
• Good: 'Casio G-Shock GA-2100 Solar Watch Black Resin Band'
• Bad: 'Casio Watch #1 Rated!! Guaranteed Quality - Fast Shipping'

Image Issues That Cause Disapprovals

• Text overlays or watermarks on product images — Google's image classifier detects these and disapproves the product.
• Placeholder images or stock images showing a different product than described.
• Images below the minimum resolution (100x100px, but Google strongly prefers 800x800px or higher).
• For apparel items: images must show the product on a model or on a clean white background. Flat lay images on non-white backgrounds cause higher disapproval rates for apparel.
• Wrong aspect ratio for the product type: apparel prefers 4:3 or square; for most products, square or 4:3 is preferred.

Landing Page Issues from Google's Crawler Perspective

Google's crawler retrieves product landing pages to verify feed data. From the crawler's perspective, your page needs to:

• Load within 10 seconds. Pages that time out are marked as unavailable. Use PageSpeed Insights to check your product page load time.
• Show the same price as the feed. The crawler compares structured data (schema.org/Product markup) and visible page price.
• Be indexable — no noindex meta tag, no 'Disallow: /' for the product URL in robots.txt.
• Not redirect to a different URL. If the feed URL redirects (even a trailing slash redirect), the crawler may see a different page than intended.
• Show the same product as the feed title/description. A landing page that shows multiple products or a category page instead of a specific product will cause disapprovals.

Using the Diagnostics Tab to Prioritize Fixes

The Diagnostics tab in GMC (Products > Diagnostics) shows all your disapprovals grouped by issue type, with the count of affected products for each issue. Always fix in this order: (1) issues affecting the most products first — these have the biggest impact on your impression share. (2) Price and availability mismatches second — these are often time-sensitive and can escalate to account review. (3) Missing required attributes third — these are easy to fix in bulk via a supplemental feed. (4) Policy violations last — these often require manual product review and may involve content decisions.

Feed Refresh Strategy

Set your primary feed to re-fetch daily at minimum. If your store has frequent price changes or inventory fluctuations, use the Google Content API for near-real-time updates. For quick fixes to specific products without re-uploading the entire feed, use a supplemental feed: a smaller feed file that contains only the products and attributes you want to update. Supplemental feed attributes override primary feed attributes for matching product IDs. This is the fastest way to fix a batch of disapprovals for a specific attribute.