Google Product Feed Preflight Before Client Handoff

A useful Google-oriented catalog preflight should catch obvious feed defects without pretending to be full Merchant Center certification. Requirements vary by product, market and program, so preserve merchant facts and flag uncertainty.

Independent technical checklist. Google requirements can change and may be conditional. Confirm current official Merchant Center documentation before production submission.

Start with the core catalog fields

• Product ID
• Title and description
• Landing-page link and image link
• Availability
• Price and currency
• Brand where applicable

GTIN, MPN, brand and other identifiers can be conditional. A validator should flag missing information for review rather than invent identifiers.

Check URLs and landing-page consistency

• Use absolute product and image URLs.
• Check redirects, canonical and indexing signals on the public page.
• Verify price and availability against the merchant's actual product experience.
• Inspect Product structured data where relevant.

Do not convert uncertainty into a false fact

If a source catalog contains a stock state that cannot be represented safely in the target profile, block or flag the conversion. For example, an OpenAI Stable unknown availability value should not automatically become in_stock or out_of_stock.

Keep a change trail

Safe formatting normalization should produce before/after evidence. Missing price, stock, brand or identifiers require merchant input. Re-run the Google-oriented preflight on the fixed copy before handoff.

Agency handoff package

• Original/before audit result
• Safe fixed copy
• Per-field change log
• After-fix recheck
• Evidence and unresolved merchant-input items
• Optional public-page audit evidence

Compare OpenAI Stable and Google-compatible feed differences →

Full agency product-feed preflight checklist →

No platform acceptance, indexing, recommendation, ranking, checkout, traffic or sales guarantee.