Google AdsTo diagnose a Merchant Center price or availability mismatch, compare the same item and variant across the submitted product data, landing page, structured data and checkout. Record currency and observation time. Check variant selection and sale timing before changing values, then fix the source of the disagreement and retest the exact submitted URL.
This guide uses a fictional bottle catalog to compare four surfaces: submitted product data, the visible page, structured data and checkout. Download the Merchant Center mismatch audit. Its sample prices and product IDs are invented, so replace them with observations from your own catalog.
Capture the affected item before changing it
Start from the affected product and issue shown in Merchant Center. Save the exact item ID, destination URL, country, language, currency and observation time. If variants share a title, include the color or size that distinguishes this item.
Open the submitted URL in a fresh browser session. Do not navigate to the product from a bookmarked page and assume the result is equivalent. A variant query parameter, locale redirect or remembered selection can change the price a visitor sees.
Google's mismatch troubleshooting guide identifies inconsistent prices, availability, sale timing and variant selection as issues to inspect. Use the issue reported for the actual item to choose the checks, rather than editing the entire feed from one example.
Google Ads. Google's official troubleshooting video illustrates price discrepancies. Use the worksheet below to record the affected item and isolate where your own offer differs.
Playing loads YouTube and may use cookies.
Compare four versions of the same offer
Take observations close together in time, especially during a promotion or stock update. Record the value seen on each surface before proposing a fix. A mismatch table makes a concrete engineering ticket.
| Surface | Fictional observation | Interpretation |
|---|---|---|
| Submitted item | Green bottle, USD 34, in stock | Advertised offer |
| URL on first load | Black bottle, USD 29 | Wrong variant selected |
| Product structured data | Black bottle, USD 29 | Describes the selected variant |
| Cart after choosing green | Green bottle, USD 34 | Supports a selection problem |
Here, the first investigation is the submitted destination and its variant behavior. Lowering the green item's feed price to $29 would conceal the symptom while describing the wrong offer. Save the browser URL after redirects as well as the submitted URL.
For a promotion, add normal price, sale price, sale start and end times, and the timezone used by each system. The relevant question is whether the same offer was valid at the same moment, not whether both systems eventually displayed the same number.
Inspect structured data with the storefront owner
Ask the developer to inspect the product offer data returned for the affected URL. Record the product or variant identifier, price, currency and availability. A correct visible page with stale offer markup is a different problem from an incorrect default variant.
Google's automatic item updates documentation explains how supported product information can be taken from the website, including structured data. Automatic updates are a safeguard against some discrepancies; they do not replace a regular, accurate feed.
Avoid adding a second competing Product block simply to satisfy a checker. First identify which storefront feature or integration owns the existing offer data. The fix should update the correct source and be checked on the affected variant and at least one unaffected sibling.
Repair the source that created the disagreement
Assign the issue to the responsible layer. A feed export with an outdated price belongs with the catalog pipeline. A URL that drops a variant parameter belongs with storefront routing. A sale price that expires in one system earlier than another needs a schedule correction.
For stock, inspect the mapping from inventory state to the submitted availability value. Google's availability specification defines the supported values and their conditions. Do not label a preorder as immediately available just to remove an issue.
Document the proposed change, owner and rollback information. Reproduce the mismatch using a test item or controlled environment where possible. The article's sheet is an audit record, not a bulk update script; a single bad row is insufficient evidence for changing an entire catalog.
Retest the item and preserve the evidence
After the source is corrected and the updated product data is processed, reopen the exact submitted URL. Repeat the variant, price, currency, availability and cart checks. Add the observation timestamp and current Merchant Center issue state to the same row.
If the issue persists, compare what changed rather than repeatedly requesting review with no new evidence. The visible page may be fixed while a feed refresh is still pending, or another market may still serve an inconsistent offer. Keep those states separate in the handoff.
Once the product is consistent, use the Google Ads launch preflight to check its destination and measurement. Then use Performance Max channel reporting to review delivery with the corrected catalog context. Resolving a product-data issue does not itself demonstrate an improvement in campaign performance.
Sources checked October 15, 2026. The bottle catalog is a worked diagnostic example, not a report from a merchant account.