Why Google Is Merging Schema Markup With Merchant Center Feeds
Google's finally putting words to a tension merchants have lived with for years: you're feeding Google product data twice, and the two feeds don't always talk to each other. The company revealed it's working to bridge the gap between website markup using schema.org structured data and product feeds submitted via Google Merchant Center. In practice that means one-to-one parity between the attributes schema.org supports and the attributes Google expects in Merchant Center, so a product stops looking like two slightly different things depending on where Google reads it.
The initiative surfaced during a recent Search Off The Record podcast episode. Irina Tuduce, a longtime Google employee involved with the company's shopping search infrastructure, laid out why both pipelines matter right now and why the mismatch hurts.
The Two Pipelines Running Shopping Right Now
In search results Google leans on structured data markup and Merchant Center product feeds to surface rich listings. They're parallel systems with different refresh logic.
Tuduce recommends using both options. She said: "We recommend doing both. Because, as I said, in signing up on the Merchant Center UI, you make sure some of your inventory, the one that you specify, will be in the Shopping results. And you can make sure you'll be on dotcom on the Shopping tab and Image tab. And then, if you specify how often you want us to refresh your data, then you can be sure that that information will be refreshed. Otherwise, yeah, you don't know when we will have the resources to recrawl you and update that information."
That's the feed path. You pick the inventory, set a refresh cadence, and Google respects it. You get control over what's in Shopping, and when it updates.
Markup is the other path. Implementing schema.org markup lets Google extract product details from websites during the crawling process. It's less controllable, more opportunistic, and it depends on crawl budget and frequency. When both pipelines are in play, shoppers see the net result, and merchants see the delta in performance.
The Two Pipelines Running Shopping Right Now
In search results Google leans on structured data markup and Merchant Center product feeds to surface rich listings. They're parallel systems with different refresh logic.
Tuduce recommends using both options. She said: "We recommend doing both. Because, as I said, in signing up on the Merchant Center UI, you make sure some of your inventory, the one that you specify, will be in the Shopping results. And you can make sure you'll be on dotcom on the Shopping tab and Image tab. And then, if you specify how often you want us to refresh your data, then you can be sure that that information will be refreshed. Otherwise, yeah, you don't know when we will have the resources to recrawl you and update that information."
That's the feed path. You pick the inventory, set a refresh cadence, and Google respects it. You get control over what's in Shopping, and when it updates.
Markup is the other path. Implementing schema.org markup lets Google extract product details from websites during the crawling process. It's less controllable, more opportunistic, and it depends on crawl budget and frequency. When both pipelines are in play, shoppers see the net result, and merchants see the delta in performance.
Where Markup And Feed Data Collide
Discrepancies arise when the product information in a merchant's schema.org markup doesn't perfectly align with the details provided via their Merchant Center feed uploads. Pricing can drift. Availability flips. Variant data gets simplified on one side and not the other.
Tuduce explained the fallback logic plainly: "If you don't have the schema.org markup on your page, we'll probably stick to the inventory that you specify in your feed specification."
Google's initiative aims to resolve such discrepancies. The point isn't to pick a winner between markup and feed. It's to make them mean the same thing.
The attributes overlap to a big extent, but there are still gaps that exist. We will want to address those gaps, Tuduce said. That admission is useful because it names the real problem: even when merchants try to be consistent, the vocabularies don't line up perfectly, so consistency is hard to prove.
What Parity Actually Means
One-to-one parity sounds technical, but the merchant impact is practical. If schema.org supports an attribute and Merchant Center supports the same attribute, the values should be interchangeable and expected to stay in sync across Shopping, Image results, and search.
A unified product data model could keep product details like pricing, availability, and variant information consistently updated and accurately reflected across Google's search results. That's the promise. Less manual reconciliation between a CMS schema implementation and a Merchant Center feed spreadsheet.
For merchants, consistent product listings with accurate, up-to-date details can boost visibility in Google's shopping experiences. Streamlined data processes also mean less redundant work. That's the promise: you stop maintaining two separate data streams and start maintaining one that feeds both pipelines.
What Merchants Lose When Data Splits
The cost of split data isn't abstract. When markup says in stock and the feed says out of stock, Google has to choose which signal to trust, and the shopper gets the wrong answer. That erodes click-through and trust.
Refresh timing adds another layer. With a feed you can specify how often you want data refreshed. With markup you don't know when Google will recrawl you and update that information. If your price changes daily and your crawl happens weekly, the gap is visible.
Merchants end up building processes to keep two sources in sync manually. That's duplicate work, more points of failure, and more places for a typo to propagate.
What Google Said About Closing Gaps
The Search Engine Journal coverage from September 5, 2024, summarizes the conversation and quotes Tuduce directly. The company wants to unify structured data markup and Merchant Center feed data for consistent product listings across shopping experiences.
Google wants to unify schema.org markup and merchant feed data for consistent product listings. A unified product data model will streamline merchant workflows. Reliable product data can lead to a better search experience. Those are the three lines framing the work.
The team plans to keep marketers informed by leveraging schema.org's active GitHub community and opening the update process to public feedback. That matters because schema.org is open source. Changes won't happen in a closed doc; they'll be discussed where the community already works.
GitHub, Feedback And The Rollout Plan
Opening the update process to public feedback is a deliberate choice. It means merchants and developers can see proposed attribute alignments before they land, and push back if a mapping would break existing implementations.
Google didn't announce a timeline in the podcast excerpt. The effort is described as ongoing. The full discussion is worth hearing, starting around the 12-minute mark, for the nuance around how Google weighs feed authority versus crawl freshness.
The implication is that the unified model will roll out gradually, attribute by attribute, with schema.org as the coordination surface.
What To Do Before The Merge Lands
You can't force parity today, but you can reduce the friction when it arrives.
Audit current product data across website markup and merchant feeds for inconsistencies. Pick a representative set of SKUs and compare title, price, availability, GTIN, brand, and variant attributes side by side. Document where they diverge.
Prepare to consolidate product data workflows as Google's unified model rolls out. If you're maintaining two exports, map them to a single source of truth now. The closer your CMS, PIM, and feed generator are, the easier the transition.
Implement richer product schema markup using expanded vocabulary. The more complete your markup is, the more useful it will be when Google starts treating it as authoritative parity with the feed.
Monitor metrics like impressions and clicks as consistent data surfaces. Consistent data tends to surface first in Shopping and Image results, so watch those surfaces for lift after fixes.
Prioritize product data hygiene and frequent catalog updates. Clean data amplifies the benefit of parity. Messy data just gets mirrored consistently.
By aligning your practices with Google's future plans, you can capitalize on new opportunities for streamlined product data management and enhanced shopping search visibility.
What Changes For Shoppers
For consumers, a harmonized system translates to more relevant, trustworthy shopping journeys. When the data is consistent, there's less chance you'll click a result only to find pricing or availability that doesn't match.
That's the real win. Merchants get less redundancy. Shoppers get fewer surprises. Google gets cleaner signals to rank and display.
The work is still in progress, but the direction is clear: Google wants one product truth, expressed once, readable by both markup and feed.
Related Internal Content
- Who Should Own the Product Feed? Why SEO Must Partner With Paid in the AI Era
Related Reading
- AI Shopping Isn't Reading Your Website—It's Reading Your Data
- Who Should Own the Product Feed? Why SEO Must Partner With Paid in the AI Era
- Google's John Mueller: Fix Conflicting Product Availability Metadata, Don't Test Which Source Wins
