Google Merchant Center Product Feed Errors and Solutions

Google Merchant Center product feed errors can prevent products from appearing in Shopping ads, free listings, and other eligible Google surfaces. Some issues affect one item, while account-level policy or setup problems can affect the complete catalogue.

Most feed problems occur because product data is missing, incorrectly formatted, outdated, inconsistent with the landing page, unsupported for the target country, or non-compliant with Google policies. The correct solution begins with the exact issue shown in Merchant Center rather than editing unrelated attributes.

This guide explains how to diagnose and fix common Google Merchant Center errors, including price and availability mismatches, missing GTINs, brand and MPN problems, image disapprovals, landing-page errors, shipping issues, variant mistakes, invalid identifiers, and data-source processing failures.

What Is a Google Merchant Center Product Feed?

A product feed, now commonly managed as a product data source in Merchant Center, contains structured information about the products a business wants Google to understand.

Common product attributes include:

• Product ID
• Title
• Description
• Product link
• Main image link
• Additional image links
• Price
• Sale price
• Availability
• Brand
• GTIN
• MPN
• Condition
• Google product category
• Product type
• Colour and size
• Item group ID
• Shipping information
• Return information

Google uses this information to match products with relevant searches and display accurate product details to potential customers.

What Happens When a Product Has an Error?

Issue level	Possible effect	Recommended response
Warning	The item may remain eligible but performance or data quality may be limited	Correct the data before the issue becomes more serious
Limited eligibility	The product may not be eligible for all destinations or features	Review the affected destination and missing requirements
Item disapproval	The affected item cannot appear in the relevant destination	Correct the product-level issue and allow reprocessing
Account issue	Many or all products may be affected	Review the account-level policy, setup, verification, or website problem
Data-source processing error	Products may not be created or updated correctly	Review file, API, schedule, format, and row-level errors

Where to Find Merchant Center Errors

1. Sign in to Google Merchant Center.
2. Open the Products section.
3. Select the Needs attention tab.
4. Choose the issue card affecting the account or products.
5. Open the Issue Details Page.
6. Review the issue description, cause, suggested action, and business impact.
7. Download the complete list of affected products when available.
8. Correct the source data or website.
9. Request a review only when the issue is eligible and the correction is complete.

The Issue Details Page can also provide direct automation options for certain mismatched price, availability, condition, or image-overlay problems.

Merchant Center Diagnostic Workflow

Step 1: Identify the Issue Scope

Determine whether the problem affects:

• One item
• A group of products
• One destination
• One country
• One data source
• The complete account

Step 2: Download Affected Products

Export the product IDs and issue details so the correction can be tracked systematically.

Step 3: Identify the Authoritative Source

Confirm whether the product value comes from:

• Ecommerce platform
• ERP
• Product information management system
• Spreadsheet
• Scheduled fetch
• Merchant API
• Website crawl
• Supplemental data source

Step 4: Compare Feed, Landing Page, Structured Data, and Checkout

Price, currency, availability, condition, variant, and product identity should remain consistent across all customer and machine-readable sources.

Step 5: Correct the Root Cause

Do not patch only the final export if the same incorrect value will be generated again by the source system.

Step 6: Resubmit or Synchronize

Refresh the product data source, API update, scheduled fetch, or platform synchronization after the correction.

Step 7: Monitor Reprocessing

Product updates can require processing time. Check whether the affected-product count decreases and whether a new issue appears.

Common Google Merchant Center Errors and Solutions

1. Missing Required Attribute

Google requires different attributes depending on the product, country, destination, and category.

Common missing fields include:

• ID
• Title
• Description
• Link
• Image link
• Price
• Availability
• Brand
• GTIN
• MPN
• Condition
• Colour
• Size
• Item group ID

Check the current product data specification and provide the attribute in the supported format.

2. Invalid Product ID

The ID should uniquely identify the product offer and remain stable across updates.

Best practices:

• Use a unique value for each product or variant
• Use the SKU where practical
• Do not change IDs during routine updates
• Do not reuse an old ID for a different product
• Keep the same ID across equivalent country or language submissions where appropriate

3. Product Title Error

The title should clearly identify the product and match the landing page.

A practical structure is:

Brand + product type + important model or feature + colour + size or pack information

Avoid:

• Promotional text
• Free-shipping claims
• Repeated keywords
• All-capital formatting
• Unsupported symbols
• Seller contact details
• Information belonging to another variant

4. Description Error

The description should accurately explain the submitted product. It should not contain links to the store, competitor references, unrelated products, or unsupported promotions.

Include useful information such as:

• Product type
• Material
• Important features
• Dimensions
• Compatibility
• Pack contents
• Usage
• Care instructions

5. Landing Page Not Working

The submitted link should open a live product-detail page on the verified and claimed domain.

Check for:

• HTTP errors
• Redirect loops
• Blocked pages
• Login requirements
• Unavailable mobile experience
• Link to a category or search page instead of the product
• Redirect to another unverified domain
• Pop-ups covering the product information

6. Price Mismatch

A price mismatch occurs when the value submitted to Merchant Center does not match the product price Google finds on the landing page, in structured data, or during checkout.

Common causes include:

• Website updated before the feed
• Feed updated before the website
• Incorrect variant selected by default
• Sale price expired
• Currency mismatch
• GST or other tax treatment differs
• Member price submitted as the standard price
• JavaScript initially displays an old or placeholder price
• Minimum order quantity not reflected correctly
• Checkout adds a mandatory product charge

Fix the source data and ensure the same final purchasable price appears in the feed, initial landing-page response, structured data, and checkout.

7. Availability Mismatch

The submitted availability should match the product's actual online-purchase status.

Supported values can include:

• In stock
• Out of stock
• Preorder
• Backorder

Common causes include:

• Inventory update delay
• Variant is unavailable but another variant is selected
• Regional availability differs
• Product can be viewed but not purchased
• Add-to-cart button is disabled
• Structured data shows a different availability value
• Page changes after JavaScript execution

8. Sale Price Error

The regular price and sale price must be submitted in the correct attributes. The sale price should match the landing page and checkout during the applicable period.

Check:

• Regular price is still submitted
• Sale price is lower than the regular price
• Currency matches
• Sale date range is valid
• Website promotion dates match the data source
• Member-only price is not submitted incorrectly

9. Missing or Invalid GTIN

GTIN is strongly recommended when the manufacturer has assigned one. Examples include UPC, EAN, JAN, ISBN, and ITF-14.

Do not guess, purchase unrelated codes, or use the same GTIN for different variants.

Check:

• Correct number of digits
• Valid checksum
• No spaces or dashes
• GTIN belongs to the exact product
• Multipack uses the multipack identifier where applicable
• Bundle uses the identifier for the main product where applicable

10. Incorrect Identifier Exists Value

The identifier exists attribute indicates whether manufacturer-assigned identifiers are available.

Do not set the value to no when the product actually has a brand, GTIN, or MPN. Misrepresenting identifier availability can cause disapproval.

11. Brand Error

Submit the brand generally recognized by customers and shown on the product or packaging.

Avoid:

• Using the retailer name as the brand
• Using a distributor name instead of the product brand
• Adding a brand to genuinely unbranded products
• Using the original equipment manufacturer brand for a compatible third-party product
• Changing brand spelling across variants

12. MPN Error

Submit only an MPN assigned by the manufacturer. Use the most specific identifier available for each variant.

Do not create an internal SKU and submit it as the manufacturer part number unless it is genuinely the manufacturer's assigned MPN.

13. Image Missing or Cannot Be Crawled

The image link should point to the main product image and be accessible to Google.

Check:

• URL starts with HTTP or HTTPS
• Image URL is publicly accessible
• Robots.txt does not block Googlebot or Googlebot-Image
• Image is not behind authentication
• Server does not block Google requests
• URL returns an actual supported image file
• Image is not temporarily unavailable

14. Image Too Small or Low Quality

Use a high-resolution image that accurately displays the product. Do not submit a thumbnail or enlarge a low-resolution image.

Google has announced a minimum requirement of 500 x 500 pixels for all product images with enforcement beginning January 31, 2027. Merchants should verify the current requirement before publishing or updating large catalogues.

15. Promotional Overlay, Watermark, or Border

The main image should not contain promotional text, price badges, watermarks, borders, or unrelated graphics.

Remove:

• Discount percentages
• Free-delivery text
• Phone numbers
• Website addresses
• Seller logos used as watermarks
• Artificial borders
• Placeholder messages

16. Placeholder or Generic Image

Do not submit a missing-image graphic, logo-only image, generic category image, or an image that does not show the actual product.

17. Variant Mismatch

Each variant should have accurate colour, size, material, pattern, price, availability, image, GTIN, MPN, and landing-page selection.

Use a common item group ID for valid variants of the same product family.

Common variant mistakes include:

• Different products grouped together
• Same GTIN used for all sizes
• Feed says black but landing page selects blue
• Unavailable size selected by default
• Variant-specific price not reflected
• Image belongs to a different colour

18. Google Product Category Error

Use the most accurate category from Google's taxonomy when the attribute is submitted or required.

Do not choose a broad or unrelated category only to avoid required attributes.

19. Shipping Information Missing or Incorrect

Shipping information should represent the cost and delivery arrangement for the target country.

Review:

• Shipping service
• Country
• Region
• Postal-code coverage
• Minimum order rules
• Free-shipping threshold
• Weight and dimensions
• Handling time
• Transit time
• Carrier rates

20. Return Policy Issue

Configure accurate return-policy information where required. The website, Merchant Center configuration, and customer-facing policy should not conflict.

21. Currency or Target-Country Error

The product price and landing page should use the currency supported for the target country. The page language should also align with the submitted product data.

22. Missing Condition

Condition can be required depending on the product. Ensure new, refurbished, or used status matches the landing page and product.

23. Invalid File Format

Data-source files may fail because of:

• Wrong delimiter
• Broken XML
• Incorrect encoding
• Unexpected column names
• Unsupported attribute names
• Invalid quoting
• Missing header row
• File too large for the selected method
• Corrupted compressed file

24. Scheduled Fetch Failure

Check:

• Fetch URL
• Username and password
• File availability at scheduled time
• Server response
• Redirects
• Firewall rules
• Fetch frequency
• Time zone

25. API Synchronization Error

API integrations can fail because of authentication, expired credentials, invalid payloads, missing required attributes, quota limits, product-ID conflicts, or platform-app errors.

Review API responses and log the failed product IDs rather than relying only on the integration dashboard.

Price and Availability Synchronization Strategy

Price and availability are fast-changing attributes. They should be updated as close as possible to the website update time.

Recommended workflow:

1. Update the ecommerce database.
2. Update the customer-facing website.
3. Update structured data in the initial HTML.
4. Send the same values to Merchant Center.
5. Confirm the correct variant and currency.
6. Test the checkout price and purchasability.
7. Monitor mismatch issues.

Automatic item updates can help reduce mismatch disapprovals, but they should not replace accurate primary product data.

Landing Page Compliance Checklist

• Specific product-detail page is used
• Product is the primary focus
• Title and description refer to the same product
• Correct variant is preselected
• Price and currency match
• Availability matches
• Buy or add-to-cart action works
• Page is available without login
• Page works on mobile
• Page does not return 404 or server error
• Pop-ups do not hide important product information
• Redirect remains on the verified domain
• Checkout does not introduce an undisclosed mandatory product charge
• Structured data matches the visible product

Product Identifier Decision Table

Product situation	Recommended identifier action
Manufacturer assigned GTIN	Submit the correct GTIN and brand
No GTIN but manufacturer assigned MPN	Submit brand and valid MPN where required
Genuinely custom or handmade product with no identifiers	Use identifier exists according to the current specification
Compatible third-party product	Use the actual third-party manufacturer's brand and identifiers
Multipack with assigned identifier	Use the identifier for the multipack
Bundle	Use the main product's identifier where applicable and provide bundle information
Variant family	Use variant-specific GTIN and MPN values

Merchant Center Error Troubleshooting Table

Error	What to compare	Recommended correction
Price mismatch	Feed, landing page, structured data, checkout	Synchronize the same final purchasable price
Availability mismatch	Feed value, selected variant, add-to-cart status	Update stock data and landing-page availability
Invalid GTIN	Packaging, manufacturer record, checksum	Submit the valid identifier or remove a guessed value
Missing brand	Product and packaging	Submit the recognized product brand where required
Image cannot be crawled	HTTP response, robots, permissions	Make the image publicly accessible
Image overlay	Main-image file	Remove promotional text, watermark, and border
Landing page unavailable	Status code, redirect, mobile page	Restore a working product-detail page
Wrong variant	URL selection, feed attributes, image	Preselect and submit the same variant
Shipping mismatch	Merchant settings and website terms	Correct service, region, thresholds, and rates
Data-source processing error	File and row-level results	Correct formatting and resubmit

How to Fix Errors in Bulk

1. Download the complete affected-product report.
2. Group products by issue code.
3. Identify the source system responsible for each attribute.
4. Correct the master data.
5. Validate a small sample.
6. Refresh the data source.
7. Review processing results.
8. Confirm changes on the landing pages.
9. Monitor the Needs attention count.
10. Document recurring errors and prevention rules.

Data-Source Validation Checklist

• Attribute names use the supported format
• Required fields are populated
• IDs are unique and stable
• Text encoding is valid
• Prices use supported decimal and currency formats
• Availability values are supported
• Image URLs return valid files
• Product links use the verified domain
• GTINs are not stored in scientific notation
• Leading zeroes are preserved
• Variants share the correct item group ID
• Country and language match the destination
• Shipping rules are configured
• Test products process successfully

Daily Merchant Center Monitoring

• Check new item disapprovals
• Check account-level issues
• Check price mismatches
• Check availability mismatches
• Check data-source processing status
• Check image crawl failures
• Check top-selling affected products
• Check recent website deployments
• Check unresolved review requests
• Update the error tracker

Weekly Product Feed Audit

• Measure approved-product percentage
• Review issue trends
• Audit product identifiers
• Audit variant grouping
• Compare feed and website prices
• Compare feed and website availability
• Review image quality
• Review shipping and return settings
• Review scheduled fetch or API logs
• Prioritize high-click-potential products

Merchant Center Feed Quality KPIs

KPI	Practical calculation
Approved item rate	Approved items divided by submitted items x 100
Disapproval rate	Disapproved items divided by submitted items x 100
Price mismatch rate	Items with price mismatch divided by submitted items x 100
Availability mismatch rate	Items with availability mismatch divided by submitted items x 100
Identifier completeness	Eligible items with valid identifiers divided by identifier-eligible items x 100
Image approval rate	Items without image issues divided by submitted items x 100
Average correction time	Total hours to resolution divided by resolved issues
Repeat issue rate	Products with recurring issues divided by corrected products x 100

Common Merchant Center Management Mistakes

Correcting Only the Export File

If the source database remains wrong, the next synchronization will recreate the issue.

Changing Product IDs

Unnecessary ID changes can break performance history and create duplicate items.

Guessing GTINs

An incorrect GTIN can cause disapproval and incorrect product matching.

Relying Only on Automatic Item Updates

Automation is a safeguard, not a replacement for accurate feed data.

Submitting Category Pages as Product Links

Each item should normally link to its specific product-detail page.

Ignoring Variant Selection

The landing page should show the same variant submitted in the product data.

Uploading Promotional Main Images

Watermarks, prices, borders, and sale text can cause image issues.

Requesting Review Before Fixing the Issue

Complete the website and data correction before using an eligible review process.

Ignoring Shipping and Return Settings

Product data can be correct while account-level fulfilment information remains incomplete.

30-Day Merchant Center Error Reduction Plan

Days 1-7: Audit

• Export all account and item issues
• Group issues by root cause
• Identify high-impact products
• Map each attribute to its source system
• Audit website structured data

Days 8-14: Correct Critical Errors

• Fix account-level issues
• Fix broken landing pages
• Synchronize price and availability
• Correct invalid identifiers
• Restore missing images

Days 15-21: Improve Feed Quality

• Improve titles and descriptions
• Complete recommended attributes
• Correct variant grouping
• Improve image resolution
• Review product categories
• Review shipping and returns

Days 22-30: Automate and Monitor

• Align feed and website update times
• Implement API or scheduled synchronization controls
• Enable suitable automatic item updates
• Create daily issue alerts
• Create a weekly product-feed dashboard
• Document recurring error-prevention rules

How DigiCommerce Supports Google Merchant Center

DigiCommerce helps ecommerce brands, retailers, manufacturers, and online stores prepare, optimize, and troubleshoot Google Merchant Center product data.

• Merchant Center account audit
• Product feed creation
• Item disapproval correction
• Price and availability synchronization
• GTIN, brand, and MPN review
• Variant and item-group correction
• Product title and description optimization
• Image issue correction
• Landing-page compliance review
• Shipping and return configuration review
• Data-source processing analysis
• Feed automation and monitoring

Related DigiCommerce resources include product page SEO, ecommerce category page SEO, ecommerce SEO services, and marketplace analytics services.

Frequently Asked Questions

1. Where can I see Merchant Center product errors?

Open Products, select Needs attention, and choose the relevant issue to open the Issue Details Page.

2. What causes a price mismatch?

Common causes include delayed synchronization, wrong variant selection, expired sale prices, currency differences, dynamic pricing, or inconsistent structured data.

3. What causes an availability mismatch?

The feed may say in stock while the selected product variant cannot be purchased, the website inventory may be outdated, or structured data may contain another value.

4. Should every product have a GTIN?

Submit a GTIN when the manufacturer has assigned one. Do not invent or guess an identifier for products that genuinely do not have one.

5. Can an incorrect GTIN disapprove a product?

Yes. Submit only a valid GTIN assigned to the exact product or variant.

6. Why is Google unable to crawl my image?

The image URL may be blocked, unavailable, protected, invalid, or returning a non-image response.

7. Can product images contain sale text?

The main product image should not contain promotional text, watermarks, or borders.

8. Should feed price include GST in India?

Google's current specification states that countries outside the United States and Canada should include applicable VAT or GST in the submitted price. Merchants should also comply with local law and current account requirements.

9. Can automatic item updates fix all mismatches?

No. They can help reduce some mismatch issues but are not a replacement for accurate and regularly updated primary product data.

10. Why is my product still disapproved after correction?

The update may still be processing, another source may overwrite it, the landing page may still conflict, or an additional issue may remain.

11. Should I request a review immediately?

Request a review only after completing the correction and confirming that the feed, website, structured data, and checkout are consistent.

12. Can DigiCommerce fix Merchant Center errors?

Yes. DigiCommerce can audit the account, correct product feeds, resolve common item errors, review website consistency, and establish ongoing monitoring.

Conclusion

Google Merchant Center errors should be solved through root-cause analysis. Start with the Issue Details Page, identify the affected products, compare feed data with the landing page and checkout, correct the authoritative source, synchronize the data, and monitor reprocessing.

The most common problems involve missing attributes, price and availability mismatches, invalid identifiers, image quality, variant selection, landing pages, shipping, and data-source processing. A reliable product master and synchronized website-feed workflow can prevent repeated disapprovals.

For Google Merchant Center feed creation, product disapproval correction, GTIN and variant audits, price and inventory synchronization, and ongoing product-feed management, connect with DigiCommerce Solutions.