Prepare Google Shopping ads by checking the proposed market and product eligibility, then reconciling the feed with the exact item a customer can buy. Product identity, imagery, availability and checkout information need to agree. A file that imports successfully is only one stage; it does not establish that every item is eligible or accurately represented.
Start with a small, representative product sample. Include a variant, an unavailable item and an item whose details recently changed. These cases reveal weaknesses that a clean export of the easiest products can hide. Assign the catalogue owner before connecting campaign work to data that nobody is responsible for maintaining.
Why is the product feed part of advertising quality?
Shopping ads use submitted product data rather than keywords to decide how and where ads show. Shopping ads display product information including a photograph, title, price and store name. The Shopping ads overview explains why the catalogue is part of the creative experience, rather than simply an administrative file behind the campaign.
Google documents Shopping and Performance Max campaigns as ways to manage Shopping ads. Record which campaign route is proposed and why it suits the business’s goal. The existence of those campaign types does not replace a check of the current market, product and account requirements for the actual retailer.
Make the eligibility review a named task before feed submission. Record the intended destination country, language, currency, product category and relevant account decisions. Have the responsible account owner obtain the applicable requirements. Avoid assuming that a product feed prepared for another country can be reused unchanged for Zambia or any other market.
Which fields must agree with the store?
The product data specification requires a unique identifier and says to keep it stable when updating data. The product data specification recommends a consistent identity for the same item. Keep the store’s source identifier and the submitted identifier linked in the review worksheet so a changed title does not accidentally become a new product record.
The submitted product title must accurately describe the item and match the landing-page title. The product description must accurately describe the product and match the landing-page description. Inspect the actual selected variant, not merely the parent product’s attractive general page. A title that names one size or colour should lead the customer to the corresponding offer.
The product landing-page link must use the verified domain. The main product image must accurately display the product. Follow the submitted link and inspect the image as a prospective buyer. A generic category photograph or a picture of a related item can make an otherwise valid row misleading.
Submitted availability must match the landing page, checkout and structured data. Submitted price and currency must match the landing page, structured data and checkout. Compare those layers together, including any product selection needed to reach the advertised item. A matching feed and product page are insufficient if checkout presents a different offer.
| Data area | Comparison to perform | Exception to record |
|---|---|---|
| Identity | Store item, variant and submitted ID | Same item exported under a new ID |
| Title and description | Feed against selected landing-page item | General parent wording hides the variant |
| Destination | Submitted link and verified store domain | Redirect or wrong product selection |
| Main image | Actual supplied item and advertised variant | Generic image or wrong colour |
| Availability | Feed, page, checkout and structured data | Product remains advertised after stock change |
| Price and currency | Feed, page, checkout and structured data | Any unexplained difference in the offer |
| Eligibility | Current market and product requirements | Assumption carried from another account |
How should catalogue updates be owned?
Write down which system controls each field. The product name may be maintained by a content editor, while availability comes from an inventory process and the feed is generated by an integration. Identify the handover between those responsibilities. An export tool cannot resolve a disagreement about which source is authoritative.
For every change, record the source update, the generated feed state and the destination observation. Keep the times and item identifiers together. This helps distinguish a source error from a mapping problem or an update that has not yet appeared through the selected workflow.
Do not correct a mismatch only in a one-off export if the next scheduled export will restore the wrong value. Trace the error back to its owner and mapping. If an urgent intervention is needed, record how the temporary correction will be reconciled with the normal process before routine updates resume.
Original five-item Shopping readiness sample
Use this hypothetical exercise for an online stationery shop. The original artefact is a five-item catalogue continuity sheet. Each item has an expected customer-visible offer, a feed comparison and a decision about whether it is ready for account review. No sample row is permission to publish a product or activate a campaign.
Item A: ordinary notebook. Select a straightforward item with one offer. Record its store identifier, submitted ID and final landing page. Compare the title, description and image. Follow the journey through checkout and inspect the displayed offer. This creates a baseline for the remaining cases without pretending that the baseline proves the whole catalogue.
Item B: colour variant. Choose a notebook available in different covers. Follow the submitted variant link and inspect which colour is selected. Compare the photograph and title with that selected offer. If the page opens on another colour, assign a destination or mapping correction rather than asking the buyer to discover the advertised variant themselves.
Item C: unavailable item. Use an item whose stock state has changed through the normal source process. Inspect the feed, page, structured data and checkout result. Record the observed agreement or disagreement. The important evidence is whether every layer describes the same availability, not merely whether the export contains a familiar stock label.
Item D: changed offer. Use an approved source change to the product’s offer and trace it through the generated data and customer journey. Compare currency and displayed amount in the private review record without inserting example selling prices into the public guide. If the observations differ, identify the source and update stage responsible before considering the item ready.
Item E: retired item. Choose a product no longer intended for the catalogue. Record how the selected integration is meant to handle its removal or exclusion, then inspect the actual destination state through the supported review process. Do not assume deleting a spreadsheet row necessarily completes every part of the removal workflow.
Give every exception an owner: catalogue content, store configuration, integration mapping or account eligibility. The final decision should identify the failed layer. “Feed problem” is too vague when the feed accurately repeats incorrect source information.
How should readiness be reviewed before advertising?
Review the applicable eligibility requirements and the five-item sheet together. Inspect the account’s product issues and resolve them against the source record. Keep acceptance of the catalogue sample separate from campaign activation, and expand the sample when a new product structure or mapping is introduced.
Measurement needs its own check. The conversion tracking guide covers the intended customer action, while WooCommerce checkout testing covers the purchase journey. A clean product record should not be treated as proof that either has been tested.
For broader campaign context, see Google Ads. To prepare a focused brief, get started with the product sample, source ownership map and any unresolved eligibility or catalogue differences.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.