Common Google Merchant Center Review Feed Errors (And How to Fix Them)

Google Merchant Center is extremely strict when validating Product Ratings feeds. Even one small formatting mistake can cause Google to:

• Reject your XML file
• Ignore specific reviews
• Fail to match reviews to products
• Delay your ratings from appearing on Google Shopping

This guide breaks down every common Google review-feed error, explains why it happens, and shows you exactly how to fix it.

Let’s begin.

Why Review Feeds Get Rejected

A review feed is rejected when:

• The XML structure is invalid
• A required field is missing
• Timestamps don’t follow ISO format
• Product identifiers don’t match your feed
• Review IDs are duplicated
• The merchant doesn’t meet minimum eligibility
• The CSV wasn’t cleaned before XML conversion

Fixing these issues typically resolves the problem instantly.

Most Common Google Review Feed Errors (2026 Update)

Below are the exact errors most merchants encounter when uploading Product Ratings.

1. “Invalid XML”

This means Google could not parse your XML at all.

Common causes:

• Missing closing tags
• Incorrect nesting
• Emojis or special characters
• Broken line breaks
• HTML inside review content
• Unexpected spaces or formatting
• Encoding problems

How to fix it:

• Remove emojis
• Remove HTML (like <br>, <p>, <div>)
• Ensure every <review> has a matching </review>
• Check that <reviews> wraps the entire file
• Ensure UTF-8 encoding

For step-by-step cleaning help: How to Clean Your Review CSV

2. “Missing required field”

Google requires these XML elements:

• <review_id>
• <reviewer_name>
• <review_timestamp>
• <content>
• <rating>
• <product_ids> + (SKU or GTIN or MPN)

If any field is empty or missing, your feed is rejected.

How to fix it:

• Ensure every review has a rating (1–5)
• Ensure reviewer names exist (use “Anonymous” if needed)
• Add timestamps to missing rows
• Add SKU/GTIN/MPN to every review
• Delete incomplete reviews

Full specification here: Google Product Ratings Feed Specification Explained (2026 Update)

3. “Product not found”

Google could not match the review to a product in your feed.

Most common causes:

• SKU mismatches
• GTIN doesn’t match product feed
• Variant SKUs missing
• Incorrect capitalization
• Extra spaces or hidden characters

How to fix it:

• Match your CSV identifiers to GMC exactly
• Use uppercase for SKUs
• Remove trailing spaces
• Ensure variant-level IDs are included

Full matching guide here: How to Match Reviews to SKUs, GTINs & MPNs

4. “Too few reviews”

Google requires:

• At least 50 total reviews across your website
• From the past 12 months
• From unique customers

If you have fewer than 50, your stars will not appear on Google Shopping.

How to fix it:

• Send review request emails
• Offer incentives (Google allows discounts for reviews)
• Migrate old reviews from past platforms
• Add reviews from Loox/Judge.me/Okendo/Stamped into one CSV

Remember: You can still upload your feed, but stars will not appear until you hit 50 reviews.

5. “Invalid timestamp”

Google requires timestamps to follow ISO 8601 format:

✔ 2026-01-12T15:34:00

❌ 01/12/26

❌ 2026/1/12

❌ 2026-01-12 15:34

How to fix it:

• Convert all timestamps to: YYYY-MM-DDThh:mm:ss
• Remove timezone abbreviations
• Remove AM/PM formatting
• Ensure consistent format across the feed

6. “Duplicate review_id”

Every review must have a unique <review_id>.

Common causes:

• Two reviews share the same ID
• Imported reviews were merged incorrectly
• Apps reuse IDs during migration

How to fix it:

• Generate unique IDs (e.g., REV-2001-PROD01)
• Appended timestamp + SKU works well
• Check for trailing spaces or hidden characters

7. “Unsupported characters or encoding”

Your XML may contain:

• Emojis
• Smart quotes
• Foreign symbols
• Curly apostrophes
• HTML entities

These break XML parsing.

How to fix it:

• Replace smart quotes with "plain" quotes
• Remove emojis
• Delete trademark symbols (™®, etc.)
• Run your CSV through a UTF-8 normalizer

8. “Review rejected due to unsupported language”

Google may reject reviews if:

• The language isn’t supported
• The content mixes multiple languages
• The text contains unreadable encoding

How to fix it:

• Standardize review language
• Remove corrupted text
• Clean up multi-language reviews

9. “Feed disapproved: Incorrect file format”

This happens when merchants upload:

❌ CSV

❌ TXT

❌ JSON

❌ Screenshots

Google only accepts XML for Product Ratings.

How to fix it:

Convert your CSV to XML first: 👉 https://review2xml.com

10. “Feed uploaded but stars not showing”

This is not an XML error — it’s a visibility issue.

If your feed is approved but stars aren’t appearing, use this full guide: 👉 Why Your Google Product Ratings Aren’t Showing (Full Troubleshooting Guide)

⭐ Bonus: Before Uploading, Validate Your File

Here’s a quick pre-upload checklist:

✔ All required XML fields included
✔ SKUs/GTINs/MPNs match your product feed
✔ No emojis
✔ No HTML
✔ No duplicate review IDs
✔ ISO timestamps
✔ UTF-8 encoding
✔ <reviews> wraps entire file
✔ <review> tags properly nested

If you want to skip manual validation, Review2XML handles all of this for you automatically.

Final Thoughts

Google review feed errors are frustrating, but every issue has a clear fix.

In summary:

• Invalid XML → Fix structure, remove emojis
• Missing required field → Fill in rating, timestamp, identifiers
• Product not found → Match SKUs/GTINs/MPNs
• Too few reviews → Reach 50 unique reviews
• Invalid timestamp → Use ISO format
• Duplicate review_id → Generate unique IDs
• Unsupported characters → Clean your CSV
• Wrong file format → Google accepts XML only

To complete your Product Ratings setup:

• Convert your CSV to XML →
https://review2xml.com

• Follow the upload guide →
https://review2xml.com/blog/how-to-upload-product-reviews-to-google-shopping-for-shopify-stores

• Troubleshoot missing stars →
https://review2xml.com/blog/google-shopping-stars-not-showing

Frequently Asked Questions

What is the most common reason a review feed gets rejected by Google?

Invalid timestamp format is the most frequent cause. Google requires ISO 8601 format (YYYY-MM-DDThh:mm:ssZ). Most review platform CSV exports use a different date format that must be converted before uploading.

How do I find which specific reviews are causing errors?

In Google Merchant Center, go to Products & store > Reviews > Product reviews and click on your feed. The Diagnostics tab shows individual review-level errors with the review ID that caused each one.

Can I fix errors without re-uploading the entire feed?

No. Google requires you to upload a complete replacement feed — it does not support partial updates. Fix all errors in your file, then upload the corrected version.

Why does Google say my product identifier doesn't match any products?

This means the SKU, GTIN, or MPN in your review feed doesn't exactly match the same identifier in your Merchant Center product feed. Even small differences (leading zeros, uppercase vs lowercase) will cause a mismatch.

How long after fixing errors does it take for the feed to go Live?

Typically 24 to 72 hours after uploading the corrected file. You can monitor status in the Merchant Center feed management screen.