Product feed: align your store and Merchant Center

A product feed is a structured set of item facts sent from a store to a destination such as Google Merchant Center. Its value depends on consistency: the feed, public product page, checkout and stock system must describe the same item. A feed cannot fix a missing product detail or a price that changes unexpectedly at payment.

Understand the source of each field

For one product, trace the identifier, title, description, landing-page URL, image, price, availability, variant and shipping information from the store's catalog into the submitted data source. Note which system owns each field. A title manually edited in the feed may be overwritten on the next sync if the source remains wrong.

The Google Merchant Center product data specification describes attributes and format rules that vary by product and destination. Read the current requirements for your country and product type; this guide is a workflow, not a replacement for the specification.

Use a stable identifier for each item. If a shirt has three sizes, check how each variant is represented and grouped. Changing IDs unnecessarily can make historical troubleshooting harder. Keep the chosen landing page on the verified domain and make sure it actually opens the corresponding product.

Compare feed and live page side by side

Open the feed row and product page while logged out. Check title, image, variant, price, currency and availability. Then add the item to cart and inspect the price at checkout. A feed that says “in stock” while checkout rejects the variant creates a bad customer experience and may cause eligibility issues.

Do not assume structured data automatically matches the visible page. Inspect both when a mismatch is reported. A theme may render a sale price while an app submits the regular price, or a variant URL may open the default size. Correct the source of truth rather than repeatedly patching one export file.

If you sell in multiple languages or currencies, test the specific country and URL submitted for each. The page reached from a French listing should not unexpectedly switch to an English variant with a different currency or unavailable shipping.

Treat images as product facts

Use an accessible main image that shows the product sold. Check that its URL loads publicly and matches the chosen variant where applicable. A placeholder, misleading color or image of an accessory alone can attract the wrong click. Keep image rights and source records.

Google's specification lists requirements for image_link and related image fields. Because details can change, validate current rules before a large feed update. The broader goal is that a shopper sees the same item in the listing and on the page.

Additional images can answer questions about size, texture, included parts and use. They should complement, not contradict, the main image. Review images after a supplier changes packaging or a product version.

Diagnose errors in Merchant Center

Start with the product-level issue and affected count. Separate a single SKU error from a shared catalog mapping failure. Open a few example items, reproduce their public page state and check the latest sync time. A warning shown after a recent fix may refer to data not yet processed; do not blindly change more fields.

Record the error text, item ID, affected URL, current feed value, live value, likely source system, owner and retest date. Google provides data source troubleshooting guidance. A successful upload only proves the file was received and parsed to some degree, not that every item is eligible or accurate.

Prioritize products with active demand, high value or many affected variants. Correct a common title or price mapping in the source once, then test a sample across categories. Avoid fixing hundreds of rows manually if the next synchronization will revert them.

Keep price and availability current

Stock moves with sales, returns and transfers. Price moves with promotions, taxes and currency settings. Define when the store updates the feed and how long a change takes to appear. Test a sale price and an out-of-stock transition. If the delay is too long for fast-moving items, investigate the integration or update frequency.

Automatic item updates or structured data can help with certain temporary mismatches, but they are not a license to submit stale information. The site, checkout and feed should share the same underlying facts. Keep a log of promotion start and end times and confirm the public page changes when expected.

A small feed audit table

Review ten representative products before the entire catalog. After each fix, wait for the next sync, recheck product diagnostics and complete a customer journey. Measure eligible products and useful traffic, then orders or enquiries where relevant. A healthy feed is a maintained connection between product truth and public offer.

Example of a price mismatch investigation

Imagine a fictional store whose feed shows a jacket at €79 while the public page shows €69 during a weekend promotion. Do not immediately change all feed prices. First confirm the exact variant, region, currency and promotion dates. Check whether the discount is stored in the catalog, calculated by an app or applied only in checkout. Then inspect what the structured data says and when the feed was last refreshed.

The durable fix is to make the source that controls the public price update the submitted data on time. Test one jacket through listing, page, cart and payment after the next sync. Record the result so the same issue can be diagnosed quickly during the next promotion.