Start with one affected item and its specific issue. Compare the submitted record, selected variant, visible page and checkout terms. Correct the supplying system, wait for processing and check eligibility again; a saved edit is not an approval.
A Merchant Center issue needs a product-level explanation. Changing a campaign budget cannot repair a price or an unavailable variant.
1. Record the reported issue
Open Products → Needs attention in Merchant Center and select the relevant issue. The issue details page explains the issue, affected product samples and available corrective or review actions. Download the affected-product list when you need to check a group rather than the displayed sample.
Capture the item ID, exact issue, destination, market and observation time. Open the affected item's details and identify the data source supplying it. Compare the processed fields with that source's latest submission and the actual linked product page. Group affected products by shared field or template before editing.
Use Google's product data specification to identify the relevant requirements. Missing attributes, landing-page mismatches and policy issues need different investigations.
2. Trace the item across systems
Compare the catalog record, submitted data, processed Merchant Center item and customer-facing page. Keep the market, currency and variant consistent. Open the actual submitted landing URL and continue through variant selection.
Record each field's source value, submitted value and page value. This shows whether the correction belongs in the catalog, integration mapping or storefront. Repair a shared source when several items have the same defect.
3. Check price and update timing
Google's price mismatch guidance covers agreement between submitted prices, landing pages and structured data. Compare the issue time with the price change and last successful feed update.
Inspect sale prices, dates and currency, including initial page data. Today's correct visible price does not establish what the crawler saw earlier. Check the selected variant rather than a product family's lowest displayed price.

4. Verify stock and variant identity
Test whether the affected option can actually be ordered. Google's availability documentation distinguishes in-stock, out-of-stock, preorder and backorder states; preorder and backorder require an availability date.
Compare sibling variants: individual IDs, option details, images and landing selections must describe the right item. Use genuine manufacturer identifiers where applicable. Do not invent identifiers or confuse a published page with available inventory.
5. Repair the source and recheck status
Assign the correction to the system that supplies the incorrect field. Google's automatic update guidance states that these updates do not replace regular accurate product submissions.
After the next update, inspect the processed item and issue status. Keep submitted, verified on the page and approved as separate states. Follow the issue's specified review process where applicable.
Diagnostic record: item; issue; market; variant; source/page disagreement; correction owner; update time; current status.
Use the Merchant Center checklist and Shopify SEO launch guide for the wider setup. Shopping ads decisions follow product eligibility; Shopify work fixes the storefront when the disagreement begins there.
Example: a price mismatch on one size
Imagine a shirt whose medium costs $40 and large costs $45. The submitted large variant says $45, but its link opens the medium by default at $40. Changing the feed price to $40 would conceal the wrong landing selection rather than repair the large item.
The filled comparison looks like this. All values are illustrative.
| Layer | Large shirt record | Conclusion |
|---|---|---|
| Store catalogue | SHIRT-L, size large, $45 | Source price describes large |
| Submitted item | SHIRT-L, $45, URL selecting medium | The link mapping disagrees with the item |
| Merchant Center processed item | Same submitted large ID and $45 | Processing retained the submitted price |
| Landing page | Medium selected, $40 | The customer reaches the wrong variant |
| After correction | URL selects large; visible page and cart show $45 | Live journey repaired; processed issue status still requires recheck |
Use the variant comparison sheet to retain those fields for each affected item. Open the submitted URL as a customer, confirm the selected size, inspect the visible price and continue far enough to verify the purchase terms. Correct the variant link or source mapping, then wait for the next processing cycle and inspect that same item again. Keep item ID, market, source timestamp, landing option and issue status in the record. If eligibility remains blocked, follow the actual issue’s review instructions; do not repeatedly resubmit unrelated changes.
Sources
- issue details pagesupport.google.com
- product data specificationsupport.google.com
- price mismatch guidancesupport.google.com
- availability documentationsupport.google.com
- automatic update guidancesupport.google.com
