Google Merchant Center Feed Data Quality Issues: Complete Fix Guide

What are feed data quality issues?

Feed data quality issues are different from policy violations. A policy violation means something about what you are selling or how you represent it breaks Google's rules. A data quality issue means your product data is incomplete, incorrect, or inconsistent with what appears on your website.

The practical difference matters: policy violations can suspend your entire account. Data quality issues disapprove individual products. Your account stays active, but affected products stop showing in Shopping results until the data is corrected.

The distinction also affects where you look for problems. Policy violations appear under Account issues in the Merchant Center dashboard. Data quality issues appear under Products > Diagnostics and are tied to specific attributes or feed-level problems.

The five issues below account for the bulk of disapproved products across Merchant Center accounts. Most of them are fixable in a single feed update.

The 5 most common feed data quality issues

1. Missing required attributes: GTIN and MPN for branded products

Google requires a GTIN (Global Trade Item Number) for all branded products that have been assigned one by the manufacturer. This is not optional for most retail inventory. If your products have a barcode, that barcode encodes a GTIN. Omitting it from the feed triggers a data quality warning and limits the product's ability to compete in Shopping auctions.

The rule is specific: if a GTIN exists for the product (meaning the manufacturer assigned one), you must include it. There is no exception for "I didn't know the GTIN" or "it's inconvenient to look up." Google validates submitted GTINs against manufacturer records. A wrong GTIN is flagged just like a missing one.

For products that genuinely have no GTIN — handmade items, custom goods, products manufactured before GTIN standards were universal — you must explicitly set identifier_exists: FALSE. This tells Google the product has no identifier by design, which prevents the missing-GTIN warning.

2. Price mismatch between feed and landing page

Google's crawler checks product landing pages within 6 hours of a feed submission. If the price displayed on the page does not match the price attribute in the feed at the time of the crawl, the product is flagged. Google requires the prices to match exactly, including currency and any sale discounts.

The most common cause is sale pricing handled incorrectly. A merchant drops the price on the website for a sale but either leaves the original price in the feed or forgets to add an end date to the sale. When the sale ends on the site but the feed still shows the sale price, every crawl produces a mismatch.

The correct approach is to use the sale_price and sale_price_effective_date attributes rather than modifying the base price. Set the base price to the regular price. Set sale_price to the discounted price. Set sale_price_effective_date to the start and end date of the promotion. Google uses these fields to display strikethrough pricing in ads and to handle the crawl-time comparison correctly.

3. Image quality issues

Image problems are the most varied category and the most visible to customers. Google has specific requirements:

• Minimum size: 100x100 pixels for all products. 250x250 pixels for clothing and apparel. In practice, images below 800x800 pixels underperform in Shopping auctions because Google uses image quality as an ad quality signal. The recommended size is 800x800 pixels or larger.
• No watermarks or text overlays: Any text, logo, or watermark on the product image results in a disapproval. The product itself must be the only subject.
• No non-product images: Lifestyle images, images with models in non-standard settings, or images that show the product in a context that obscures it can trigger disapprovals. The main image must show the product clearly, ideally on a white or neutral background.
• No placeholder images: A generic "image coming soon" graphic results in immediate disapproval.

4. Title and description quality

Title quality problems are often not flagged as hard disapprovals — they reduce ad performance without triggering a warning. But Google does disapprove products with titles that are too short, clearly generic, or missing key identifying attributes.

The recommended title structure for most products is: Brand + Product Type + Key Specification. For example: "Nike Air Max 270 Men's Running Shoe Size 10" rather than "Running Shoe." The brand name, product type, and one distinguishing attribute (size, color, model number) are the three elements Google uses to match the product to search queries. Missing any of them means your product may not appear for the queries that would convert.

Description quality is less strictly enforced but affects the relevance score Google uses to determine when and where the product appears. A description that repeats the title, uses vague marketing language, or omits key product details (materials, dimensions, compatibility) underperforms compared to descriptions that answer the questions a buyer would have before purchasing.

5. Availability mismatch

Setting a product to in stock in the feed when the landing page shows out-of-stock, sold out, or a disabled add-to-cart button is a data quality violation. Google's crawler checks availability signals on the landing page and compares them to the availability attribute in the feed.

The reverse is also flagged: setting a product to out of stock in the feed when it is purchasable on the site. Both create a mismatch between what the ad says and what the customer sees when they click through, which is why Google enforces this check.

The fix is to keep feed availability synchronized with website stock levels. For Shopify stores, the Google Shopping app handles this in real time. For manually managed feeds, update the feed every time stock status changes, not on a weekly batch schedule.

How to diagnose feed data quality issues

All feed data quality issues are visible in the Diagnostics tab inside Merchant Center:

1. Log in to Merchant Center and go to Products > Diagnostics.
2. The Diagnostics view separates issues into account-level and feed-level. Account-level issues affect all products. Feed-level issues are tied to specific attributes or feeds.
3. Click on any issue to see the list of affected products. The right column shows how many products each issue affects.
4. Sort by Affected products (descending) to prioritize. Fix the issue affecting the most products first.
5. Click through to individual products to see the exact attribute that is flagging — this shows the value you submitted versus what Google expects.

Fixing GTIN issues

Finding the correct GTIN for a product is easier than most merchants expect:

• Barcode on the product: The barcode printed on retail packaging encodes the GTIN. A barcode scanner app (or the camera on most phones) reads it in seconds.
• Manufacturer's website: Product pages on the manufacturer's site almost always list the UPC, EAN, or ISBN in the product specifications section.
• GS1 database: GS1 maintains a global GTIN registry at gs1.org/services/verified-by-gs1. You can look up any product by its partial code.
• Retailer feeds (for resellers): If you source from a distributor, request a product data file. Most include GTINs as a standard field.

For products with no GTIN by design, add the following attribute to your feed: identifier_exists: FALSE. This applies to custom or handmade products, bundles you assembled yourself, and any product manufactured before barcode standards were established. Do not use this attribute for mainstream retail products that do have a GTIN — Google cross-references and will flag the mismatch.

Fixing price mismatches

Price mismatches almost always come from one of three situations:

1. Sale prices not using the correct attributes: Use sale_price and sale_price_effective_date rather than changing the base price attribute. The sale_price_effective_date format is YYYY-MM-DDTHH:MM:SS+TZ/YYYY-MM-DDTHH:MM:SS+TZ (start/end). When the sale ends, the base price automatically becomes the active price again without a feed update.
2. Feed update lag: If you update prices on the website manually and update the feed on a schedule, there will be a window where they do not match. For stores with frequent price changes, use the Content API or a platform integration that pushes feed updates in real time.
3. Tax display differences: In some regions, Google compares feed prices including tax to landing page prices including tax. Confirm your tax settings in Merchant Center match how your site displays prices.

Fixing image issues

For image size problems, re-upload images at 800x800 pixels or larger. Most product photography tools and stock image platforms produce images at this resolution or higher by default. If you are resizing up from smaller originals, you will get soft images — reshoot if possible.

For watermark and text-overlay problems, upload a clean version of the product image without any graphics on top of it. Use the additional_image_link attribute for lifestyle images and context shots — those do not need to meet the same strict requirements as the main image.

Use the image_link attribute to specify which image is the primary product image. If your product page has multiple images in the markup, Google's crawler may pick the wrong one. Specifying it explicitly in the feed removes that ambiguity.

After fixing: how to resubmit and verify

Once you have corrected the data in your feed, you need to tell Google to re-crawl. The Diagnostics page does not update on its own:

1. Go to Products > Feeds in Merchant Center.
2. Click the feed that contains the corrected products.
3. Click Fetch now (or Process depending on your feed type) to trigger an immediate re-fetch and reprocessing of the feed.
4. For website-crawled attributes (price, availability, images), Google re-crawls the landing pages separately from the feed submission. This can take 24 to 72 hours after resubmission.
5. Return to Products > Diagnostics after 72 hours to confirm the affected products no longer appear under the issue you fixed. If the issue persists, check that the fix was applied to the live site and not just a staging environment.

If you fixed a price mismatch but the product is still disapproved after 72 hours, check that the landing page price and the feed price match for every variant (size, color, etc.) — not just the default variant. Google crawls specific variant URLs when they exist.