Changed your product price, but Google still shows the old one?

AISEO Site · Prepared 10 September 2026 · Updated 10 October 2026

You finish setting up a sale. Your store shows the new price. Then a customer sends you a screenshot: Google is showing something different.

Before rewriting the product description or uploading the same file again, check where the disagreement starts. The price shoppers see, the product details your website sends to search engines, and the record supplied to Google may not have updated together. Sometimes your information is already correct and the destination has not refreshed yet.

This guide helps store owners and ecommerce managers find the right thing to fix and avoid repeating the problem at the next sale. The same checks are useful when investigating an incorrect product detail in an AI shopping answer.

First, make sure you are comparing the same offer

A smaller size, another currency or a members-only discount can make two legitimate prices look like a mistake.

Open the exact product link shown with the incorrect price. Check the selected size or color, currency, country, quantity and discount conditions. Use a signed-out browser so a personal account discount does not confuse the comparison. Note when you saw each price.

If those details differ, resolve that difference before changing your prices. A result linking to the cheapest size should not be compared with a more expensive size selected on your own screen.

If the link opens a different color or size, use our guide to incorrect product variants in Google Shopping to trace the selected item from the listing to the cart before changing its price.

If the offers really are equivalent, check the following three places.

Trace the offer through four checkpoints

1. Establish the approved price and sale window

Find the record that authorizes the offer: the product team's price, currency, eligible market, variant and promotion start and end. Write down the time and timezone. This is the reference for the investigation. A majority vote between three stale copies cannot tell you the intended price.

Check whether the offer is public, conditional on membership, or dependent on a coupon. Do not compare a conditional discount with the ordinary offer and then “fix” every system to the discounted amount. Google's price requirements apply to the submitted offer and its landing-page and checkout experience.

2. Follow the anonymous page into the cart

Open the submitted landing URL in a signed-out session, with its variant parameters intact. Record the final URL, selected item and displayed currency. Add that item to the cart without completing a purchase. Compare the item price and discount conditions; keep shipping and other charges labelled separately.

If the page starts at the sale price but the cart switches to another SKU or an expired price, stop here. Give the storefront team the URL and the exact selection that reproduces the mismatch. Editing a feed cannot correct the customer's cart.

3. Inspect the offer embedded in that same page

Use the rendered page and a structured-data test to find the Product and Offer for the selected variant. Check price, priceCurrency, availability and the offer URL. Ask which template or integration writes those fields. Multiple plugins can leave contradictory offers even when the visible price is correct.

A valid parser result is not enough: the values must describe what this shopper can buy. Google's structured-data guidance requires agreement with customer-facing data. Its automatic updates can help with some discrepancies, but do not replace a maintained source.

4. Check the processed destination item

In Merchant Center open the exact item ID for the same market and variant. Compare the effective price and sale fields, landing link and availability with the approved offer. Inspect the supplying data source, last successful processing and any item issue. An export file on your laptop is evidence of a produced file, not a processed destination record.

If a source rule, supplementary source or scheduled connector overwrites a value, repair that writer rather than making a one-off destination edit that the next run will undo. Save the original and corrected item values and the processing time. Different downstream displays may update later; a source correction is not proof of their refresh.

Worked example: the $79 sale and the $99 offer

This teaching example uses a backpack normally priced at $99 and a public $79 promotion. It is not a customer case. The approved promotion is active for the exact variant and market. The page and cart show $79; Merchant Center's processed sale value is $79; the page's embedded Offer still shows $99.

The failing checkpoint is the page's offer output. Ask the developer to trace the selected variant's promotion into that output and its cache. Re-run the same URL after the fix, then check the regular and sale fields in the destination. Do not change the approved price merely because one copy disagrees.

Now change one fact: the promotion ended an hour ago. The correct price may be $99, and the visible page and destination may be stale instead. Check the approved window before choosing the repair. At both sale boundaries, use timestamps rather than screenshots taken at different times as if they were simultaneous.

Choose your next step

Send a repair ticket the next person can reproduce

Include the submitted URL, final URL, item ID, selected variant, market, currency, approved offer and observation times. Attach the external display, page/cart comparison, relevant Offer values and processed item status. Share account evidence privately with the people assigned to the repair.

Name the first failing checkpoint and its owner. A useful request is “this variant's active sale is missing from the Product template; reproduce with this URL and verify these four values after the fix.” “Google price is wrong” leaves the next person to repeat the whole investigation.

Verify the fix and the next sale boundary

After the source is corrected, repeat the same anonymous page, cart, markup and destination checks. Save before and after values plus the destination processing result. If current records agree and the external result is stale, preserve its URL and timestamp and monitor the relevant destination; do not repeatedly alter correct data.

For prevention, test a full-price item, an active sale, a recently ended sale, an unavailable item and a multi-variant product. Include the moment a promotion starts and ends. This is a focused sample, not proof that the entire catalog is consistent. If it reveals a shared template or connector error, expand checks to the affected group.

What this means for AI shopping

When a shopper asks an AI assistant for a recommendation, a persuasive description is not a substitute for reliable product facts. If the answer shows an incorrect price, save the answer and its linked source, then run the same checks for the exact offer.

Once the basics agree, improve the information that helps a customer choose: measured dimensions, compatibility, care instructions, delivery conditions and meaningful limitations. For a backpack, “Will my laptop fit?” deserves actual compartment measurements, not “perfect for every professional.”

Do not invent missing specifications from a photograph. Get the approved details from the manufacturer or your product team. Accurate information helps you present a coherent offer; it does not guarantee that an AI service will recommend it.

Questions store owners ask

Will requesting indexing fix a wrong price?

Not by itself. First correct the information responsible for the mismatch. A request to recrawl a page is not the same as updating a Merchant Center record, and neither means the result will change immediately. Google's merchant-listing documentation explains testing and recrawling after changes.

How quickly will Google show the corrected price?

There is no single reliable deadline for every display. It depends on where the old information appears and which update or processing step is involved. Check the affected product's status and keep a dated record of the correction. Avoid promising a refresh time you cannot verify.

Do I need a developer for the first check?

Usually you can compare the live page, selected product and Merchant Center record yourself. Bring in technical help when embedded product details are wrong, updates repeatedly fail, or you cannot tell which system controls the offer.

Should I replace my ecommerce platform?

Not just because of one mismatch. A template, plugin, sale rule or connection may be the issue. Identify the failing step first; then decide whether a configuration fix, integration change or broader project is justified.

Keep the correction record

Keep one offer record with the expected values, original mismatch, responsible source, verified correction and any downstream display still awaiting refresh. Use the variant guide when identity differs and the Merchant Center visibility guide when data is correct but impressions are missing.

AISEO Site's current subscription reads Search Console performance and provides AI analysis and a daily email. It does not repair product feeds or manage Merchant Center. Use your ecommerce team or an authorized integration owner for the changes described here.

Prepared by AISEO Site with AI assistance. Updated 10 October 2026. The price example is illustrative; technical references are linked in the relevant steps.