E-commerce

Why Google Shows the Wrong Price or Image for Your Products

Illustration representing merchant center

A store owner fixes a pricing error, checks the product page, confirms it's correct, and then watches Google Shopping keep showing the old price for another week anyway. Or an old product photo, one that was swapped out months ago, keeps turning up in a Google Images result or an ad, long after the live site stopped using it. Neither of these is really a bug in your store. It's a side effect of something Google does that most store owners have never heard explained clearly: it keeps its own persistent memory of your products, built up over time from multiple sources, and that memory doesn't update the instant your feed does.

How Google Builds Its Hidden Product Memory

Google doesn't just read your current Merchant Center feed and display it. It independently crawls your product pages, reads your schema markup, and keeps a running history of prices and images it's seen over time, sometimes stitching data from different sources together. One documented example showed Google displaying "Was £474, now £355" on a listing, built by combining a schema label mentioning "sale," HTML copy saying "Now," and a feed price from three months earlier, none of which the merchant had set up as an intentional current promotion. Google assembled a sale badge nobody asked for, out of signals that individually looked harmless.

Images work the same way. Google indexes your product photos separately from whatever you currently submit in your feed, and without an explicit 404 response telling it an image is gone, the old file can keep surfacing in Shopping results and ads indefinitely, including copies that exist on marketplace listings or other sites you don't directly control.

Why PrestaShop and OpenCart Stores Experience This Issue

If you're running PrestaShop or OpenCart, this issue tends to show up in a specific, recurring way: a sale ends, the price reverts in your store and in your feed, but the product page's schema markup, often generated by a theme or plugin that doesn't get revisited after a sale wraps up, still technically contains "sale" language or an old discounted price buried in structured data that nobody manually checks.

Google's crawler doesn't know the sale is over just because the visible price changed; it's reading the same signals it always reads, and if the schema wasn't cleaned up, the mismatch persists until Google happens to recrawl and reconcile it, which per Google's own current guidance can take anywhere from a few days to several weeks depending on your site's crawl priority.

Understanding Cross-Platform Feed Bleed

One further wrinkle, flagged by structured-data consultant Jarno van Driel, is less documented but consistent with what store owners have observed in practice: major marketplaces appear to exchange feed data with each other through their own APIs, informally, not as a publicly specified integration. A mistake in your Google Merchant Center feed can apparently follow through and cause an ad rejection on a completely different platform, like Amazon, even though you never submitted anything to Amazon with that specific error. If you sell across more than one channel and start seeing unexplained rejections on a platform you didn't touch, it's worth checking whether the same underlying product data recently had an issue somewhere else first.

Audit Steps to Check What Merchant Center Sees

Merchant Center has a specific section, "Information found on your site," under each product's diagnostics, that shows exactly what Google's crawler currently has on file for that listing, separate from what you submitted in your feed. This is the single most useful place to start, because it tells you directly whether the mismatch is a feed problem (your submitted data is wrong) or a crawl problem (Google's independent read of your page is stale or wrong).

Price Discrepancy Checks:

  • Inspect Source Code: Right-click the live product page in Chrome, choose "View Page Source," and search for "price" to see exactly what value is sitting in your structured data markup, not just what's visibly displayed to a shopper.
  • Verify Signal Parity: Confirm the HTML price, the schema price, and the Merchant Center feed price all match exactly. Even a formatting difference can register as a mismatch.
  • Purge Expired Promos: Remove "Sale" language from schema markup the moment a promotion ends, not whenever someone next happens to edit that product.

Orphaned Image Checks:

  • Serve Proper HTTP Status: When a product image is genuinely retired, serve an actual 404 for the old file rather than quietly leaving it sitting on your server or CDN. Without that signal, Google has no reason to stop treating it as current.
  • Reverse Image Audit: Search the old image's filename directly in Google Images periodically to spot where an outdated photo is still circulating, including on marketplace listings you don't control directly.

Business and Trust Impact of Stale Data

Beyond the annoyance of an inaccurate listing, this has real downstream effects that are easy to underestimate: a misleading sale badge your store never intended erodes customer trust the moment a shopper clicks through and finds a different price, and an outdated product image in an ad is money spent driving traffic to a listing that no longer matches what you're selling. As more shopping discovery shifts toward AI-driven tools that pull product data automatically rather than a human double-checking a listing by eye, an inaccurate hidden data layer becomes a problem that compounds silently rather than one a human reviewer would likely catch and correct.

Workflow Habits for Preventing Data Mismatches

The single biggest reason these mismatches linger for small stores isn't a lack of technical knowledge, it's that pricing, product content, and ad management often sit with three different people, or the same overworked one wearing three different hats, none of whom are specifically watching the schema markup after a sale ends. Building a simple habit, checking the "Information found on your site" panel whenever a price changes meaningfully, costs a few minutes and catches most of this before it becomes a customer-facing problem rather than an internal one.

Expected Timelines for Google Recrawls

Once you've corrected a schema mismatch or served a proper 404 for a retired image, patience is still required. Google needs to recrawl the specific page before anything changes on its end, and per Google's own recent guidance, a known URL refresh runs roughly 30 days typically, with sitemap-driven recrawls happening closer to 24 hours to two weeks. If a disapproved product in Merchant Center shows an error that matches a fix you already made, give it a few days before concluding the fix didn't work. Resubmitting the same feed repeatedly in that window doesn't speed anything up, it just adds noise to your account's change history without changing when Google revisits the page.

Multi-Channel Inventory Management Strategies

If the cross-platform feed bleed described above is a real pattern for your store, specifically an error on one platform showing up as a rejection on another, the practical defense is keeping a single source of truth for price and availability data and pushing identical values to every channel from that one place, rather than updating each platform's dashboard separately by hand.

Spreadsheet-based feed management tools exist at every price point, including free ones for a small catalog, and the core value they offer isn't automation for its own sake, it's eliminating the chance that your storefront price, your Merchant Center feed, and your actual checkout price ever quietly drift apart from each other. Even a simple shared product spreadsheet, checked before any price change goes out anywhere, closes most of this gap for a small store that isn't ready for dedicated feed-management software yet.

Summary Checklist for Store Owners

Checking the "Information found on your site" panel in Merchant Center costs about two minutes per product and tells you directly whether Google's read of your listing currently matches reality. Make that check a standard step whenever a sale ends or a product photo changes, not something you only think to do after a customer complains about a price that doesn't match what they clicked through on. The hidden data layer isn't going away, and treating it as background Google behavior you can't influence is the one approach guaranteed not to fix it.

Further reading: Google Search Central: Product structured data.