Merchant Center structured data mismatch

Treat the submitted product, the visible landing page, and Product/Offer markup as three descriptions of one offer. The price, priceCurrency, availability, URL, and variant identity should not contradict one another.

Google can use supported structured data while evaluating and updating product information. That makes stale or incorrect markup an operational risk even when customers see the right text.

Many mismatches come from platform themes, apps, and caches updating different layers.

• Offer price differs from the visible selected variant.
• priceCurrency follows a default locale instead of the target page.
• availability remains InStock after inventory changes.
• Several variants are marked up without a clear current offer.
• A server-rendered value and client-visible value disagree.
• Identifier markup belongs to the parent rather than the purchasable variant.

Open the exact submitted URL for the target market and variant. Compare what a customer sees with the rendered JSON-LD or supported microdata—not only the template source. Check that the markup resolves to the same offer after redirects and localization.

Then compare Merchant Center's processed values and latest issue detail. A structured-data testing tool can validate syntax, but valid syntax does not prove commercial accuracy.

Identify which system owns each value: commerce platform, feed integration, theme, server cache, or client script. Update the shared source where possible so visible content, markup, feed, and checkout move together. Confirm the corrected markup persists without a logged-in session.

Supported evidence checks may compare Merchant price or availability with readable page markup. CommerceVigil reports missing, conflicting, or inaccessible evidence as inconclusive; it does not claim structured data is the sole cause or certify markup for every Google surface.