When sources disagree on a product data field, first identify the field and the sources, then resolve the inconsistency rather than testing which value the platform will use. For the Google product information discussed here, check the product feed, the page’s structured data, and its visible content. A July 2026 report quoted Google’s John Mueller as saying that there is no publicly defined order of precedence for resolving these metadata conflicts, and that weights and filtering criteria may change. A value selected on one occasion should therefore not be treated as evidence of a fixed rule.
First, identify what conflicts: availability, price, or dates?
The discussion began with product availability: the person asking the question noted that the page showed the product as out of stock, while the HTML sent by the server and the structured data indicated that it was in stock. Follow-up questions asked how Google decides when a feed and a page’s structured data disagree. When checking these issues, it is not enough to note that “the data conflicts.” Identify which field has different values and which sources provide them:
- Availability: Does the page show the product as out of stock while the HTML, structured data, or feed still indicates that it is in stock?
- Price: Does the price displayed on the website differ from the prices in the feed and structured data?
- Dates: Do the visible date, dateModified, and the sitemap’s lastmod contradict one another? This was a separate discussion in the report and should not be directly applied as a rule for handling availability conflicts.
When checking availability, do not rely solely on what the browser displays
The report noted that product availability information may have several versions: the initial HTML shows one status, the DOM (the page’s document structure) after JavaScript runs shows another, and the Merchant Center feed supplies a third. A page that looks correct does not necessarily agree with the other sources.
- Inspect the product availability information in the initial HTML and check the structured data.
- Compare the DOM after JavaScript runs with the page’s visible content.
- Check the same field in the product feed, identify any differences, and correct them.
For example, if the page shows the product as out of stock but the initial HTML and feed still indicate that it is in stock, correct those inconsistencies. Do not stop checking just because the page looks right. This comparison is intended to identify conflicts; it does not mean that any source necessarily takes precedence.
Consistent information still does not guarantee which value Google will use
Rather than guessing which source Google will use, provide consistent product information in the feed, structured data, and visible content to help Google understand it. The report also mentioned that conflicting prices across a website, feed, and structured data have led to Merchant Center disapprovals. This does not mean that all availability conflicts will lead to disapproval. Resolving inconsistencies is a practical step, but these reports do not guarantee which value Google will use or that correcting the data will result in approval.
Conflicting product metadata: perspectives from across the web
Could a product feed be used to provide the data instead?
Yes, it is an option to consider. Google’s John Mueller suggested providing data through a product feed when discussing conflicting metadata, but he was not requiring all merchants to switch to a feed. Even with a feed, you should avoid providing contradictory information across sources. The discussion offered no guarantee that using a feed would eliminate conflicts or ensure that Google uses its values.
References
- Social Search Data For All, AI-Detected Pages Rank Lower – SEO Pulsewww.searchenginejournal.com · 2026-07-31T12:30:09+00:00 — Source used in the article above.
- Google’s Mueller: Fix Conflicting Metadata, Don’t Test Itwww.searchenginejournal.com · 2026-07-29T10:30:57+00:00 — Discusses: Could a product feed be used to provide the data instead?

