ChatGPT Ads product feed vs Google Shopping feed
Reuse accurate catalog facts, but keep destination mappings and validation separate. Product Feed Scan offers separate audit flows; it does not convert feeds or promise a simultaneous two-channel audit.
Published: · Updated:
Check your native ChatGPT Ads feedSpecification review: September 19, 2026
OpenAI native and Google-compatible feeds have separate availability, identity and eligibility rules. Check the detected mode; XML is not a Google-compatible upload format. Refresh products within 14 days and promptly after price or stock changes.
Crawler access requires manual verification. Schema.org 30.1 additions are optional opportunities with no score impact; page structured data is not scanned. Read the versioned scope and limitations.
Reuse the source of truth
Keep one authoritative record of each item's identity, price, stock and images. Exporters should map that record to the selected destination contract. Review differences rather than editing the underlying facts to satisfy superficial field checks.
Native versus Google-compatible OpenAI feeds
The native format is not the registered Google-compatible path. OpenAI's product specification requires confirmation before using that compatibility format. The checker detects native or Google-compatible fields and reports the applied rules; neither mode certifies registration or upload acceptance.
Validate each channel separately
Run the native file through the ChatGPT Ads checker. Use the Google Shopping checker for general source-quality diagnostics on that export, then review Merchant Center separately. Equal scores across profiles do not mean equal compliance or approval.
What can you reuse?
| Area | Native OpenAI | Google Shopping | Practical action |
|---|---|---|---|
| Identifiers | item_id; assigned gtin/mpn where applicable | id; destination-specific identifier requirements | Preserve item identity; do not invent identifiers. |
| Titles and descriptions | title, description | title, description | Reuse factual copy; review each destination's limits. |
| Brand and seller | brand, seller_name | brand and applicable merchant data | Do not substitute the retailer for a product brand. |
| Images | image_url | image_link | Map the actual asset; verify the destination separately. |
| Availability | Native vocabulary includes pre_order | Google vocabulary uses preorder | Map states explicitly, not by blind column renaming. |
| Pricing | price and optional sale_price | price and applicable sale_price | Keep currency and storefront amounts consistent. |
| Variants | group_id and native variant metadata | item_group_id and applicable variant attributes | Keep one stable ID per sellable variant. |
| Channel-specific data | Ads eligibility and native fields | Google-required/conditional attributes | A passing general score is not channel approval. |
| Update and delivery | Use the configured OpenAI ingestion route | Use the configured Merchant Center data source | Check delivery diagnostics in each destination. |
Sources: OpenAI: native product-file specification · Google Merchant Center: product data specification
Practical checklist
- Record both exporter mappings and versions.
- Preserve real assigned identifiers and variant identities.
- Check actual availability vocabulary in each output.
- Review each destination's processing and account diagnostics.
- Keep before-and-after evidence using the same audit profile.
Choose the next check
Independent source analysis. No OpenAI or Google approval, delivery integration or visibility guarantee. A free scan shows priority findings; the complete private report costs €19 once and remains available for 30 days.
General product feed checker · Implemented rules and limitations