When Google Merchant Center reports a product-price mismatch, the feed may be stale, the page may serve a different default currency, or the crawler may see a different price from a shopper. Trace the same offer through the feed, final landing page, structured data, and checkout before changing currency settings or resubmitting the catalog.
Google expects submitted price information to match the landing page and checkout, with the currency clear for the target country. A localized currency is not a safe assumption just because a store wants to enter another market. Confirm that the page presents the submitted offer and allows an eligible shopper to complete a purchase in that currency. See Google's price requirements and price mismatch guidance.
Trace one offer across four surfaces
Choose one item ID and variant. Record values and observation times so a later comparison does not mix old feed data with a new page price.
| Surface | Inspect | Evidence to keep |
|---|---|---|
| Product landing page | Variant, visible price, currency, promotion, availability | Final URL and timestamped capture |
| Structured data | price, priceCurrency, variant and offer |
Rendered HTML or JSON-LD for that URL |
| Merchant Center source | Item ID, submitted price, currency, market, last update | Item export and processing status |
| Checkout | Price, currency, taxes or fees shown before confirmation | Test journey to the last step before placing an order |
Do not compare a product page for one size or color with a feed row for another. Check redirects, location selection, cookies, and device behavior if they can change the displayed offer. If prices render after JavaScript, verify what the crawler and user can access, not just the source template.
Separate stale data from a real offer mismatch
Record the feed fetch or upload time and the time of the page check. Determine whether a promotion started or ended between them. A delay can explain a discrepancy, but it does not prove timing is the cause. Inspect item diagnostics and reproduce the same offer under the target market and language.
If the landing page, feed, structured data, and checkout disagree, identify which system owns the commercial price and which process generated the inconsistent value. Correct the upstream source or regional rule; avoid editing JSON-LD alone while the visible page and feed remain different. Reprocess the affected item and recheck current diagnostics before expanding the fix.
Check regional rules before enabling a currency
For each target country, verify the required currency, shipping and tax presentation, payment availability, and destination URL. A currency selector that changes the product page but not checkout can leave the customer with a different offer. A feed in a new currency does not create a valid market experience by itself.
Keep a separate market record for each submitted offer when requirements differ. Use current Merchant Center country and currency rules for the destination rather than copying settings from another market. If conversion or automatic currency adjustment is involved, verify the applied rate, rounding, and display behavior against the user journey.
Fix the narrowest proven cause
First confirm the relevant row and page. Then update the source responsible for the mismatch, document the before-and-after values, and let Merchant Center process the item. Do not bulk-edit prices until evidence shows a systemic mapping error. A successful resubmission can clear a data issue, but it does not guarantee approval, impressions, or sales.
Short-video script: one offer, four price checks
Opening: “Merchant Center says price mismatch? Compare the same product variant in four places before changing your feed.”
Cut 1: Show the product page: “Record the visible price, currency, variant, and time.”
Cut 2: Show a redacted feed row and structured data: “Check the item ID, price, and priceCurrency.”
Cut 3: Show checkout before order confirmation: “Does the shopper still see the same offer?”
Close: “Fix the source you can prove is wrong. A clean match resolves a consistency issue, not a promise of traffic.”
Educational carousel: diagnose a price mismatch without guesswork
- Cover: One product, one variant, four price checks.
- Landing page: Capture the final URL, visible offer, currency, and timestamp.
- Structured data: Confirm the matching variant and currency in rendered markup.
- Feed: Match the exact item ID and note the last submitted update.
- Checkout: Follow the offer to the last step before placing an order.
- Compare timing and market: Check promotions, locale, redirects, taxes, and currency rules.
- Repair: Change the narrowest verified source, reprocess, and check diagnostics again.
Field experiment thread: reproduce before changing regional settings
1/ Select one affected item and one unaffected item in the same market. Record their IDs, variants, and current diagnostics.
2/ Capture the landing-page price, feed price, structured price, checkout price, currency, locale, and observation time for each.
3/ Write a testable hypothesis, such as “the page defaults to EGP for this locale while the feed submits SAR.” Treat it as unconfirmed until reproduced.
4/ Change only the proven source for the affected item. Keep promotion, variant, and market settings stable where possible.
5/ Reprocess the item, repeat the same checks, and classify the result as resolved, still present, or inconclusive. Do not extrapolate one item to the catalog without a sample.
Tool-neutral prompt pack: compare the same product offer
Prompt 1 — Build the evidence table: “Using these redacted records [feed row, final page, rendered product data, checkout], align one product ID and variant. List price, currency, timestamp, market, and source. Flag mismatches and unknowns; do not infer a cause.”
Prompt 2 — Rank diagnostic checks: “Given the evidence [records], propose checks for stale feed timing, locale/default currency, wrong variant, promotion timing, JavaScript-rendered price, or market configuration. For each, state what evidence would confirm or reject it.”
Prompt 3 — Draft a repair record: “Summarize the confirmed source of the discrepancy, smallest correction, owner, timestamp, affected IDs, reprocessing step, and verification evidence. Mark unverified explanations as hypotheses.”
Stop-doing swipe file: currency changes that hide the mismatch
- Stop: “The target is Saudi Arabia, so submit SAR even though the page and checkout show only EGP.” Use: Validate the market-specific offer, display, and payment route first.
- Stop: Editing only structured data. Use: Trace the source that feeds both the visible offer and submitted item.
- Stop: Comparing different variants or timestamps. Use: Match ID, variant, locale, and time across the four surfaces.
- Stop: Changing the whole catalog after one alert. Use: Reproduce the discrepancy on one row and expand only if evidence shows a shared source problem.
Hook–Value–Template: document a price consistency audit
Hook: “The product ad and checkout should describe the same offer in the right currency.”
Value: “Compare one exact variant across the landing page, feed, structured data, and checkout, while recording time and market.”
Template: Product ID and variant [ ]; target country/language [ ]; feed price/currency/time [ ]; visible page price/currency/time [ ]; structured price/currency/source [ ]; checkout price/currency/time [ ]; promotion and locale [ ]; confirmed source of mismatch [or unknown]; narrow correction and owner [ ]; reprocessing and result [ ].
Official references for Merchant Center price checks
- Google Merchant Center: Price requirements
- Google Merchant Center: Price mismatch troubleshooting
- Google Merchant Center: Product data specification
- Google Search Central: Product structured data
These checks can help locate a consistency defect. They cannot guarantee approval or performance; final eligibility depends on the destination's rules, the actual offer, and the product experience.