What Is E-commerce Schema Markup?
E-commerce schema markup is structured data added to product pages using the Schema.org vocabulary, formatted as JSON-LD and delivered in a script tag. It translates page content (product name, price, reviews, availability, shipping) into a machine-readable format that Google can process without relying solely on parsing natural language HTML.
When Google validates the schema successfully, it uses the data to generate rich results in search. These are enhanced snippets that display star ratings, prices, stock availability, and breadcrumb trails directly in the search results page, before a user clicks. For e-commerce, this means your product listing can show "4.8 stars, 342 reviews, $89.95, In stock" inside the SERP itself.
Beyond traditional search results, schema markup feeds into Google's Knowledge Graph, which AI systems query when generating product recommendations and AI Overview answers. A product page with complete schema is more likely to be accurately represented in AI-generated answers than one that requires an AI to infer all attributes from prose text.
Why Schema Matters for Product Pages
Product pages face a structural disadvantage in traditional search results: they are competing against review sites, comparison sites, and editorial content for the same queries. A well-implemented schema that surfaces star ratings and price in the snippet changes the click-through dynamic. Users comparing results gravitate toward snippets that answer their immediate questions (is it affordable? is it well-reviewed?) before clicking.
Google's research has consistently shown that rich results achieve higher click-through rates than standard blue-link results. The mechanism is simple: a snippet with five stars and a price removes friction from the evaluation process. The user does not need to visit the page to confirm basic product attributes, but the confirmation that those attributes meet their criteria increases the probability they will click through to purchase.
See the Product Page SEO guide for a broader breakdown of what makes product detail pages rank, or audit any product URL instantly with the free E-Commerce Product Page SEO Checker. Schema is one component of a larger structural requirement.
Core Schema Types for E-commerce
All e-commerce schema markup begins with the Product type as the root object. Offer, AggregateRating, Review, and BreadcrumbList are either nested inside Product or accompany it. Each type is responsible for a different dimension of product information.
The hierarchy reflects how Google reasons about product pages. The Product type establishes what the page is about. The Offer type establishes the commercial terms. The AggregateRating type establishes social proof. BreadcrumbList establishes the page's position in the site hierarchy. Together they give Google a complete, machine-readable picture of the page without requiring it to parse unstructured HTML.
Product Schema in Detail
The Product schema type accepts a large number of properties. The most important for rich results and AI citability are:
- name: The full product name. Should match the H1 heading exactly.
- description: A concise product description. Do not paste the entire product copy. Write 2-3 sentences that summarise the core product value.
- image: An array of product image URLs. Google recommends providing multiple images at different aspect ratios (1:1, 4:3, 16:9).
- sku: Your internal SKU or model number. Helps Google disambiguate between product variants.
- brand: Nested Organization or Brand type with the brand name. Critical for Knowledge Graph entity matching.
- gtin13 / gtin8 / mpn: Global trade identifiers. Google uses these to match your product listing to its product knowledge base for enhanced features.
// Minimal valid Product schema
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Women's Trail Runner X2",
"sku": "WTR-X2-BLK-9",
"brand": { "@type": "Brand", "name": "TrailCo" },
"offers": { "@type": "Offer", "price": "89.95", "priceCurrency": "AUD", "availability": "https://schema.org/InStock" }
}
AggregateRating and Review Schema
AggregateRating is the schema type that enables star ratings to appear in organic search results. It is nested inside the Product type and summarises the collective rating across all reviews. Google requires that the ratings reflect genuine user reviews and that the review content is accessible on the page itself (not behind a paywall or loaded only via JavaScript after the initial render).
Individual Review objects can also be nested, each containing a Rating, author name, date published, and review body. Google may display individual review excerpts in certain result formats. For AI Overviews, review content is particularly important: AI systems often cite product pages that contain structured review data when answering queries like "what are the best trail running shoes?"
A common implementation mistake is displaying a star rating visually on the page but failing to implement the corresponding AggregateRating schema. Google's crawler sees no structured data confirming the rating, so no rich result appears in the SERP. Always verify schema implementation using Google's Rich Results Test after adding or modifying rating markup.
Offer Schema: Price, Availability, Shipping
The Offer type tells Google the commercial conditions for the product. Required fields for rich results are price, priceCurrency, and availability. Availability must use Schema.org URLs (e.g. https://schema.org/InStock, https://schema.org/OutOfStock, https://schema.org/PreOrder).
Google introduced Merchant Listings as an enhanced version of product rich results that shows free shipping, return policies, and other purchase signals directly in search. These require the OfferShippingDetails nested type, which specifies shipping rate, destination, and delivery time. Australian stores should include the shippingDestination property with addressCountry: "AU" to ensure the shipping information is shown to Australian searchers.
The hasMerchantReturnPolicy property enables return policy information in Merchant Listings. This is relatively new schema vocabulary but already influences whether Google's Shopping Graph surfaces your products in comparison contexts.
How E-commerce Schema Markup Affects AI Search Visibility
Schema markup does not directly improve organic rankings. Google has been clear that structured data is not a ranking factor. Its value is in rich result eligibility and AI search citability, both of which influence click-through rate and ultimately revenue, if not the underlying position in search results.
For AI search engines, schema markup's importance is growing. Systems like Google's AI Overviews and Perplexity rely on structured, machine-readable signals to construct accurate product comparisons and recommendations. A product page that communicates price, availability, rating, and brand via schema gives AI systems cleaner input than a page that buries this information in paragraphs of marketing copy.
The Product Page SEO Checker audits your product pages against 82 technical and content criteria, including schema completeness and accuracy. It checks whether Product, Offer, AggregateRating, and BreadcrumbList are present, whether values are valid, and whether rich result eligibility requirements are met. For e-commerce SEO strategy across your full catalogue, the E-commerce SEO service covers technical schema implementation as part of a broader audit and optimisation programme.
Frequently Asked Questions
Does schema markup improve Google rankings?
Schema markup is not a direct ranking factor. Google has confirmed this. Its value is in rich result eligibility, which improves click-through rates, and in AI search citability, which affects how often your products are mentioned in AI-generated answers. Improved CTR over time can indirectly improve ranking signals, but schema alone does not move rankings.
What is the difference between JSON-LD and microdata for schema?
JSON-LD is delivered as a separate script block in the page head or body, independent of the HTML content. Microdata embeds schema attributes directly in the HTML elements. Google recommends JSON-LD because it is easier to implement, maintain, and validate. It does not require you to modify the visual HTML structure to add schema properties, and it is simpler to update programmatically across large product catalogues.
Why are my star ratings not appearing in Google search results?
Several reasons are possible. The AggregateRating schema may be missing or incorrectly formatted. The review content may not be visible on the page (if loaded only via JavaScript). Google may not yet have recrawled the page since schema was added. The rating may violate Google's guidelines (e.g. self-serving reviews, ratings not based on genuine user experiences). Use the Google Rich Results Test to check for validation errors first.
Should I add schema to every product page or just featured products?
Add schema to every active product page. The implementation should be automated through your e-commerce platform's template layer so it applies universally. Selective implementation means most of your catalogue misses out on rich results and AI citability. Platforms like Shopify, WooCommerce, and Magento have theme-level schema implementation that covers all products once configured correctly.
How does product schema help with AI search?
AI search systems retrieve and synthesise information from multiple pages when generating answers. Product schema provides clean, structured signals (price, availability, rating, brand) that AI models can read directly without parsing marketing copy. Pages with complete schema are more likely to be cited accurately in AI-generated product comparisons and recommendation answers, particularly in Google AI Overviews and Perplexity product queries.
What GTINs should I include in product schema?
Include whichever global trade identifier applies to your product: gtin13 for standard European Article Numbers (EAN), gtin8 for short barcodes on small items, gtin12 for UPC codes, or gtin14 for shipping containers. If you manufacture your own products without registered GTINs, use the mpn (Manufacturer Part Number) property instead. Google uses GTINs to match your product page to its shopping knowledge base, enabling richer product feature displays.
Tharindu Gunawardana
Founder and Director of SearchMinistry
Tharindu Gunawardana is the Founder of SearchMinistry Media and a search strategist with 17 years of experience across Sri Lanka, Singapore, and Australia. A former Agency SEO Director, he specialises in helping brands transition from traditional SEO to AI-driven discovery.