Google Merchant Center issue
Price mismatch
The price Google reads for an offer may differ from the price submitted in Merchant Center.
Google’s source: Official Merchant Center guidance ↗
What Google is reporting
Google expects the submitted price and currency to match the purchasable offer on the landing page, including its active sale price.
Why this happens
- A sale starts or ends before the product data updates.
- The landing page selects a different variant, currency, or location.
- Structured data and the visible price disagree.
These are possibilities, not a confirmed cause for your account.
Does it affect eligibility?
Google may warn or preemptively disapprove affected products when prices conflict. Use the reported status rather than inferring that all products are blocked.
How to diagnose it
- Read Google's issue details for a specific offer, destination, and country.
- Compare submitted price and currency against the exact variant's visible and structured price.
- Check sale dates, redirects, locale selection, and checkout price.
How to fix it
- Update the store or product source so the purchasable offer matches its submitted price.
- Keep sale timing and structured data synchronized.
- Resubmit or wait for recrawl, then verify Google's latest status.
What CommerceVigil checks
For supported issues, CommerceVigil may compare a Merchant price with readable landing-page structured price. Different variants or inaccessible pages can make the result inconclusive.
Google’s reported issue remains authoritative. AI explanations are separate from deterministic evidence checks.
Frequently asked questions
Can a sale trigger a mismatch?
Yes, when the active sale price and the submitted data diverge.
Does CommerceVigil change prices?
No. Its Merchant connection is read-only.