New researchTechnical SEO & AI Search · 2027Explore the framework

Merchant Center feed vs structured data: fix product mismatches

Find and fix price, availability and condition differences across your Merchant Center data source, product-page markup and visible offer.

Part of the E-commerce SEO series. For the full picture, start with E-commerce technical SEO: the complete guide for online stores.

A product page says $39, its JSON-LD says $49, and the Merchant Center item still says $59. Changing the number in one place may clear a warning temporarily, but it does not solve the synchronization problem. A Merchant Center feed versus structured data audit follows one offer across every place Google and shoppers see it. Merchant Center’s automatic item updates can correct occasional price or availability differences, but they are a safety net, not a fix for a broken sync.

How do you fix a Merchant Center feed versus structured data mismatch?

Compare the submitted item with its exact landing URL, the visible product offer and the rendered structured data. Google’s Merchant Center automation guidance says it can use page markup and other extracted data to update price, availability and condition, but these updates are not a replacement for accurate, frequent product data submissions. Mismatches can still cause disapprovals.

Source What to capture for one item
Merchant Center data Item ID, link, price, sale price, currency, availability, condition, update time
Visible landing page Selected variant, current purchasable price, currency, stock state
Product markup Offer URL, price, priceCurrency, availability, itemCondition

Use the same variant and destination URL in all three checks. The product structured data guide covers eligibility and schema shape; this article focuses on disagreement between systems.

Which mismatches matter most?

Start with price and availability on products that receive traffic or have Merchant Center issues. Google’s product data specification requires availability to match the landing page and structured data. Its price mismatch help describes comparing submitted price with the crawled landing page or markup and possible item disapproval.

Sales and variants make the comparison tricky. Check whether the sale is active in the correct timezone, whether the landing URL preselects the advertised variant, and whether several prices appear on the same page. Google’s structured data mapping lists how feed attributes correspond to schema.org properties. A technically valid Product object can still describe the wrong variant.

How do you find the source of the mismatch?

Trace the product data pipeline: catalogue or inventory system, storefront template, structured-data generator, feed or API, and cache. Compare update timestamps. If stock changes in inventory but a cached page still says InStock, fix the cache or update path. If the page is current but the feed is old, improve feed frequency or event-driven updates. Avoid editing schema alone when the visible offer remains inconsistent.

Test the rendered page with Google’s Rich Results Test and inspect the item issue in Merchant Center. Then resubmit or resync the affected data and allow Google to reprocess it. Google’s automatic item updates documentation warns that frequent or widespread discrepancies can cause the feature to stop working. The out-of-stock products guide covers the page lifecycle behind stock changes.

Feed and markup mismatch checklist

  • Compare the same item ID, variant and landing URL across systems
  • Check visible price, sale state, currency, stock and condition
  • Inspect rendered Offer markup, not only source templates
  • Find which upstream system or cache is stale
  • Correct the source of truth and sync feed and page together
  • Validate markup and review Merchant Center item issues
  • Recheck affected products after Google processes changes

The durable fix is consistency in the product pipeline, not a one-time edit to whichever number Google flagged.

Frequently asked questions

Should the feed or the schema be the source of truth?

The actual offer shown to the shopper must be accurate, and both submitted data and markup should reflect it. Fix the system producing stale values rather than forcing one incorrect source to match another.

Will automatic item updates fix every mismatch?

No. Google says the feature is intended for sporadic price, availability and condition differences, not as a replacement for frequent feed updates. Persistent mismatches can lead to disapprovals or automatic updates being stopped.

Why does a variant have the wrong price in Google?

The feed may point to a URL showing a different selected variant, currency or sale state. Compare the exact landing URL, selected offer, visible price and structured data for the same item ID.

Can valid Product markup guarantee Merchant Center approval?

No. Valid markup is only one piece of product data quality. Google compares landing-page information with submitted data and applies Merchant Center policies and requirements separately.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows