Google's John Mueller
When your product page says "in stock" in the HTML, "out of stock" in the structured data, and something entirely different in your Merchant Center feed, you've got a metadata conflict. And if you're sitting there wondering which value Google will actually use, John Mueller has a blunt answer: stop guessing and just fix it.
Google's Search Advocate made this clear recently in a Bluesky thread, and the takeaway is straightforward — but more important than most SEO advice I read.
The Bluesky Thread That Started It All
Sebastián Galanternik flagged a real-world example that any ecommerce operator will recognize: a product listing where the visible page showed the item as out of stock, while the server-rendered HTML and the structured data markup both claimed the item was available.
He asked a simple question — how do free listings handle availability when those sources disagree?
Mueller's first reply cut straight to the point. "I'd recommend not providing clashing meta data – it makes it hard to work out what's relevant. An option might be to serve it via feed instead, for example."
Notice what Mueller didn't do. He didn't offer a hierarchy. He didn't say "the feed wins" or "the structured data takes priority." He just told Galanternik to stop providing conflicting signals in the first place.
No Public Order of Precedence
When Galanternik pressed further — asking which source Google actually treats as correct when a feed and on-page structured data disagree — Mueller delivered the line that matters most:
"There's no publicly defined order of precedence for metadata reconciliation here – if you're giving conflicting metadata, you should fix it, not analyze if it'll work regardless."
That's it. Google hasn't published a rule. It hasn't documented a priority list. If you're trying to reverse-engineer which signal wins, you're wasting time on a moving target.
This isn't just about availability, either. Mueller pointed out that dates are a common version of the same problem. A visible date on the page, a dateModified value in your structured data, and a lastmod value in your sitemap can all conflict. And they often do.
"All of these can have different weights & filters, + they'll change over time. The web is very dynamic, and people are very creative :-). It's just to say that understanding & interpreting metadata is hard, so the easier you can make it to pick the right value, the more likely it'll work."
Why Availability Gets Out of Sync So Easily
The reason availability conflicts show up so often is that they're easy to create accidentally. You've got three separate systems talking about the same product:
- The initial HTML served by your server
- The rendered DOM after JavaScript executes
- Your Merchant Center feed
Any one of those can tell a different story. Your server might serve the original stock status. Your JavaScript might update it to "out of stock" after a real-time inventory check. Your feed, updated nightly, might still reflect yesterday's numbers.
Google hasn't said which of those three it prioritizes. So aligning them is the only reliable strategy.
This isn't theoretical, either. We've covered how clashing prices across the site, the feed, and the schema have already driven Merchant Center disapprovals. Availability conflicts are just the next thing in line.
How to Actually Check for Conflicts
Here's what you should do, practically speaking. Pull three snapshots of any product page:
- The raw HTML your server returns (right now, before any JavaScript runs)
- The rendered DOM after all scripts have executed
- Your Merchant Center feed for that product
If all three agree, you're in good shape. If they don't, fix the conflict. Don't test which value Google settles on. Don't wait to see what happens in search results.
It's a technical SEO best practice that prevents disapprovals, confusing users, and wasted engineering hours.
The Bigger Picture
Mueller's advice here isn't about a specific algorithm. It's about a principle: make it easy for Google to pick the right value by ensuring consistency. Every conflict you introduce gives the system another puzzle to solve. Every conflict you resolve makes its job simpler.
The easier you can make it, the more likely it'll work. That's the whole thing, really.
You don't need to reverse-engineer Google's internal reconciliation process. You just need to stop giving it conflicting instructions and fix what's broken.
Source: Google's Mueller: Fix Conflicting Metadata, Don't Test It by Matt G. Southern, Search Engine Journal, July 29, 2026
