Schema.org

Definition

Schema.org is a collaborative project founded by Google, Microsoft, Yahoo, and Yandex that creates and maintains a shared vocabulary for structured data on the web. It defines standardized types and properties - like Product, Offer, Review, and Organization - that websites use to describe their content in a way machines can reliably understand.

When a merchant marks up a product page with Schema.org vocabulary, they are using a common language that every major search engine recognizes. The product’s name is name, its price is price, its availability is availability. No ambiguity, no guessing. The same vocabulary works whether the data is encoded as JSON-LD, Microdata, or RDFa.

Schema.org is not a technology or a file format. It is a dictionary. JSON-LD is one of the formats used to write in that dictionary. Together, they form the backbone of structured data on the modern web.

Why It Matters

Schema.org is the closest thing the web has to a universal product description language, and this matters more now than ever.

Search engine optimization. Google, Bing, and other search engines use Schema.org markup to generate rich results - the enhanced listings that show star ratings, prices, availability, and product images directly in search results. Pages with complete Schema.org markup consistently outperform plain listings in click-through rates.

AI agent comprehension. As AI agents begin browsing the web to help users shop, Schema.org markup is the most reliable signal they can use to understand what a page sells. An AI agent parsing a product page with Schema.org markup can extract structured data with high confidence. Without it, the agent must infer product details from unstructured HTML - a process that is slower, less accurate, and more likely to fail.

Foundation for protocols. The newer agentic commerce protocols do not replace Schema.org - they build on it. The product data exposed through ACP and MCP still uses Schema.org concepts. A product still has a name, price, description, and availability. Schema.org defines what those fields mean. The protocols define how to access them.

Cross-platform compatibility. Schema.org works on every ecommerce platform, every CMS, and every static website. Whether a merchant runs Shopify, WooCommerce, Magento, or a custom-built store, Schema.org vocabulary applies equally. This universality is its greatest strength.

How It Works

Schema.org defines a hierarchy of types. At the top are broad categories like Thing, CreativeWork, and Event. Under these sit more specific types that ecommerce merchants commonly use:

Product is the core type for any item sold online. It includes properties for name, description, brand, SKU, images, color, material, and dozens of other attributes. The more properties a merchant populates, the richer the machine-readable representation of their product.

Offer describes the commercial terms - price, currency, availability (InStock, OutOfStock, PreOrder), delivery details, and seller information. A Product can have multiple Offers representing different variants or sellers.

Review and AggregateRating capture customer feedback. Individual reviews include author, rating, and text. AggregateRating summarizes all reviews with an average score and count.

Organization and LocalBusiness describe the merchant entity - name, address, contact information, logo, and social profiles.

BreadcrumbList defines the category navigation path, helping search engines and AI agents understand where a product sits in a store’s hierarchy.

To implement Schema.org, merchants typically embed it as JSON-LD in their page templates. Most ecommerce platforms handle basic Schema.org markup automatically, but the default implementation is often minimal. Merchants who want maximum visibility - in both traditional search and AI-driven discovery - should audit their Schema.org implementation and fill in missing properties.

The practical rule for merchants: every product attribute that exists in your store’s backend should also exist in your Schema.org markup. If you track color, size, material, and weight internally, those fields should be in your structured data too. The gap between what you know about your products and what machines can read about them is lost visibility.

Related Terms

• JSON-LD - The most common format for embedding Schema.org data in web pages
• Structured Data - The general concept that Schema.org standardizes
• AI Readiness - How well a store’s data prepares it for AI-driven discovery, where Schema.org plays a key role
• Product Feed - Structured product data exports that often use Schema.org vocabulary