Ecommerce Schema Markup: What to Add in 2026

Ecommerce schema markup is structured data, usually JSON-LD, that tells Google exactly what a product is, what it costs, whether it is in stock and what customers think of it. For online stores the types that matter most are Product with Offer (price and availability), Review and AggregateRating (ratings), plus BreadcrumbList and Organization. An important 2026 update: Google stopped showing FAQ rich results in May 2026 and has removed the FAQ rich result documentation, so FAQ schema no longer earns special search features. You can still keep useful FAQs on the page for shoppers.

This guide explains each type, which properties Google requires, how to avoid the review mistakes that lead to manual actions, and gives copy-ready JSON-LD examples you can adapt and test.

Disclosure: Optihole is an SEO agency that implements structured data for online stores. Our team has 6+ years in SEO and has completed 800+ SEO projects for 210+ clients in 45+ countries. The code below uses invented example values, not client data.

Does schema markup improve rankings?

Not directly. Structured data makes pages eligible for richer search results such as price, availability and star ratings, which can make a listing more useful and visible. Google is clear that eligibility is not a promise: it “does not guarantee” that structured data will show up in results (Google Search Central). Google also says a structured data manual action removes rich result eligibility but “doesn’t affect how the page ranks in Google web search”.

Google recommends JSON-LD because it is “the easiest solution for website owners to implement and maintain at scale”, and advises using fewer but complete and accurate properties rather than many incomplete ones (Google Search Central).

Which Product schema properties does Google require?

Google has two product experiences (Google Search Central):

• Product snippets are for pages about a product, including review pages. Google requires name plus at least one of review, aggregateRating or offers (product snippet docs).
• Merchant listings are for pages where shoppers can buy the product. Required properties are name, image and offers with a price (merchant listing docs). Recommended extras include brand, GTIN or MPN, availability, shipping details and return policy.

Google notes that if you add the required properties for merchant listings, your product pages can also be eligible for product snippets. Here is a typical product page example:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Oak Bedside Table, 2 Drawers",
  "image": [
    "https://www.example.com/images/oak-bedside-table.jpg"
  ],
  "description": "Solid oak bedside table with two soft-close drawers.",
  "sku": "OBT-2D",
  "brand": {
    "@type": "Brand",
    "name": "ExampleHome"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://www.example.com/products/oak-bedside-table",
    "price": 149.0,
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": 4.6,
    "reviewCount": 38
  }
}

Keep every value in the markup identical to what the page shows. If the visible price changes for a sale, the price in the markup must change too. Availability values such as InStock, OutOfStock, BackOrder, PreOrder and Discontinued are all supported.

How should review and rating schema be used?

Reviews are where most stores get into trouble. Google’s review snippet guidelines (Google Search Central) and general policies set some clear rules:

• Only mark up reviews that are visible on the page. If a shopper cannot read the reviews, do not include them in the markup.
• Attach reviews to the product. Nest them in the Product, or use itemReviewed to point at it.
• No fake or copied reviews. Google’s policies list “fake reviews” as misleading content you must not mark up.
• Self-serving reviews of your business are not eligible. Google limits review stars for LocalBusiness and Organization to sites that capture reviews about other businesses. Reviews of your products on the product page are a different case and can be marked up.
• Keep counts accurate. ratingValue and reviewCount should match the numbers displayed.

Google also supports pros and cons on editorial product review pages through positiveNotes and negativeNotes, which need at least two statements. These are aimed at review content rather than ordinary store product pages. A single customer review nested in a product looks like this:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Oak Bedside Table, 2 Drawers",
  "review": {
    "@type": "Review",
    "reviewRating": {
      "@type": "Rating",
      "ratingValue": 5,
      "bestRating": 5
    },
    "author": {
      "@type": "Person",
      "name": "Sam K."
    },
    "reviewBody": "Solid build and the drawers close quietly."
  }
}

What happened to FAQ schema?

Google deprecated the FAQ rich result in May 2026. Its documentation updates log says the documentation was removed because “the FAQ rich result feature is no longer shown in Google Search results” (Google Search Central). In practice:

• Adding FAQPage markup will not create expandable FAQ results in Google any more.
• Existing FAQPage markup is not a problem to leave in place, but it is no longer worth adding to product or category templates just for Google.
• FAQ content still matters. Clear answers about sizing, delivery and returns help shoppers decide, and plain-language answers on the page can be read by search features such as AI Overviews.
• Spend the effort elsewhere: complete Product, Offer, shipping and return policy markup has a direct link to current Google shopping features.

What other schema should an online store use?

• ProductGroup for variants. Products sold in several sizes or colours can use ProductGroup with variesBy, hasVariant and productGroupID, which makes them eligible for variant information in merchant listings (Google Search Central).
• BreadcrumbList on product and collection and category pages, to show where a page sits in your store (Google Search Central).
• Organization on the home page or about page. Google says merchants can use it to influence their merchant knowledge panel with details such as return policy, address and contact information (Google Search Central).
• Shipping and returns. shippingDetails in the Offer and hasMerchantReturnPolicy describe delivery costs and return windows.

A breadcrumb example for a product page:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Bedroom",
      "item": "https://www.example.com/bedroom"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Bedside Tables",
      "item": "https://www.example.com/bedroom/bedside-tables"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Oak Bedside Table, 2 Drawers"
    }
  ]
}

And an Organization example with a return policy:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "ExampleHome",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/logo.png",
  "hasMerchantReturnPolicy": {
    "@type": "MerchantReturnPolicy",
    "applicableCountry": "US",
    "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
    "merchantReturnDays": 30,
    "returnMethod": "https://schema.org/ReturnByMail",
    "returnFees": "https://schema.org/FreeReturn"
  }
}

Ekram does excellent work! He is fluent in English, is quick to understand, and easy to communicate with.. goes above and beyond what is asked for, with a lot of attention to detail. He is polite and responds quickly. He is a professional!

Verified Fiverr client, United States, 5 stars

What are the most common ecommerce schema markup mistakes?

Most problems we see in ecommerce schema markup are not exotic. They are small mismatches that build up across thousands of product pages:

• Stale prices and stock. Markup is cached or hard-coded, so a sale price or an out-of-stock status on the page does not match the JSON-LD.
• Two Product blocks on one page. The theme outputs one and an app or plugin outputs another, often with different values.
• Ratings with no visible reviews. A rating widget loads reviews in a way users cannot see, or the markup shows a rating for a product with no reviews at all.
• Store-wide ratings on every product. Using your overall shop rating as the product rating misrepresents the product.
• Missing currency or wrong format. Prices need a priceCurrency, and numbers should not include currency symbols.
• Markup on category pages that describes one product. Product markup belongs on the page about that product, not on a list page.

Fixing these is usually a template job: correct the source once, and every product page improves together.

How do you add and test ecommerce schema?

• Check what your platform already outputs. Many ecommerce themes and SEO plugins add Product markup automatically. Duplicate or conflicting Product blocks are a common problem.
• Generate markup from your product data, not by hand. Price, stock and rating values should come from the same source as the visible page so they never drift.
• Test with Google’s Rich Results Test before and after deployment, on a sample of product, category and home pages.
• Monitor Search Console. The enhancement reports for products, merchant listings and breadcrumbs show errors and warnings across the whole site.
• Recheck after theme, app or plugin changes, which often break or duplicate markup.

Schema issues are often part of a wider set of problems; our guide to technical SEO warning signs can help you spot them.

Frequently asked questions

What is the most important schema for an ecommerce site?

Product with Offer. It describes the product, price and availability and is required for merchant listing experiences. Add ratings, breadcrumbs and Organization markup after that.

Can I still use FAQ schema in 2026?

You can, but Google no longer shows FAQ rich results as of May 2026, so it will not change how your pages appear in Google. Keep helpful FAQs on the page for shoppers.

Can I mark up reviews from my own customers?

Yes, for product reviews shown on the product page, as long as they are genuine and visible. Self-serving review stars for your business as a whole (LocalBusiness or Organization) are not eligible.

Does schema markup help rankings?

Not directly. It makes pages eligible for rich results, which can improve how listings look. Google does not guarantee rich results will appear.

JSON-LD or microdata?

Google supports both, but recommends JSON-LD because it is easier to implement and maintain at scale.

Why are my star ratings not showing?

Common causes are missing required properties, reviews not visible on the page, policy issues, or Google simply choosing not to show them. Test the page and check Search Console reports.

Final thoughts

Good ecommerce schema markup is accurate, complete and generated from the same data shoppers see. Focus on Product and Offer first, add honest ratings and variant data, use breadcrumbs and Organization markup, and drop FAQ schema from your priority list now that Google no longer shows FAQ rich results.

Not sure your markup is right? Ask us for a structured data check (choose “SEO” in the form). We will test your product, category and home page markup and list what to fix. Schema work is part of our ecommerce SEO services; see all our services.

Sources

• Google Search Central: Introduction to Product structured data
• Google Search Central: Product snippet structured data
• Google Search Central: Merchant listing structured data
• Google Search Central: Review snippet structured data
• Google Search Central: Product variant structured data
• Google Search Central: Breadcrumb structured data
• Google Search Central: Organization structured data
• Google Search Central: General structured data guidelines
• Google Search Central: Introduction to structured data markup
• Google Search Central: Latest documentation updates (FAQ rich result removal)