A Product Feed Checklist for Google Shopping

Identify whether the feed comes from a platform integration, a scheduled data source, a file or another supported connection. Record who owns it and which system is considered authoritative for price, availability and product identifiers.

This matters when someone edits a field directly in one system. A later sync may replace that change, or the website may continue showing a different value. The team should know where an approved correction belongs before making it.

Google’s product data specification describes the attributes and requirements used for product submissions. Review the applicable requirements for your catalogue and target destination rather than copying a sample intended for a different product category.

For representative items, inspect the title, description, image, price, availability and relevant identifiers. If a field is missing or disputed, investigate the actual product information. Do not invent an identifier or a product claim simply to fill a required-looking field.

Products that differ by size, colour or another meaningful attribute need data that accurately identifies the submitted version. Check how the integration represents those options and how a customer recognises the matching version after clicking.

Use a sample with several configurations during the review. An attractive generic image may not communicate the specific colour being advertised. Where the destination opens a particular configuration, confirm that the selected option, displayed price and availability make sense together.

Google Merchant Center publishes requirements for product landing pages. The page should present the corresponding product offer clearly and consistently. Review the actual destination on a phone as well as a desktop, including any market or currency behaviour.

Check that popups, account gates or broken product selection do not prevent an ordinary visitor from understanding the offer. The feed can be technically well formed while the page remains difficult to use. Treat catalogue accuracy and landing page usability as connected checks.

Compare shipping information and any promotion shown in the advertising with the approved offer. The relevant settings can involve more than the product feed, so identify which account or platform controls each part. Record the owner of corrections rather than passing the same issue between teams.

If an offer changes, include the start and end conditions in the change plan. Verify the resulting product page, cart behaviour and submitted data after the change. A sale label that remains in one place after it expires elsewhere creates unnecessary confusion.

Account diagnostics can identify issues affecting product eligibility. Group repeated problems by cause, such as missing information from the source catalogue or a template inconsistency on the website. Include representative products and the exact observation for each issue.

Work through this release checklist:

• The data source and field owners are documented.
• Product identifiers and variant attributes reflect real items.
• Images and titles help identify the submitted product.
• Price, currency and availability agree with the destination.
• Delivery and promotion information follow the approved offer.
• Diagnostics are reviewed after the correction has had time to process.

Keep data quality separate from campaign performance claims. A clean submission supports a more reliable campaign foundation, but it does not guarantee that a particular product will receive traffic or produce a profitable result. Review campaign choices using their own evidence once the catalogue is dependable.