WEBSITE PLANNING

Check That Product Data Matches the Storefront

Audit one exact product variant across its page, structured data and Merchant Center submission before expanding the check to your catalog.

Choose a record you can identify everywhere

Start with one genuine sellable variant and its stable identifier. Record the exact landing link rather than the general store homepage. Compare title, selected option, price, currency, availability and image across the visible page, structured data and Merchant Center submission where used. A discrepancy is easier to resolve when the audit names one record and one field instead of reporting that the whole feed looks wrong.

A fictional mismatch example

A demonstration row says variant SAMPLE-BLUE is unavailable on the product page but in stock in the submitted data. Another row says the page shows the green image even though the link selects blue. These are invented audit findings, not claims about a client store. Each finding needs a source value, observed value, responsible system and correction owner. Do not correct only the export if an upstream record will overwrite it again.

Use the current field definitions

Google’s product-data specification describes attributes and requirements, including variant data. Consult the applicable definitions for the actual product and market rather than guessing identifiers. A syntactically valid file can still disagree with the customer-facing page. Structured data and feeds should express supported business facts, not invented stock or product claims.

Verify the correction survives a refresh

After a controlled change, check the exact variant again and note when each system updates. Review a second variant to make sure the correction did not flatten differences across the product family. Keep unavailable reporting separate from a confirmed pass. Then expand the same worksheet to the catalog in manageable batches. North Front Digital can discuss the data flow and scope through the project inquiry form.