Google Shopping Inventory Feed Errors: How to Fix Common Rejections

You upload your product feed. A few hours later, Merchant Center shows a wall of red warnings. Products disapproved. Items pending. Errors you have never seen before. The products were live yesterday.

This is one of the most common frustrations for e-commerce sellers running Google Shopping campaigns. Feed errors block your products from appearing in Shopping results, which means lost impressions, lost clicks, and lost revenue for every hour those products stay disapproved.

This guide covers the feed errors that cause the most disapprovals, what triggers each one, and the specific steps to resolve them. If you are setting up a feed for the first time, start with the Google Shopping product feed setup guide and then come back here for troubleshooting.

Why Google Rejects Products From Your Feed

Google Merchant Center validates every product in your feed against two things: your landing page and Google's product data specification. If the data in your feed does not match what Google's crawler finds on your site, or if required attributes are missing or malformed, the product gets flagged.

The validation happens automatically every time you submit or update your feed. Google also crawls your landing pages independently to verify price, availability, and other attributes. This means a product can pass feed validation but still get disapproved later when Google's crawler finds a mismatch on your site.

"I had 300 products approved for months. Changed nothing. Woke up to 200 disapprovals. Turned out Google re-crawled my site and my caching layer was serving stale prices."

- r/PPC, Google Shopping seller, 2025

The core principle is straightforward: your feed and your website must say the same thing about every product at all times. When they diverge, disapprovals follow.

The 8 Most Common Feed Errors and How to Fix Each One

These errors account for the vast majority of product disapprovals in Google Merchant Center. They are listed roughly in order of how frequently they appear across seller accounts.

Error	What Triggers It	Fix	Re-approval Time
Price mismatch	Feed price differs from landing page price	Sync feed to live site prices. Increase update frequency.	24-72 hours
Invalid availability	Using non-standard values like "true" or "available"	Use only in_stock, out_of_stock, or preorder	24-48 hours
Missing or invalid GTIN	Wrong digit count, unregistered code, or letters in GTIN	Validate against GS1 database. Use identifier_exists=false for custom items.	24-72 hours
Image too small or invalid	Image below 100x100 px (non-apparel) or broken URL	Use images 800x800 px or larger. Verify all image URLs return 200.	24-48 hours
Missing shipping information	No shipping attribute and no account-level shipping set	Configure shipping in Merchant Center settings or add to feed	24-48 hours
Landing page not crawlable	URL returns 404, redirects to wrong domain, or blocked by robots.txt	Verify URL returns 200. Check robots.txt. Match verified domain.	48-72 hours
Mismatched brand across variants	Variants in same item_group_id have different brand values	Use consistent brand for all variants sharing a group ID	24-48 hours
Invalid sale price format	Missing currency code, sale_price higher than price, or wrong date format	Use ISO 4217 currency codes. Ensure sale_price is less than price.	24-48 hours

The sections below walk through each error in detail.

1. Price Mismatch Between Feed and Landing Page

This is the error Google treats most seriously. Your feed says a product costs $49.99. Google's crawler visits your page and sees $54.99. The product gets disapproved immediately.

Common causes:

• Feed updates on a 24-hour schedule but site prices change more frequently
• Caching layers serve stale prices to Google's crawler
• Logged-in pricing differs from anonymous visitor pricing (Google crawls as an anonymous visitor)
• Currency or tax display differences between feed and landing page
• Promotional pricing applied on-site but not reflected in the feed

To fix it: increase your feed update frequency to at least every 6 hours if you have dynamic pricing. Enable automatic item updates in Merchant Center (under Settings), which allows Google to use the crawled price as a temporary override instead of disapproving the product outright. Ensure your site serves the same price to all visitors, including bots, without requiring login or cookies.

2. Invalid Availability Values

Google only accepts three availability values: in_stock, out_of_stock, and preorder. Sellers often submit values like "true," "false," "available," "yes," "1," or "limited stock." All of these trigger a disapproval.

Map your internal availability statuses to Google's three accepted values before they enter the feed. If you use a feed management tool, create a static mapping rule that converts your values to the Google format.

3. Missing or Invalid GTIN

Google uses GTINs (Global Trade Item Numbers) to match your products to its global product catalog. When the GTIN is wrong, Google cannot verify that your product is what you say it is.

GTIN problems include:

• Wrong digit count (valid GTINs are 8, 12, 13, or 14 digits)
• Letters or special characters in the GTIN field
• Internal barcodes or warehouse codes submitted as GTINs
• GTINs that do not exist in the GS1 registry
• Using the same GTIN for multiple distinct products

Verify every GTIN against the GS1 check digit calculator before including it in your feed. For products that genuinely do not have a manufacturer-assigned GTIN (handmade goods, custom items, unbranded parts), set identifier_exists to false. Do not fabricate GTINs.

4. Image Violations

Google has strict image requirements. The most common violations are:

• Images smaller than the minimum size (100x100 pixels for most products, 250x250 for apparel)
• Placeholder or generic stock images
• Images with promotional text, watermarks, or overlays
• Broken image URLs that return 404 or redirect errors
• Images that show a different product than the listing

Use product photos at least 800x800 pixels. Google recommends 1200x1200 or larger for best results in Shopping ads. Verify every image URL in your feed returns a 200 status code. If you manage a large catalog, run a weekly automated check on image URLs to catch broken links before Google does.

"Half my feed got rejected because the CDN changed URL structure and all my image links broke overnight. 400 products, gone from Shopping in one crawl cycle."

- r/ecommerce, online store owner, 2026

5. Missing Shipping and Tax Information

Google requires shipping cost information for every product. You can provide it at the account level in Merchant Center settings, or at the product level in your feed. If neither exists, the product gets disapproved.

For US sellers, tax information must be configured in Merchant Center under Tax settings, not in the feed. For international sellers, check the requirements for your target country, as tax handling rules vary.

6. Landing Page and Domain Issues

Every product URL in your feed must point to a page on a domain you have verified and claimed in Merchant Center. The page must be publicly accessible, return a 200 status code, and display the product information that matches your feed.

Common domain-related disapprovals happen when:

• The feed URL redirects to a different domain than the one verified in Merchant Center
• Pages require authentication or geolocation-based redirects that block Google's crawler
• SSL certificates expire, causing HTTPS URLs to fail
• Staging URLs accidentally make it into the production feed

Feed Errors That Silently Kill Performance

Not all feed issues trigger hard disapprovals. Some create warnings that reduce your product's visibility without removing it entirely. These are harder to catch because your products still appear in Merchant Center as "active," but they show up in fewer searches or get lower placement.

"My products were technically approved, but impressions dropped 70%. Turned out I had 'limited performance' warnings on 80% of my catalog because of missing optional attributes like color and size."

- r/GoogleShopping, e-commerce seller, 2025

Warning-level issues that hurt performance include:

• Missing optional attributes (color, size, material, pattern, age_group, gender) for categories where Google expects them
• Generic or duplicate titles across similar products
• Thin product descriptions under 50 characters
• Missing google_product_category or incorrect category mapping
• Low-quality images that meet minimum size but lack detail

Check the Diagnostics tab in Merchant Center regularly. Filter by "warnings" and "limited performance" items. These products are approved but underperforming, and fixing the warnings often produces a measurable increase in impressions and clicks within days.

A Systematic Process for Cleaning Up Feed Errors

If you have dozens or hundreds of disapproved products, working through them one at a time is not practical. Use this process to resolve errors in batches.

Step 1: Export your Merchant Center diagnostics. Go to Products, then Diagnostics, and download the full list of issues. Group errors by type rather than by product. This tells you whether you have a systemic problem (like all products missing shipping) or isolated issues (one bad GTIN).

Step 2: Fix systemic issues first. If 200 products have the same error, the fix is usually one change: a feed rule, an account setting, or a mapping correction in your feed tool. Systemic fixes give you the highest re-approval rate per hour of work.

Step 3: Validate before resubmitting. Google's feed rules documentation explains how to use test feeds and preview tools to check your data before it goes live. Catching errors in preview saves you the 24-72 hour re-approval wait.

Step 4: Set up monitoring. Configure alerts in Merchant Center for approval rates that drop below 95% or price errors that exceed 1% of your catalog. Early detection prevents small issues from compounding into account-level problems.

If your feed issues trace back to inconsistent product data across sales channels, the root cause is usually upstream from Google. A structured product feed management process that normalizes data before it reaches any channel prevents most of these errors from occurring in the first place.

Preventing Feed Errors Before They Happen

The most efficient way to deal with feed errors is to not have them. These practices keep disapproval rates low:

Update your feed frequently. If you change prices, inventory, or product details on your site, your feed should reflect those changes within hours, not days. Sellers using real-time or near-real-time feed updates see significantly fewer price and availability mismatches.

Enable automatic item updates. This Merchant Center feature allows Google to temporarily adjust your feed data based on what it crawls on your landing pages. It is not a substitute for accurate feeds, but it catches mismatches before they turn into disapprovals.

Validate GTINs at the source. Before any product enters your catalog, verify its GTIN against the GS1 database. Build this check into your product onboarding workflow so bad identifiers never reach your feed.

Test every feed change before publishing. Use Merchant Center's feed preview feature to review how Google interprets your data. This is especially important after changing feed formats, switching feed tools, or modifying product attributes in bulk.

Monitor image URLs independently. Broken images are one of the most common feed errors because they happen outside your feed. CDN changes, domain migrations, and expired image hosting all break image links without touching your feed data. Run a weekly crawl of your image URLs to catch failures early.

Your product feed is the foundation that every channel depends on. When feed data is clean and consistent at the source, errors at Google (and every other marketplace) drop dramatically. If you are managing feeds across multiple channels, the role of product feeds in discoverability goes well beyond Google Shopping.

When Feed Errors Signal a Bigger Data Problem

Recurring feed errors are often a symptom rather than a root cause. If you find yourself fixing the same types of disapprovals every week, the problem is usually in how product data flows through your systems.

Common upstream causes:

• Product information lives in multiple places (your store platform, a spreadsheet, a PIM, and the feed tool) with no single source of truth
• Price changes happen on the storefront but do not propagate to the feed automatically
• New products get added to the store without the required Google attributes (GTIN, brand, google_product_category)
• Inventory status changes on one channel but the feed for another channel still shows the old status

The pattern is the same in each case: data originates in one system, needs to reach another system, and something breaks in the middle. Solving this at the feed level works for a while, but the long-term fix is a centralized product data layer that feeds every channel from the same source.

Google Merchant Center is just one of many places where bad product data surfaces. The same data quality issues that cause Shopping feed errors also cause listing rejections on Amazon, sync failures across marketplaces, and inconsistent customer experiences across channels. Fixing the data once, at the source, fixes it everywhere.