Match each feed row to the selected item
Compare each feed row with the exact selected variant’s live price, stock and destination. Correct the source and update path behind a mismatch rather than patching a generated export once. This sample audit checks product-data consistency; account and destination eligibility require their own evidence before paid traffic is evaluated.
Worked example — illustrative data.
| Item | Mismatch specimen | Proposed correction |
|---|---|---|
| ARC-BR | Feed USD 79; page USD 85 | Confirm canonical price source and update path |
| ARC-BK | Feed in stock; selected variant unavailable | Reconcile exact variant inventory |
| ARC-WH | Landing URL returns an error | Restore valid product or remove invalid row |
Take a dated feed export and compare each sampled item with its exact landing URL and selected variant. Include currency, identifiers and image links in the working sheet where relevant to the destination specification. Record which system owns each attribute and when updates reach the feed. Recheck after correcting the source rather than patching a generated value that the next sync will overwrite. Use a small controlled sample before auditing the full catalog.
Parent-level stock can hide an unavailable variant
One parent product can contain an available black variant and unavailable brass variant. Matching only the parent name can hide the error, so compare the item identifier and landing selection together.
Resolve known product-data mismatches before sending visitors to the item. Verify destination eligibility and reporting separately before deciding whether paid traffic is appropriate.
Continue with Guides for stores, software teams and local businesses, eCommerce SEO services and Validate a BigCommerce catalog import.
For Merchant product-data requirements, see Google product-data specification (checked November 2026).