Should you really implement both Merchant Center feeds and product structured data?

Why does Google impose two distinct systems for product data?

The distinction between Merchant Center feeds and structured data is based on two different display environments. The Merchant Center feed powers the Shopping tab, Google Shopping ads (both paid and free), and all Google shopping surfaces. This feed is structured according to a specific XML or TXT format, hosted on your servers or through a third-party platform.

The Product structured data is a schema.org markup integrated directly into the HTML of your pages. It allows Google to generate rich product snippets in organic search results: price, availability, reviews, stars. These two systems do not share a common API and operate in silos—hence the need to maintain both in parallel.

What happens if we only use one of the two formats?

If you only deploy the Merchant Center feed, your products will appear in the Shopping tab and free ads, but your pages will not benefit from any rich snippets in regular organic results. You will therefore lose visibility and CTR on informational or transactional queries that do not trigger the Shopping interface.

Conversely, if you only implement the structured data without the Merchant Center feed, your products will not be eligible for free Shopping surfaces. You miss out on a major acquisition channel, particularly on mobile where the Shopping tab captures a significant share of e-commerce traffic.

Is this double entry really necessary in the long term?

Mueller mentions a potential future simplification, without providing a timeline or technical details. The idea would be to allow Google to automatically reconcile data from both the feed and the markup, or even to require only one format. However, this statement remains vague and conditional—no official roadmap has been published.

In the meantime, the redundancy is accepted by Google and presented as a necessary evil. E-commerce traders must therefore maintain two product data systems, with the development, synchronization, and maintenance costs that this implies.

• Merchant Center feed: mandatory for Shopping surfaces (tab, free listings, Google Lens, YouTube Shopping).
• Product structured data: mandatory for rich snippets in regular organic results.
• Double maintenance: currently unavoidable if you aim for maximum visibility.
• Announced simplification: hypothetical, no commitment or timeline.

Is this statement consistent with observed practices on the ground?

Yes, the complementarity between feeds and structured data is a reality observed since the introduction of free listings in the Shopping tab. Sites that have only deployed one of the two formats consistently experience partial visibility loss: either in organic rich snippets or in Shopping surfaces. This redundancy has been documented for years in Google's official guidelines.

However, the promise of simplification is much more debatable. Google frequently mentions "upcoming rationalizations" without ever following through. The most emblematic case is the AggregateRating markup, which remains distinct from the Merchant Center feed despite years of requests from the field. There’s no indication that a merger would be technically trivial or a priority for Google.

What nuances should be added to this recommendation?

Mueller talks about "product structured data", but does not specify whether it includes only the Product type or also the Offer, AggregateOffer, Review types. In practice, a complete Product markup must include nested entities (Offer for price, AggregateRating for reviews, ImageObject for visuals). This level of granularity is not explicitly outlined in the statement.

Moreover, the Merchant Center feed requires specific attributes not covered by schema.org: GTIN, MPN, brand (mandatory for certain categories), shipping, tax, age_group, gender, color, size. These fields are not included in the Product vocabulary of schema.org, making the "simplification" technically complex. [To be verified]: no official source details how Google plans to reconcile these two schemas of different structures.

In which cases does this rule not apply or require adjustments?

If you sell digital products, services, or non-physical content, the Merchant Center feed is generally not relevant (except for specific use cases like subscriptions or licenses). The Product structured data remains sufficient to generate rich snippets. However, be careful: Google may interpret these products as ineligible for rich results if they do not comply with the guidelines (no fictitious pricing, verifiable availability).

For multilingual or multi-currency sites, synchronizing between feeds and structured data becomes a headache: the Merchant Center feed requires a feed for each country/language, while the on-page markup must reflect the currency and language of the displayed page. A desynchronization can lead to product rejections in the Merchant Center or inconsistent rich snippets. This issue is never addressed in official communications.

What concrete steps should be taken to align feeds and structured data?

The first step is to audit discrepancies between your Merchant Center data and your on-page markup. Export your current feed and compare the fields price, name, availability, image, brand with the content of your schema.org Product tags. The most frequent discrepancies involve dynamically varying prices (promotions, geolocated discounts) and real-time inventory.

Next, implement an automated synchronization system: ideally, your product data should come from a single source (PIM, ERP, CMS) that feeds both the XML feed and the JSON-LD injected into your pages. Headless e-commerce solutions (Shopify, WooCommerce, Magento) offer plugins that generate both formats simultaneously, but always check for consistency post-deployment.

What mistakes should be avoided during implementation?

Never manually duplicate data between feeds and markup: this inevitably creates desynchronizations (outdated prices, out-of-stock products shown as available). Use dynamic variables and templates to ensure that both sources update at the same time. Also watch out for JSON-LD syntax errors that invalidate the structured data without triggering a visible alert on the user side.

Also avoid overloading the Product markup with irrelevant data. Google penalizes "spammy" markup: do not fill in fictitious fields (invented reviews, fake prices, misleading availability) to force the display of rich snippets. Manual validations by Google can lead to manual actions across the entire site.

How can you verify that your implementation is compliant and effective?

Use Google's Rich Results Test to validate the structured data of your product pages. Test multiple pages (product in stock, out of stock, on promotion) to verify that the markup adapts dynamically. On the Merchant Center side, check the diagnostic reports: product rejections, warnings on missing fields, price discrepancies.

Finally, monitor your performance in Google Search Console: the “Performance” report filtered on product pages allows you to measure the impact of rich snippets on CTR. Compare impressions and clicks before/after deployment of the markup. For Shopping surfaces, analyze data in the “Shopping” tab of GSC (if enabled) or directly in the Merchant Center dashboard.

• Audit discrepancies between Merchant Center feeds and Product structured data
• Automate synchronization via PIM, API or CMS plugin
• Validate JSON-LD with Google’s Rich Results Test
• Check Merchant Center diagnostic reports (rejections, warnings)
• Monitor the CTR of product pages in Search Console
• Test various scenarios (stock, promotion, multi-currency) to ensure dynamic consistency