1. Reproduce the mismatch the way Google sees it
Open the flagged product's landing page in a private window, in the target country and currency if you can, and compare three numbers: the visible price on the page, the price in the page's structured data (microdata or JSON-LD), and the price in your latest feed. A mismatch in any pair triggers the error. Note which pair disagrees – that tells you which system to fix.
2. Stale feeds and sale pricing
The most common cause is timing. Your store runs a sale, the site updates instantly, and the feed still carries yesterday's price until the next scheduled fetch – or the reverse, where the feed picks up the sale price and the page shows it only to logged-in customers. Align feed generation with price changes: regenerate on sale start and end, not just on a nightly schedule. When you run promotions, use the sale_price and sale_price_effective_date attributes properly instead of overwriting the base price, so both systems describe the same offer.
3. Tax, currency, and variant traps
If your store displays prices excluding tax but your feed includes it (or the other way round), every product mismatches. Pick the convention your target country requires and apply it in both places. Multi-currency setups mismatch when the crawler lands in a different currency than the feed targets – make sure the URL in the feed resolves to the same currency the feed declares. Variants are another classic: the feed lists the cheapest variant's price while the landing page defaults to a larger size. The feed price must match the variant the link actually lands on.
4. Structured data that disagrees with the page
Google reads your structured data as part of the comparison. Plugins that output a cached or pre-discount price into the schema while the visible price shows the discount will mismatch even when the feed is perfect. After any pricing change on the site, view the page source and confirm the schema price matches what a customer sees. Enable automatic item updates in Merchant Center as a safety net – it lets Google correct price and availability from your structured data between feed uploads – but treat it as a net, not the fix.
5. Verify across one full cycle
After fixing the source, upload or fetch the feed and wait for a full processing cycle before judging. Then re-check Diagnostics and spot-check the specific items that were flagged. If mismatches return on the same products, the generator is still producing a different price than the storefront – compare a raw feed row against the page for one SKU, field by field, until the divergence shows itself.
6. Prevent the recurrence
Price mismatch is a process problem with a process fix: one source of truth for price, feed regeneration tied to price changes, and a weekly Diagnostics check so a drift is caught at ten products instead of ten thousand. Stores that fold the check into weekly operations stop seeing this error class almost entirely.
Price mismatches eating your listings?
We run structured Merchant Center feed diagnostics: audit, root-cause mapping, remediation, and verification.
Related: Diagnosing Merchant Center feed errors · Fixing GTIN errors · Merchant Center feed diagnostics