Skip to content
Published Authored byBilly Reiner

Glossary · Defined term

Structured data

Structured data is machine-readable markup that describes the meaning of page content (a product, a person, an article, an event) in a standard vocabulary — most commonly Schema.org1. Shopify themes auto-emit Product structured data on every product page to enable rich snippets: "Schema markup for products is built into themes to enable rich snippets"2 — verbatim Shopify Help Center.

The underlying purpose is entity disambiguation. A page that says "Acme runs on Tuesday" could mean a product, a person, a software release, or an event — structured data tells the engine which. AI engines (ChatGPT, Perplexity, Claude, Gemini, AI Overviews) lean on structured data for the entity layer underneath their answers.

Definition

Structured data is machine-readable markup that describes the meaning of page content (a product, a person, an article) in a standard vocabulary like Schema.org. Shopify themes auto-emit Product structured data to enable rich snippets.

Structured data is distinct from unstructured prose in that the meaning is explicit. A paragraph that says "Acme Hiking Boot, $189, in stock" is prose; the equivalent Schema.org Product structured data declares "@type": "Product", "name": "Acme Hiking Boot", "offers.price": "189.00", "offers.availability": "InStock". The fields are typed; the values are checkable; the engine doesn't have to parse natural language to extract the facts.

Three syntaxes, one vocabulary

The Schema.org vocabulary can be emitted in three syntaxes: JSON-LD (JSON-based, in a script tag, Google-recommended), Microdata (HTML attributes embedded inline), and RDFa (XHTML-style attributes). All three are valid and parsed by Google; JSON-LD is the modern default because it's separable from the visual markup and easier to maintain.

Schema.org defines hundreds of types — Product, Article, Person, Organization, Event, FAQPage, HowTo, Review, AggregateRating, Place, LocalBusiness, Recipe, VideoObject, ImageObject, and many more — with hundreds of properties each1. The ecosystem is consortium-governed by Google, Microsoft, Yahoo, and Yandex, with public proposals and quarterly updates.

For ecommerce in 2026, the load-bearing types are Product, Offer, Brand, AggregateRating, Review, BreadcrumbList, Organization, and (where applicable) FAQPage and Article. Google's structured-data guidance3 documents which types are eligible for rich results, which are merely parsed for entity recognition, and which validate cleanly but produce no visible SERP enhancement.

Where the standard comes from

Schema.org launched on 2 June 2011 as a joint initiative by Google, Microsoft, and Yahoo, with Yandex joining later. Before Schema.org, the major search engines maintained competing vocabularies (Google Rich Snippets, Microformats, RDFa); the consolidation was driven by the realisation that publishers wouldn't adopt structured data unless one vocabulary worked everywhere.

The 2014 W3C standardisation of JSON-LD as the recommended syntax was the second consolidation step. Together those two moves — one vocabulary, one syntax — made structured data feasible for mainstream adoption across CMS platforms. By 2020 every major ecommerce platform shipped Product schema by default.

Adoption status in 2026

Universal among major search engines (Google, Bing, Yandex, DuckDuckGo) and AI engines (ChatGPT, Perplexity, Claude, Gemini, AI Overviews, Copilot). Theme-level emission is universal in Shopify, WordPress, Webflow, and BigCommerce. Custom emission for non-default types (FAQPage, HowTo, Service, Person) is still merchant-side work.

The 2026 wrinkle: Google retired the FAQ rich result for general Search on 7 May 2026, restricting rich-result eligibility for FAQPage schema to government and health authorities. The FAQPage type remains valid and is still parsed by AI engines as a structured FAQ source — the visual SERP enhancement is gone, but the entity layer underneath is not.

Structured data on Shopify specifically

Shopify themes auto-emit Product structured data on every product page. The emitted JSON-LD includes name, description, image, price, availability, and (when the Barcode field is populated) GTIN. Themes typically also auto-emit BreadcrumbList. What themes don't auto-emit by default: Organization (sitewide), FAQPage, Article on blog posts, Person — those require custom JSON-LD via theme.liquid.

For most Shopify stores, the auto-emitted Product and BreadcrumbList schema is sufficient for rich snippets and basic AI entity recognition. The add-on install — Organization, FAQPage, Article, Person — is where merchants start adding custom JSON-LD in theme.liquid. Schema apps (Schema App, JSON-LD for SEO, others) automate this for merchants who don't want to edit Liquid.

The full install lives in Shopify Schema & Product Data, which has 14 sub-type pages plus the implementation pages for Rich Results Test and schema apps. If you'd rather we audit and patch the structured-data posture, ShopifyRanked does it in 7 days for $499.

Structured data is the umbrella; the related terms are the syntax and the install surface.

  • JSON-LD: the recommended syntax for structured data.
  • GTIN: one of the Schema.org Product properties carried in structured data.
  • Canonical tag: complementary signal for URL-level deduplication.
  • The Shopify schema guide: the full Shopify schema treatment.

Keep reading