Reference entries (12)
- reference GAP — no independent or primary evidence that schema markup ITSELF improves AI-answer citation; vendor claims (FAQ schema → 2.8× citations, author schema → 3×) are single-source and unverified
- reference Google has been NARROWING rich-result features — FAQ rich results deprecated May 7, 2026; seven types retired June 2025
- reference John Mueller (Google) via Search Engine Journal — "There's no generic ranking boost for SD usage"
- reference Google documentation — structured data makes pages ELIGIBLE for rich results, NOT a generic ranking boost ("enables a feature to be present, does not guarantee that it will be present")
- reference GEO paper — critical methodology caveat: the lifts come from BODY-TEXT edits, NOT schema markup; authors explicitly note "less likely to affect search engine rankings"
- reference Bing — supports JSON-LD, schema.org, Microdata, Microformats, Open Graph, RDFa via the Markup Validator (August 2018)
- reference Google Search Central — product rich results require "a distinct URL" per product (or per variant); confirms one findable page per record
- reference Google Search Central — structured data produces eligibility, not a guarantee; does not guarantee rich results even with correct markup
- reference Google Search Central — structured data labels each individual element so users can search by ingredient, calorie count, cook time
- reference schema.org — founded jointly by Bing, Google, and Yahoo! in 2011; Yandex joined Nov 2011
- reference schema.org — ItemList / ListItem / Product / Offer types exist precisely to mark up individual records and lists as machine-readable structured data
- reference Research brief: the searchable, structured catalogue as a working tool — when records-not-prose pays off (June 2026)
