Local product promise path from stock note to review reply

Product feed fields and store page copy should agree before a local listing sends customers to a product page.

Google Merchant Center product data uses fields such as product identifiers, titles, descriptions, prices, links, and availability to understand and display products. Google Search merchant listing structured data can also expose details like price, availability, shipping, and returns. If the feed says one thing and the store page says another, the customer may not know which promise is current.

The mismatch usually appears in small places: a feed says in stock while the page says preorder, the title names a bundle while the page sells a single item, the image shows a color that is no longer available, the price changed on the page but not in the feed, or the branch inventory is copied from a different location. Each mismatch creates support work and can reduce trust.

A local listing check should compare title, variant, image, price, availability, pickup method, return note, and last checked date. It should also include the page customers actually land on, not only the admin view or spreadsheet. If a store uses multiple channels, the page should have a clear source of truth for staff.

The goal is simple: a customer who sees the listing, opens the page, and visits the store should encounter the same product promise at every step.

Product feed fields and store page copy should agree before a local listing goes live

// COMMENTS

ON THIS PAGE