Odd Logic
Schema markup in 2026 does two jobs: it earns rich results in Google and makes your product data readable so ChatGPT, Perplexity, and AI Overviews can cite it. This guide covers the four schema types ecommerce brands need, what Google deprecated (including FAQ rich results), and how to implement structured data without breaking it.
Ecommerce Schema Markup in 2026: How Structured Data Gets Your Products Cited by AI
Schema markup is how you tell Google and AI systems exactly what is on your product pages. In 2026 it does two jobs at once. It makes your pages eligible for rich results in Google Search, and it turns your product data into something ChatGPT, Perplexity, and Google AI Overviews can read and cite.
For ecommerce, four schema types carry almost all the weight: Product, Organization, Review, and Breadcrumb. Everything else is situational.
Here is the part most guides still get wrong. FAQ and How-to schema no longer produce rich results in Google. If you are still adding them for search visibility, stop. We cover what replaced them below.
What schema markup actually does now
Schema markup is structured code, almost always written in JSON-LD, that labels the content on a page so machines do not have to guess. A price is tagged as a price. A rating is tagged as a rating. Availability is tagged as in stock or out of stock.
Google has been clear that structured data is not a direct ranking factor. It does not push you up the results on its own. What it does is remove ambiguity. When an AI system can verify your product, your price, and your reviews from clean markup instead of scraping raw HTML, it trusts your page and cites it more often.
That trust is the whole game now.
In March 2025, Google and Microsoft both confirmed they use schema markup to power their generative AI features. ChatGPT confirmed it uses structured data to decide which products show up in its answers. That is not a minor tweak. It moved schema from a display feature to a discovery signal.
The payoff shows up in the data. Pages with proper schema have a meaningfully higher chance of appearing in AI-generated answers, and product pages with no schema usually do not get cited at all, because the AI cannot reliably pull price, availability, or rating out of unstructured HTML.
If you are new to how AI search surfaces work, start with What Is Answer Engine Optimization (AEO)? A Plain-English Guide for 2026 and How to Get Cited on Perplexity and Google AI Overviews. This post is the technical layer underneath both.
The 2026 deprecations: what stopped working
Google spent the last two years pruning schema types that delivered little value. This confused a lot of people into thinking structured data was dying. It is not. Google Search Advocate John Mueller said plainly that Google is not killing schema. It is cleaning house.
Here is what actually changed, so you do not waste effort on dead features:
How-to rich results were removed in 2023 and no longer appear on any device.
- Seven schema types were retired in June 2025 in a single pass, including Course Info, Estimated Salary, and Vehicle Listing.
- Practice Problem support was removed from Search Console and the Rich Results Test in January 2026.
- FAQ rich results stopped appearing in Google Search on May 7, 2026.
None of these changes affect rankings. They change how your result looks, and increasingly how machines read your page. The schema that survived is the schema that matters for ecommerce: Product, Organization, Article, Review, and Breadcrumb.
Audit your site and remove any leftover FAQ, How-to, or Practice Problem markup. It no longer helps, and it can throw warnings in Search Console.
The four schema types every ecommerce site needs
Organization schema
This is the most important type for AI visibility, and most stores implement it badly or skip it entirely. Organization schema defines who you are as a brand: your name, logo, official site, and social profiles. It is what lets an AI system connect a product to a recognized seller instead of an anonymous URL.
Nest your business policies here too. Return policy and shipping details belong under Organization markup, and Google uses them to generate returns and delivery rich results that appear before the click. Those features have low implementation cost and most of your competitors are not using them.
Product schema
This is the anchor for every product page. It carries the name, image, description, brand, price, availability, and identifiers.
Product schema unlocks two different rich results, and the distinction matters:
Product snippets show stars, price, and availability under your blue link. Required fields are name, image, and an offer with price and priceCurrency.
Merchant listings are the carousel results at the top of high-intent commercial queries. The requirements are stricter. You need price, priceCurrency, availability, and a product identifier: GTIN, MPN, or SKU. Only pages that directly sell the product qualify. Pages that only link out to other sellers do not.
A minimal, valid Product block looks like this:
{ "@context": "https://schema.org", "@type": "Product", "name": "Classic Cotton Crew Tee", "image": "https://yourstore.com/img/crew-tee.jpg", "description": "100% combed cotton crew neck t-shirt.", "brand": { "@type": "Brand", "name": "Your Brand" }, "sku": "CT-CREW-01", "gtin13": "0123456789012", "offers": { "@type": "Offer", "url": "https://yourstore.com/products/crew-tee", "price": "29.99", "priceCurrency": "USD", "availability": "https://schema.org/InStock" } }
Two things trip up most stores:
Price must be a plain number. Write "29.99", never "$29.99" or "1,350." A currency symbol or comma will invalidate the field.
GTIN is the single most underused property. Google heavily weights GTIN-matched products for merchant listings, and most sellers leave it blank. If your products have a GTIN, add it.
Review and AggregateRating schema
Ratings are one of the highest-value signals you can mark up. They power the star ratings in snippets, and they are exactly what AI systems extract when they build comparison-style answers for commercial queries like "best waterproof hiking boots."
One rule: mark up real, on-page reviews only. Ratings in your schema that do not appear on the visible page are a violation and can get your entire markup ignored.
Breadcrumb schema
The quiet workhorse. Breadcrumb markup shows your site hierarchy in the result and helps both Google and AI systems understand where a product sits in your catalog. Low effort, consistent payoff.
The rule that breaks most implementations
Your schema must match what is visible on the page. Every time.
If your markup says a product is in stock and the page says sold out, or your schema lists a price the page does not show, AI systems catch the mismatch and stop trusting the page. Auto-generated schema that does not match visible content can trigger quality penalties.
This is why bulk schema plugins fail so often. They generate valid code that does not reflect the actual page. Valid and accurate are not the same thing. A plugin can pass the validator and still be wrong.
How to implement schema without breaking things
The process is not complicated:
Add a JSON-LD script block to each page type: product pages, category pages, blog posts, and your homepage.
2. Validate every template with Google's Rich Results Test before you ship. It confirms your syntax is correct and tells you separately whether you qualify for product snippets and merchant listings.
3. Align your schema with your Google Merchant Center feed if you run Shopping ads. A schema-to-feed mismatch causes ad disapprovals.
4. Monitor the Enhancements section of Google Search Console for errors and warnings. Prioritize high-impression pages first, since that is where better markup returns the most.
5. Remove deprecated markup: FAQ, How-to, and Practice Problem.
Do this at the template level, not page by page. One clean Product template applied across every product page beats hand-coding a hundred pages and getting three of them wrong.
Where schema fits in a complete AEO strategy
Schema markup is necessary but not sufficient. It makes your content readable and citable. It does not create the authority or the content worth citing in the first place.
The full picture is clean structured data, answer-first content, real authorship signals, and a brand that AI systems already recognize. Schema is the layer that ties those together into something a machine can trust and quote.
If you want the rest of the stack, read How to Rank on ChatGPT: What Actually Works for the content side, What Is Generative Engine Optimization (GEO)? for how AI systems choose their sources, and AEO vs GEO vs SEO: What's the Difference? if you are still mapping where these disciplines overlap.
The honest takeaway
Schema markup in 2026 is no longer a rich-snippet nice-to-have. It is the difference between being a source an AI can cite and being invisible to it.
Get Organization, Product, Review, and Breadcrumb right. Match your markup to your visible pages. Drop the deprecated types. That covers the large majority of what ecommerce brands need.
At Odd Logic, structured data is part of the Search and AI Visibility work we do for ecommerce brands, alongside answer-first content and reputation signals. We are a newer agency, so we are not going to point to a decade of case studies we do not have. What we will do is implement your schema correctly, tie it to your content and your Merchant Center feed, and show you where your products are and are not getting picked up in AI answers. If closing that gap is the job, that is the job we do.