A product page incident can mislead a customer even when the rest of the store is healthy. Examples include the wrong price, stale availability, an incorrect variant, a broken buy button, a missing image, or a page that no longer loads. Record the customer-visible state first, contain the misleading path, and reconcile every system that supplies the page before reopening it.
Open one incident timeline
Record the discovery time, product identifier, variant, URL, market, currency, device, browser, account state, and exact symptom. Save the page response, screenshot, selected variant, cart result, feed value, structured-data result, and most recent catalog or theme change. Keep customer information out of the record. If an order was affected, reference its internal identifier rather than copying personal or payment data.
Contain the smallest unsafe path
If the price, availability, identity, or purchase action is materially wrong, pause the affected offer or remove its purchase action through the supported commerce controls. Avoid deleting the product or URL before evidence and redirects are understood. If only one variant or market is affected, contain that boundary rather than disabling the whole catalog. Record who approved the change and how to reverse it.
Google's Merchant Center landing-page requirements say a submitted page should show the specific product and key details such as title, image, price, currency, availability, and a buy button. Google also says those details should match the submitted product data and remain consistent during page load. These requirements are useful comparison points even when the incident was found through another channel.
Reconcile the sources of truth
Compare the commerce platform record, inventory system, pricing rules, promotions, product feed, page markup, cache or CDN, and checkout. Use one row per variant and market. Note the expected value, actual value, source system, last update time, and owner. Do not assume the product page is authoritative merely because it is public; a cached page may lag the catalog, while a feed or checkout can also be wrong.
Google's product data specification requires submitted availability to match the landing page, checkout, and structured data. It likewise says submitted price and currency should match the landing page, structured data, and checkout. Treat mismatches as separate defects so the repair does not update one surface while leaving another inconsistent.
Repair and test one variant
Make the smallest reversible correction in the true source system. Purge or refresh caches only through documented controls. Then test the canonical URL in a clean browser and on mobile: select the exact variant, confirm title and image, read the price and currency, verify availability, add the item to the cart, and continue far enough to confirm the same values at checkout without placing an order. Test structured data and feed diagnostics separately.
Google's approval guidance says an unavailable landing page can cause product disapproval and recommends keeping price and availability current, including through structured data and automatic item updates where appropriate. Automatic updates are a safeguard, not permission to leave the store's own data inconsistent.
Address affected customers carefully
Identify orders or sessions within the confirmed incident window using the minimum data necessary. Escalate refunds, cancellations, legal disclosures, or price-honoring decisions to the authorized business owner; technical staff should not invent policy. Publish a customer notice only when approved and when it helps an affected person take action.
Close with a cross-system check
Record the root cause or unknown, affected products and markets, containment period, corrected source, cache state, page result, feed result, structured-data result, checkout result, and owner of follow-up. Monitor the page and merchant diagnostics through at least one normal update cycle. A resolved incident has consistent facts across catalog, page, feed, markup, cart, and checkout—not merely a screenshot that looks right.
Sources
- About landing page requirements — Google Merchant Center Help
- Product data specification — Google Merchant Center Help
- Tips to help your products stay approved — Google Merchant Center Help