Schema Markup for Magento Product Pages: 5 Types You Need
Schema markup for Magento product pages: the five types you need
Magento product pages want four schema types as a baseline — Product, Offer, BreadcrumbList and, only where you display genuine reviews, AggregateRating — with FAQPage on pages that carry a real question-and-answer section. Emit them accurately as JSON-LD and your pages become eligible for rich results such as price, availability and star ratings (eligibility, never a guarantee: Google decides per query), and far easier for AI search engines to parse and cite. Note that FAQ rich results are now shown only for a narrow set of authoritative sites, so mark up FAQs for the machine-readability and the citation, not for an accordion in the SERP.
Schema markup is how you state a page's facts in a machine's own language: not "here is some text that mentions a product", but "this is a product, this is its price and currency, this is its rating and the number of reviews behind it". Search engines no longer have to infer what your page is — you have told them. Here is what each type does, what it earns you, and how to implement the set properly on a Magento 2 store.
The five types at a glance
| Schema type | What it states | What it earns in search |
|---|---|---|
| Product | Name, description, brand, SKU/GTIN, image | Eligibility for every product rich result — the foundation |
| Offer | Price, currency, availability | Price and stock status shown directly in the listing |
| AggregateRating | Star rating and review count | Stars in the search result — a visible click-through advantage |
| BreadcrumbList | Site hierarchy (Home › Category › Product) | A readable trail in the result instead of a raw URL |
| FAQPage | Question-and-answer pairs on the page | Expandable Q&A in the listing; quote-ready text for AI engines |
1. Product — the foundation
Product schema declares the item itself: name, description, brand, SKU or GTIN, and image. Without it a search engine is guessing that the page is a product page at all, and nothing else in this list can attach. Map it from real attribute data — the same accurate name, identifier and imagery you would send to a Google Shopping feed — so every channel describes the product identically.
2. Offer — price and availability
Nested inside Product, the Offer states the price, the currency and whether the item is in stock. This powers the price and stock status that can appear directly in search results, and it is exactly the data an AI shopping assistant reads when it compares your listing against a rival's. Stale Offer data is worse than none: a price on the page that contradicts the markup undermines the whole implementation.
3. AggregateRating — the stars
If you collect reviews, AggregateRating emits the average score and the review count. Stars make a listing visibly different from the plain links around it, which is why review markup is one of the most sought-after rich results — an advantage on rankings you already hold, at no media cost. It must reflect genuine on-page reviews; marking up ratings the visitor cannot see is against Google's guidelines.
4. BreadcrumbList — the trail
BreadcrumbList replaces the raw URL in your search listing with the site hierarchy: Home › Category › Product. It gives the searcher context before the click, mirrors the navigation crawlers use to understand your structure, and makes the listing look tidier and more established.
5. FAQPage — the answers
If your product page answers common buyer questions, FAQPage markup can surface them as an expandable accordion in the result — more space in the listing, objections answered before the click, and precisely the question-and-answer format AI engines prefer to quote. Keep each answer short, self-contained and identical to what the page displays.
Implementing it on Magento 2, step by step
Default Magento themes emit only fragments of product microdata — there is no complete, valid JSON-LD implementation of all five types out of the box. Closing the gap looks like this:
- Audit what you emit today. Run a product URL through Google's Rich Results Test and note which types are detected, which carry warnings, and which are missing entirely.
- Standardise on JSON-LD. It is the format Google recommends, and it keeps the markup in one script block instead of scattered through the template — far easier to keep valid as the theme changes.
- Map from live product data. Name, SKU, brand attribute, image, price and stock status must come from the catalogue itself, not hand-written snippets, so the markup updates the moment the product does.
- Validate, then fix the warnings. Invalid markup earns nothing. Retest after fixes, and re-check whenever the theme or the attribute set changes.
- Monitor in Search Console. Its rich-result reports show which pages are eligible, which have errors, and whether a change quietly broke markup across the catalogue.
The two rules that govern all five steps: the markup must match what is visible on the page — mismatches can draw a manual action — and it must stay valid across thousands of products as prices, stock and reviews change daily. That is a synchronisation job, not a snippet job, which is why we built Schema Discovery for Magento to emit and maintain the full set automatically from live catalogue data.
Where schema fits in the bigger picture
Structured data is one line of the wider 2026 Magento SEO checklist, but it is the line doing double duty: the same markup that wins rich results in Google is a primary signal AI search engines use when deciding which pages to cite. Stores that keep it accurate are legible to both kinds of engine at once. Schema Discovery ships as part of the AgenticEcom Suite alongside the rest of the SEO layer.
FAQ
What schema markup do Magento product pages need?
Five types: Product (the item), Offer (price and availability), AggregateRating (stars and review count), BreadcrumbList (site hierarchy) and FAQPage (question-and-answer pairs). Together they qualify the page for rich results in Google and make it citable by AI search engines.
Does schema markup improve rankings directly?
No — Google treats structured data as an eligibility signal for rich results rather than a ranking factor. The gain comes from the richer listing itself, which stands out and tends to earn more clicks from positions you already hold, and from AI engines that lean on schema to understand and cite pages.
Does Magento 2 output schema markup by default?
Only fragments. Default themes include partial product microdata, but not a complete, valid JSON-LD set covering Product, Offer, AggregateRating, BreadcrumbList and FAQPage. Most stores add it via a module or theme work.
What is the hardest part of Magento schema markup?
Keeping it accurate at scale. The markup must match the visible page and stay valid across thousands of products while prices, stock and reviews change constantly — which is why automated emission from live catalogue data beats hand-coded snippets.