Best Practices for Google Product Review Feed

These are the recommended ways to configure Google Product Review Feed based on what we've seen work well. The key to success with Google Product Reviews is having proper product identifiers (especially GTINs) and maintaining a consistent feed. This guide covers attribute mapping, configurable product handling, and feed maintenance.

Recommended configurations and patterns for Google Product Review Feed.

General Guidelines

Do's

Don'ts

Product Identifier Priority

Google needs to match your reviews to products in their catalog. The priority order:

1. GTIN (EAN/UPC/ISBN) - Most reliable, always preferred
2. MPN + Brand - Good fallback when no GTIN
3. SKU + Brand - Last resort, less reliable matching

Recommendation: Invest time in populating GTINs for your products. This significantly improves review matching rates.

Checking GTIN Coverage

-- Quick check for GTIN attribute coverage
SELECT COUNT(*) as total,
       SUM(CASE WHEN value IS NOT NULL AND value != '' THEN 1 ELSE 0 END) as with_gtin
FROM catalog_product_entity_varchar
WHERE attribute_id = (SELECT attribute_id FROM eav_attribute WHERE attribute_code = 'ean');

Configurable Product Handling

For stores with configurable products (size, color variants), choose the right linking strategy:

Option 1: Use Connected Product (Default)

Option 2: Force Parent Product

Option 3: Link to Parent and All Simples

Feed Generation Frequency

Tip: Daily generation is sufficient for most stores. More frequent updates don't improve Google matching - they just use more server resources.

Multi-Store Setup

For stores with multiple store views:

Same catalog, different languages:

• Generate separate feeds per store view
• Use descriptive filenames (reviews-en.xml, reviews-nl.xml)
• Same GTIN mapping across all views

Different catalogs per store:

• Configure each store independently
• May need different attribute mappings
• Submit separate feeds to Merchant Center

Review Quality

Google may reject feeds with low-quality reviews. Ensure:

• Reviews have actual content (not just ratings)
• No spam or fake reviews
• Proper moderation before approval

Tip: Only approved reviews in Magento are included in the feed.

Feed Validation

Before submitting to Google:

1. Check feed structure:

   • Download the generated XML
   • Validate against Google's schema
   • Check for XML errors

2. Verify content:

   • Reviews have content
   • Products have identifiers
   • Timestamps are valid

3. Test submission:

   • Use Google Merchant Center's feed testing tool
   • Review any warnings or errors

Common Mistakes

Mistake: No GTIN attribute mapped

Mistake: Wrong Collection Method

Mistake: Too frequent cron generation

Mistake: Not checking Merchant Center for errors

Performance Considerations

The feed generation process:

• Reads all approved reviews
• Joins product data for identifiers
• Writes XML file to pub/media directory

For very large review sets (10,000+):

• Generation may take several minutes
• Consider running via CLI during off-peak hours
• Monitor disk space for feed files

Need More Help?

Documentation:

• All Help Articles - Complete documentation overview

Support:

• Contact Support - Get help from our team