schema.org Product JSON-LD

Structured-data markup embedded in retail product pages that serializes price, rating, color and SKU in schema.org vocabulary.

The Zappos catalog exposes it on pages even though no public API exists, making it the main machine-readable field source.

In this catalog it appears concretely: - Zappos tags include. - Goodreads Web Catalog — "public book pages and search results expose schema.org Book JSON-LD with title, author, ISBN, format, page count, language, average rating, rating counts and review counts".

A table is only as good as the column you actually need. If this field is absent, sparsely populated or defined inconsistently across rows, no amount of surrounding richness rescues the analysis, so it deserves its own line in your evaluation checklist.

The failure mode is concrete: the listing promises one thing, the delivered files tell another, and the gap surfaces mid-project when fixing costs most.

82.4% of the 1,744 cataloged datasets are free to access, and Zappos tags include lets you inspect the real artifact before any budget is committed.

Treat every claim of this attribute as testable:

1. Open Zappos tags include and compare its listing against the delivered artifact before paying for a commercial equivalent.
2. Open Goodreads Web Catalog and confirm its record — "public book pages and search results expose schema.org Book JSON-LD with title, author, ISBN, format, page count, language, average rating, rating counts and review counts" — against the files you actually receive.
3. Pin down update cadence in writing. Across this catalog, 22.6% of 1,744 datasets refresh daily and 64 still arrive only through a manual request form, so ask exactly how fresh each release is.
4. Check whether definitions are verified at all. Field definitions are verified for 1495 of 1,744 datasets (85.7%), and any source you license should meet that bar.
5. Price the delivery route before the license. In this catalog bulk download is the most common access method (725 datasets) ahead of official APIs (574), and 379 sources still require scraping — a maintenance cost that lands on you, not the vendor.

See the term applied to real records: footwear data, publishing data.

Adjacent concepts worth reading next: - navigation facets - PDP sitemap - productid colorid - sitemap url discovery - Work-Edition Model