When a page contains conflicting metadata, first identify which fields are duplicated or inconsistent and where each value comes from, then resolve the conflict rather than testing which value Google ultimately uses. This article discusses two situations: multiple SEO plugins generating description tags, and inventory information differing across a product page, structured data, and a product feed. Each requires checking different sources; disabling a plugin or switching to a feed is not a universal solution.
Duplicate description tags: first identify which plugins generate them
A user report on Webmasters Stack Exchange described finding two Meta Description tags in the page source after enabling both SEO Ultimate and Yoast SEO. This case establishes that description tags were duplicated and both plugins were generating descriptions. The available material does not include the text of the two descriptions, so it does not establish that their wording was contradictory.
- Check the number of description tags in the source code and whether multiple plugins are generating them.
- Once the sources of duplication are confirmed, adjust how descriptions are generated to prevent both plugins from producing tags at the same time.
The user planned to disable Yoast SEO and watch for any URL issues, but the available material provides no follow-up results. This approach is therefore only a troubleshooting lead, not a verified fix. It does not mean that all websites should disable the same plugin.
Inconsistent product availability: compare the HTML, rendered page, and feed
A July 2026 report from Search Engine Journal described a product page that displayed an out-of-stock status while the server-delivered HTML and structured data indicated that the product was in stock. This was not simply a duplicate-tag issue: different sources gave contradictory availability information for the same product.
For availability fields, the report recommended comparing the following:
- Initial HTML: the availability information initially delivered by the server.
- Rendered DOM and visible page content: whether different values appear after JavaScript runs.
- The page’s structured data and Merchant Center product feed: whether they agree with what the page displays.
During the review, list values from each source side by side to identify specific discrepancies, such as “the page shows out of stock, but the structured data shows in stock,” rather than simply labeling them as an SEO issue. The goal is to provide consistent product information across all sources.
Resolve inconsistencies rather than guessing which source takes priority
The report noted that Google has not publicly explained which source takes priority when product availability information conflicts. John Mueller recommended fixing the inconsistencies rather than investigating whether things could still work despite the conflicting information. Another article published around the same time also cautioned that the relevant weighting and filtering criteria may change over time.
Mueller suggested providing data through a feed as an option, but did not promise that feeds always take priority or guarantee that they would eliminate conflicts. The report also mentioned that price discrepancies across a website, feed, and structured data had led to Merchant Center disapprovals. However, that pricing example does not mean that all metadata conflicts result in disapproval.
Conflicting page metadata: perspectives from across the web
Which fields can be checked when page dates are inconsistent?
You can compare the date displayed on the page, dateModified in the structured data, and lastmod in the sitemap, first confirming each value and its source. Search Engine Journal reported a situation in which these three dates conflicted. However, the supplied material does not explain how that case was resolved, nor does it establish that all three fields must always contain the same date.
What should be checked in hreflang attributes on multilingual pages?
A 2017 Semrush study recommended checking whether the set of hreflang attributes includes the current page’s URL and language code. Among websites with conflicts in their page source, the study found that 96% of cases lacked self-referencing hreflang. The article noted that this could cause the attributes to be ignored or misinterpreted. These were findings from that study at the time, not a statement about the current state of all websites or current platform rules.
References
- Using Excerpts as Meta Descriptions?webmasters.stackexchange.com — Source used in the article above.
- 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.
- 13 Most Common Hreflang Mistakes [Semrush Study]www.semrush.com · 2017-02-15T03:00:00Z — Discusses: What should be checked in hreflang attributes on multilingual pages?
- Google’s Mueller: Fix Conflicting Metadata, Don’t Test Itwww.searchenginejournal.com · 2026-07-29T10:30:57+00:00 — Discusses: Which fields can be checked when page dates are inconsistent?

