When to run this checklist
Run it when a store first connects a Product FeedA structured file of a store's products, prices and availability used to build shopping and catalogue ads. to Google Merchant Center, and before any campaign is allowed to use it. Run it again after a replatform, because the new platform's feed usually maps attributes differently; after a change of feed tool or app, for the same reason; and before launching in a new country, since shipping, currency, language and returns are set per country and a feed that is right for one market can be wrong for the next.
The person who manages the feed runs the list, with help from whoever owns the online store for the accuracy group and from the paid search manager for the review and ownership group. On a large catalogue, check the product data lines against a sample from every category and brand rather than the first page of products, because errors cluster in the categories nobody looked at.
Before you start
- Admin access to Merchant Center and to the site's domain verification method.
- The site's shipping and returns policies, by country, as customers see them at checkout. The guide to setting and keeping delivery promises explains how operations set those promises so the feed, the pages and the checkout can state the same one.
- The feed file or the platform connection, and its attribute mapping.
- A sample of products from every category and brand, including variants and items on sale.
- The Google Ads account the feed will serve, with admin access to link it.
- A view of margin, season and bestseller status, for the custom labels.
The checklist
The groups follow the order a feed is built: the account it sits in, the product data it carries, whether that data stays accurate, and the review that clears it to serve. Nothing in the review group is ticked until the groups above it pass.
Account
Product data
Accuracy
Review and ownership
Where each check is explained
The widget keeps each line short enough to tick; the reasoning lives in the guides. Each check links to the page that explains it.
| Check | Explained in |
|---|---|
| Website verified and claimed | Product feeds and Merchant Center |
| Shipping and returns match the site | Product feeds and Merchant Center |
| Linked to Google Ads | Performance Max structure |
| Every required attribute | Product feeds and Merchant Center |
| GTINs and brand | Merchant Center missing product identifiers |
| Titles lead with search terms | Category and product page SEO |
| Category and product type | Product feeds and Merchant Center |
| Clear images without overlays | Product feeds and Merchant Center |
| Landing page price and availability match | Merchant Center products not updating |
| Fetch schedule follows changes | Merchant Center products not updating |
| Product structured data on templates | Structured data and schema |
| Diagnostics reviewed before use | Google Shopping products not showing |
| Custom labels | Performance Max structure |
| Feed owner and change route | Marketing data operations and taxonomies |
If an item fails
No campaign uses the feed until the account group passes. An unverified or unclaimed website, or shipping settings that disagree with checkout, can hold back the whole account, not just a few products, and fixing them after campaigns launch means traffic is already arriving at disapproved items.
Product data failures can be handled item by item. Products missing a required attribute will be disapproved, so either fix them or exclude them from the feed until they can be fixed; do not leave them to fail in diagnostics. Missing identifiers are the commonest problem on stores that resell branded goods: the identifiers guide explains when a product genuinely has none and how to declare that. Weak titles and wrong categories do not block serving, which is exactly why they survive setup, and they quietly limit which searches the products can match. Products sold in several colours or sizes that fail the attribute lines are set up end to end in the product variants tutorial, from an id per variant to a shared item group.
Accuracy failures are the ones that come back. If landing page prices or stock disagree with the feed during setup, they will disagree more often once sales and stock-outs begin; the fix is a faster fetch schedule or a direct platform connection, not a one-time correction. Adding product Schema MarkupStructured data vocabulary. to the page templates gives Google a second source that agrees with the feed. Custom labels can be added later, but not without restructuring campaigns, and campaigns built without them cannot separate products by margin when the business starts asking about ROASRevenue generated per unit of ad spend. by product line.
A homeware store's first feed
A homeware store called Haverlin Home connects its new online shop to Merchant Center with about 900 products. The setup pass fails four lines. The shipping setting says free delivery everywhere, while checkout charges £4.95 under £50. Around 120 products from two own-brand ranges have no identifiers and are flagged as missing, although own-brand items with no manufacturer code should be declared as having none. Titles start with internal codes such as HF-2231 rather than the product name. And the feed fetches once a week while stock changes daily. The team fixes the shipping rule, declares the own-brand items correctly, rewrites the title template to lead with product type, colour and material, and switches to a daily fetch before the first Shopping campaign is built.
Common mistakes
- Launching campaigns while the account is still under review. Ads start, items are disapproved, and the first week's data describes a broken feed.
- Shipping settings set once for convenience. Free delivery in Merchant Center and a charge at checkout is a mismatch Google treats as a policy problem.
- Inventing identifiers. A made-up code is worse than declaring that a product has none.
- Titles copied from the stock system. Shoppers search for what a product is, not for a warehouse code.
- Promotional overlays on images. Badges and text on the main image lead to disapprovals.
- No named owner. The feed breaks after a site change and nobody is responsible for noticing.
The product feeds and Merchant Center guide carries the weekly health check for a running feed, and the checklists library holds the rest.
