What is schema markup? Ecommerce structured data, explained
Schema markup is structured data code added to a webpage to tell search engines and other machine readers what the page contains. It uses a shared vocabulary, usually from Schema.org, to label things like products, prices, availability, reviews, FAQs, articles, organizations, and breadcrumbs.
The short version: schema markup turns page content into explicit facts that software can understand instead of forcing search engines or AI systems to infer everything from visible text.
What schema markup means in practice
A normal product page is written for humans. It may show a product name, image, description, price, color, availability, return policy, and reviews.
A machine can read that page, but it still has to infer what each element means. Is $129 the current price, an old price, a monthly payment, or an example? Is navy a color, a collection name, or part of a description? Is a five-star icon a rating, a decoration, or a testimonial block?
Schema markup removes some of that ambiguity by labeling the content directly.
For example, product schema can tell machines:
- this page describes a product;
- this string is the product name;
- this value is the SKU or GTIN;
- this image represents the product;
- this offer has a price and currency;
- this product is in stock or out of stock;
- these items are variants of the same parent product;
- these reviews or ratings belong to the product.
That does not replace the visible product page. It makes the page easier to interpret.
How schema markup works
Schema markup has three basic parts: types, properties, and values.
| Part | What it means | Example |
|---|---|---|
| Type | The kind of thing being described | Product, Organization, FAQPage, BreadcrumbList |
| Property | A field that belongs to that type | name, image, description, sku, offers |
| Value | The actual fact on the page | "Merino Wool Hoodie", "InStock", "129.00" |
Most modern schema markup is implemented as JSON-LD. JSON-LD is a block of structured data that can sit in the page HTML without wrapping every visible element in extra tags.
A simplified product example looks like this:
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Merino Wool Hoodie",
"description": "A lightweight wool hoodie for travel and everyday wear.",
"sku": "MWH-001",
"brand": {
"@type": "Brand",
"name": "Example Brand"
},
"offers": {
"@type": "Offer",
"price": "129.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
}The exact fields depend on the page and the search feature you are trying to qualify for. The important principle is simple: only mark up facts that are accurate, visible, and supported by the page.
Why schema markup matters for ecommerce
Ecommerce pages depend on precise product facts. Schema markup gives search systems a cleaner way to understand those facts.
Rich-result eligibility
Search engines can use structured data to decide whether a page is eligible for enhanced search displays. For product pages, that can include details such as price, availability, ratings, shipping, return information, and product imagery.
Eligibility is not a guarantee. A page can have valid schema markup and still not receive a rich result. Search engines decide what to show.
Clearer product understanding
Product pages often contain many small details: size, color, material, model number, compatibility, ingredients, dimensions, reviews, and variants. Schema markup helps identify which detail is which.
That matters when search systems, shopping surfaces, and AI agents need to compare products or answer specific buyer questions.
Better consistency across systems
Schema markup is one output of a broader product-data workflow. The same product facts may also feed storefront pages, marketplace feeds, retailer portals, ad platforms, catalogs, and APIs.
If the product data is inconsistent upstream, schema markup can expose that inconsistency. If the product data is clean, schema markup becomes easier to generate and maintain.
Common schema types for ecommerce teams
Schema.org includes many types, but ecommerce teams usually start with a smaller set.
| Schema type | What it describes | Ecommerce use |
|---|---|---|
| Product | A product or product variant | Product name, image, description, SKU, brand, GTIN, category, and attributes |
| Offer | A sale offer attached to a product | Price, currency, availability, condition, seller, shipping, and returns |
| AggregateRating | Overall rating data | Average rating and review count |
| Review | Individual review content | Review author, body, date, and rating |
| BreadcrumbList | Page hierarchy | Category and navigation context |
| Organization | The company or brand | Name, logo, URL, and contact details |
| FAQPage | Frequently asked questions | Short question-and-answer content on eligible pages |
| Article | Editorial content | Blog post headline, author, publish date, image, and publisher |
For product pages, Product and Offer are usually the most important. They are also the easiest to get wrong if price, availability, variants, or identifiers are not managed carefully.
Schema markup vs related terms
Schema markup overlaps with several SEO and product-data terms.
| Term | Meaning | How it differs from schema markup |
|---|---|---|
| Structured data | Any data organized in a machine-readable structure | Schema markup is a specific structured-data implementation for webpages |
| Schema.org | The shared vocabulary of types and properties | Schema markup uses the vocabulary on a page |
| JSON-LD | A format for linked structured data | JSON-LD is how the markup is commonly written |
| Metadata | Page-level information such as title tags and meta descriptions | Metadata describes the page; schema markup can describe entities and facts inside the page |
| XML sitemap | A file listing URLs for crawlers | A sitemap helps discovery; schema markup helps interpretation |
| Product feed | A structured product file sent to platforms such as Google Merchant Center | Feeds syndicate product data; schema markup exposes product facts on the page |
| PIM | Product information management | A PIM can manage product facts that later power schema markup, feeds, and pages |
For more on the product-data source of truth behind commerce pages, read Catalog's guide to PIM.
When do you need schema markup?
You usually need schema markup when important page facts should be easier for search engines, shopping surfaces, or AI systems to understand.
Common signals include:
- product pages have prices, availability, ratings, variants, shipping, or return details;
- category and product pages rely on breadcrumbs for context;
- editorial pages answer common buyer questions;
- product data appears on the page but is hard for machines to identify consistently;
- a site is eligible for Search Console enhancement reports but has errors or missing fields;
- product details change often and need a more reliable structured-data workflow;
- AI-shopping visibility matters and product pages need clearer machine-readable context.
Schema markup is especially important when a catalog has many SKUs, variants, or fast-changing offers. Manual one-off markup breaks quickly at that scale.
Common schema markup mistakes
Treating schema as a ranking shortcut
Schema markup can help search engines understand a page and can make pages eligible for richer displays. It is not a guaranteed ranking boost.
The page still needs useful content, accurate product data, strong technical foundations, and a reason to deserve visibility.
Marking up facts that are not on the page
Structured data should match the visible page. If the page does not show a rating, price, return policy, FAQ, or review, do not add markup that pretends it does.
Mismatch creates trust and quality problems.
Letting price or availability go stale
Product schema is only useful if it stays current. A page that marks a product as in stock when the storefront says out of stock creates a bad experience for shoppers and machines.
Fast-changing commerce data needs a reliable source, not copied-and-pasted markup.
Using generic schema instead of specific product facts
Adding Product markup with only a name and description is a start, but it may not be enough for competitive commerce pages.
Useful product schema often depends on richer facts: brand, SKU, GTIN, variant relationships, images, offers, price, availability, shipping, returns, ratings, and attributes.
Skipping validation
Small syntax mistakes can invalidate schema markup. Required or recommended fields can also be missing.
Teams should test markup with Schema.org Validator, Google's Rich Results Test, and Search Console enhancement reports after launch.
Confusing schema markup with a product feed
A product feed sends product data to a platform. Schema markup labels product facts on a webpage. Many ecommerce teams need both.
The strongest setup keeps product pages, feeds, schema markup, and APIs aligned to the same trusted product data.
Where Catalog fits with schema markup
Catalog is not a schema markup generator or validator. Catalog fits one layer deeper: the product data that schema markup depends on.
Good schema markup needs complete, normalized, current product facts. That includes product names, descriptions, attributes, variants, identifiers, categories, compatibility, use cases, and offer details.
Catalog helps structure and enrich product data so it can be used across AI commerce surfaces. That same product context can support better product pages, cleaner feeds, more useful APIs, and more reliable schema markup.
In practice, the stack can look like this:
| Layer | Job |
|---|---|
| Product data source | Store approved product facts, attributes, variants, and offer details |
| Catalog | Normalize and enrich product data for AI-ready understanding |
| Storefront and CMS | Render the visible product and content experience |
| Schema markup | Label page facts for search engines and machine readers |
| Product feeds and APIs | Send structured product data to external systems and builders |
If your product data is thin, schema markup will be thin too. If your product data is rich, structured, and current, schema markup becomes a stronger signal of what each product actually is.
For deeper product-data context, read how product data enrichment supports AI commerce. For builder workflows, see the Catalog API. For AI-search visibility, read how to make products show up in ChatGPT.
Related terms
FAQ
What is schema markup in SEO?
Schema markup is structured data added to a webpage so search engines can understand the page more explicitly. In SEO, it is commonly used to make pages eligible for rich results and to clarify entities such as products, articles, FAQs, organizations, reviews, and breadcrumbs.
Is schema markup the same as structured data?
They are closely related, but not identical. Structured data is the broad concept of organizing information in a machine-readable way. Schema markup is structured data added to webpages using Schema.org vocabulary.
What is an example of schema markup?
A product page can use Product schema to label the product name, image, description, brand, SKU, offer, price, currency, availability, rating, and reviews. That helps search systems understand which facts belong to the product.
Does schema markup improve rankings?
Schema markup is not a guaranteed ranking boost. It can help search engines understand a page and can make the page eligible for richer search displays, but rankings still depend on content quality, relevance, authority, technical health, and competition.
What schema markup should ecommerce sites use?
Most ecommerce sites should start with Product, Offer, BreadcrumbList, Organization, and relevant review or rating markup when those facts are present on the page. Editorial pages may also use Article or FAQPage when appropriate.
How do you test schema markup?
Use Schema.org Validator to check whether the markup is valid. Use Google's Rich Results Test to see whether the page is eligible for Google rich-result types. After launch, monitor Search Console enhancement reports for errors, warnings, and coverage changes.
Does Catalog replace schema markup?
No. Catalog does not replace schema markup. Catalog helps create structured, enriched product data. Schema markup is one way to expose some of that product data on webpages for search engines and machine readers.
