seo

Product data drift: when Merchant Center, structured data, and PDP copy conflict—and rich results vanish

Thu Apr 09 2026 • Nigel Abramow

A merchandiser changes a title to add a seasonal hook. The PPC team shortens names in the feed to fit ads. An inventory app flips a variant to out of stock. None of these edits seem major, yet a week later product stars and price chips disappear from Google’s results. Click‑through drops. Merchant Center shows “Mismatched value [price]” and a handful of disapprovals. Nothing broke, but something drifted.

Product data drift is what happens when three views of the same item stop lining up: your Merchant Center feed, the structured data on the PDP, and the copy the shopper can see. Search depends on those sources agreeing. When they conflict, rich results become ineligible, free listings lose visibility, and Shopping campaigns start burning budget on shaky ground.

The problem

Google expects your product markup to describe what’s on the page, and your feed to describe the same item with the same core attributes. In practice, many stores run multiple titles, prices and availability states for the same SKU. Google tries to reconcile this and will even use “automatic item updates” to correct obvious price and stock differences, but it withdraws enhancements when the signals can’t be trusted. The visible symptom is simple: fewer impressions with rich attributes, lower CTR, and Merchant Center warnings that don’t map cleanly to a single cause.

Why it happens

Teams rarely intend to create conflicting data. It emerges from normal merchandising, platform defaults, and tooling that layers new data on top of old templates. A few common patterns account for most cases.

Multiple sources of truth

Once feeds and on‑page markup stop being generated by the same logic, drift starts. Shopify themes, review apps and SEO plugins often inject their own schema while your feed is built elsewhere.

• The theme outputs Product JSON‑LD, while a reviews app adds its own Product + AggregateRating block

• The feed adds brand to titles while PDP H1 and structured data use a shorter name

• A supplemental feed overwrites availability rules that disagree with PDP “backorder” messaging

This shows up as duplicate or conflicting markup in the Rich Results Test, and “mismatched value” diagnostics in Merchant Center.

Variant versus parent confusion

Google wants the data to point to the same thing. If the feed lists a specific variant URL, but your structured data describes the parent product, Google sees two items.

• Feed URL includes a variant query parameter, while canonical points to the parent PDP

• Structured data aggregates offers, but the feed sends a single variant price

• PDP price selector shows a variant with tax, while the feed uses the parent’s base price without tax

Expect price and availability mismatches, and sometimes disapprovals for “inaccurate landing page.”

Asynchronous updates and caching

Even when the logic matches, timing can be off. Feeds update on a schedule. PDPs and JSON‑LD are generated per request, then cached.

• Scheduled fetch picks up old prices while a flash sale goes live on site

• CDN caches a PDP and its JSON‑LD for hours after stock changes

• Content API updates queue behind rate limits during catalog imports

Google will use automatic item updates to patch price and stock temporarily, but repeated drift erodes trust and suppresses rich results.

Tax, currency and region rules

Cross‑border setups and display settings introduce subtle differences that Google treats as material.

• PDP shows tax‑inclusive pricing, feed lists tax‑exclusive pricing

• Currency selectors show converted prices, but structured data is hard‑coded to the default currency

• Magento store views localize availability labels that don’t map to Google’s required enumerations

Rich results require exact matches on price, currency and availability using Google’s accepted values.

Titles, descriptions and merchandising edits

Copy changes done for brand reasons can accidentally break alignment.

• Merchant Center appends brand and size to titles for Shopping, while PDP titles remove size for readability

• SEO teams rewrite meta descriptions and on‑page copy without updating schema “description”

• Feed rules normalize casing; the PDP uses styling and emojis that are stripped in the feed

Google doesn’t need character‑for‑character matches, but material differences in meaning, attributes or claims trigger warnings and reduced eligibility.

Reviews and ratings inconsistency

Review snippets are sensitive to provenance and values.

• PDP shows 4.8 from 1,264 reviews, but the Product Ratings feed lists 4.6 from 1,100 after moderation

• A third‑party aggregator injects rating markup that doesn’t match visible review counts

• Syndicated reviews violate Google’s policies, causing ratings to be dropped entirely

When ratings disagree, Google often removes stars from search and free listings for the affected items.

App and plugin collisions

On Shopify, Magento and WordPress, it’s easy to add a second schema layer without noticing.

• WooCommerce microdata lives in templates while an SEO plugin outputs JSON‑LD with different values

• Shopify theme schema uses selected_or_first_available_variant, but a separate “rich snippets” app hard‑codes the first variant’s price

• Magento modules output both microdata and JSON‑LD for the same product with diverging availability

Duplicate schemas with conflicting values reduce confidence and eligibility.

What it means commercially

Losing product enhancements in organic search isn’t cosmetic. Price, availability and rating chips raise CTR on product queries because they answer intent before the click. When those elements vanish, traffic shifts to advertisers and marketplaces that still show them. In paid, mismatches push items into “limited performance” states or disapprovals, shrinking inventory in Performance Max. The budget that remains often works harder to win a click without the familiar stars and price anchor, raising CPCs and CAC. There’s also a trust cost: when an ad promises a price that the PDP doesn’t match, bounce rates rise and repeat visits fall. Across a quarter, these small gaps add up to real revenue left on the table.

What to check first

Before rewriting templates or swapping apps, isolate one SKU and follow the data from search result to cart. The aim is to confirm whether Google is seeing one coherent product or three partial versions.

• Pick a live product with recent impressions and run its URL in Google’s Rich Results Test

• In the test, confirm there is one Product entity, not multiple overlapping blocks

• Compare structured data fields (name, price, availability, GTIN, brand) to the visible PDP content

• Open Merchant Center Diagnostics for the same item and review warnings tied to title, price and availability

• Check which URL the feed uses and whether it includes a variant parameter that matches PDP selection

• View source to ensure currency and price in JSON‑LD match what the shopper sees with tax settings applied

• Verify availability uses Google’s accepted values (InStock, OutOfStock, PreOrder) and matches PDP text

• If ratings are present, match average rating and review count to any Product Ratings feed values

• Search the source for additional Product or AggregateRating blocks added by apps or plugins

• For Shopify, confirm only one system outputs schema and that it references the selected variant

• For Magento, test another store view to catch localization and tax differences in markup

• For WooCommerce, disable overlapping SEO schema for a test and keep WooCommerce’s own product schema

Once a single product is clean, roll the fixes into templates and feed rules so the alignment is generated, not hand‑maintained.

Final thought

Data drift isn’t a penalty issue; it’s a coherence issue. The web page, the feed and the shopper view need to describe the same item with the same facts at the same time. If that sounds basic, that’s the point. Most fixes are unglamorous: pick one schema source, anchor titles, normalize tax display, and make sure the feed and PDP talk about the same variant. When those basics hold, rich results tend to come back and stay.

Where to go from here

If your product stars, prices or free listings have faded and the diagnostics feel contradictory, start with one SKU and line up the three data sources. If you need a second pair of eyes, we can audit schema, feed logic and platform settings together, fix the collisions, and wire updates so price and stock stay in sync. It’s quieter work than a redesign, but it restores the signals that make search and Shopping efficient.