Home · Newsletter · Issue 2

Merchant Evidence Brief · Issue 2

"Machine-readable product data" means two different things. Here are both specs, side by side.

Sources checked 22 November 2026 (Korea Standard Time, UTC+9). Published here as a web archive.

Last issue covered who reads your site. This one covers what they need. There are two common ways a store hands structured product facts to machines:

  1. On-page structured data: JSON-LD on each product page, read by crawlers like Googlebot.
  2. A product feed: a file (CSV, TSV, JSON) you submit with one row per item, such as the product feed OpenAI documents for its shopping surfaces.

They overlap, but their rules differ in ways that cause silent rejections. Below is what each primary source requires.


1. Google merchant listings (on-page JSON-LD)

Google’s merchant-listing documentation covers product pages where a customer can buy (Google). The required core:

Google’s AI-features guidance adds a related fundamental: “making sure your structured data matches the visible text on the page” (Google — AI features). Markup claiming a price or stock state the page doesn’t show is a problem in its own right.

Common misreadings - “If the Rich Results Test passes, I’m eligible.” Passing validation isn’t a guarantee of display. Google’s documentation consistently separates eligibility from serving (Google — AI features). - “AggregateOffer is fine everywhere.” For merchant listings, use an Offer.


2. OpenAI’s product feed (file upload)

OpenAI’s product feed reference describes a discovery feed with stricter, row-level rules (OpenAI):


3. Side by side

Topic Google merchant listing (JSON-LD) OpenAI product feed (file)
Unit One product page One row per item/variant
Required identity name, image item_id, title, image_url, url, brand, seller_name, description
Offer/price Individual Offer with price + currency, price > 0 price as amount + currency string
Availability Recommended Required enum; bad value rejects the row
GTIN Recommended Optional; strict digits + check digit
Placeholders Not addressed in the sections cited here Explicitly prohibited

Sources: Google; OpenAI.


4. Where spreadsheets quietly break feeds

Most of the OpenAI rules above are ones spreadsheets violate by default:


5. Which one do you need?

It depends on where you want to appear, and the sources keep those decisions separate:

Many stores will want both, generated from one source of truth (your catalog database or platform export), so the price on the page, in the JSON-LD, and in the feed never disagree. If you maintain the feed by hand in a spreadsheet, the four failure modes in section 4 are the ones to automate first.


Ten-minute check

  1. Export your catalog as CSV. Open it in a text editor, not a spreadsheet, and search for E+. Any hit in an ID or GTIN column means digits may already be lost.
  2. Search for n/a, null, and TBD, and delete them from optional fields.
  3. List the distinct values in your availability column. Each one should map to exactly one value from the OpenAI enumeration.
  4. On one product page, view the source and find the JSON-LD. Confirm there’s an Offer (not only an AggregateOffer), a price above zero, and a currency, and that the price matches what the page shows.
  5. Write down which surface each fix was for. Ads and checkout integrations need their own checks.

Disclosure: the author is building Catalog Sentry Local, a local CSV preflight tool that checks several of these rules. It isn’t required for anything above, and every check here can be done by hand. This issue has no sponsor.

Sources - Google Search Central, Merchant listing structured data: https://developers.google.com/search/docs/appearance/structured-data/merchant-listing - Google Search Central, Product snippet structured data: https://developers.google.com/search/docs/appearance/structured-data/product - Google Search Central, AI features and your website: https://developers.google.com/search/docs/appearance/ai-features - OpenAI, Product feed schema: https://developers.openai.com/commerce/specs/file-upload/products - OWASP, CSV Injection: https://owasp.org/www-community/attacks/CSV_Injection