SEO

Product Schema

Also called Product markup, product structured data

Structured data describing one product for sale, including its price, identifiers and stock state.

Quick facts: Product Schema

Category
SEO
Also called
Product markup, product structured data
Level
Intermediate
Affects
Product rich results, click-through from search, shopping surfaces
Where to see it
Rich Results Test, Schema Markup Validator, Google Search Console, Merchant Center
In this article4
  1. How Product schema works
  2. Why Product schema matters
  3. Common mistakes with Product schema
  4. How to act on it

How Product schema works

Product schema describes one item for sale in terms a machine can act on. The identity properties cover the name, the image, a description and the brand, plus whichever product codes apply — an internal SKU, a manufacturer part number, or a global trade item number where the product has one.

The commercial detail sits in a nested offers block: the price, the currency it is quoted in, the availability state, and often the seller and the conditions of the offer. Where genuine customer ratings exist on the page, an aggregate rating can be attached as well.

When the markup is complete and honest, the product becomes eligible for the richer treatment search engines give shopping results — the price and stock state shown under the listing rather than a plain blue link. Eligible is the operative word: qualifying makes the enhanced result possible, never certain.

Why Product schema matters

A shopper comparing options scans results for price and availability before they click. A listing that answers both questions in the result itself is competing on different terms from one that makes them find out, and that difference in click-through is the practical value of the markup — not a ranking effect.

It also underpins the parts of search that draw on product data rather than page text, including free product listings and the feeds that connect a shop to shopping surfaces. For a store selling across borders, which is common for Nepal-based sellers reaching customers abroad, the currency and availability a customer sees must match what the markup declares for their market, or the result is worse than no markup at all.

Common mistakes with Product schema

The serious one is a price in the markup that disagrees with the price on the page. It happens innocently — a sale changes the displayed figure while the schema is generated from a cached field — but it is treated as misrepresentation, and it is one of the more common reasons a site collects a manual action for spammy structured markup.

The next is scope. Product markup is meant for a page about one specific product; applying it to a category listing, a blog post that mentions products, or a service page describing what you do is markup that does not match the page. Stale availability belongs in the same family: schema that still says in stock after the item has sold out sends shoppers to a dead end and teaches them not to trust the listing.

How to act on it

Generate the markup from the same data that renders the page, so price, stock and title cannot drift apart. Most ecommerce platforms will do this if configured properly; the failure usually comes from a plugin reading a different field, so test a real product page rather than trusting the settings screen.

Validate with the Rich Results Test, then watch the enhancement reports in Google Search Console — that is where errors on live pages appear once you have moved on. Check a sale item, an out-of-stock item and a product with variants specifically, since those three break most often. If the catalogue is large enough that manual checks are impractical, treat structured data as a standing part of ecommerce SEO and monitor it rather than setting it once.

Do and do not

Do

  • Generate markup from the same data the page renders
  • Test a sale item and an out-of-stock item
  • Keep availability updated as stock changes

Do not

  • Apply product markup to category or listing pages
  • Publish a price the visitor will not see
  • Invent product identifiers the item does not have

Questions people ask about this

Can I use Product schema on a category page?

No. Product markup describes one specific product, and a category or listing page shows many, so the markup would not match the page. Search engines have separate handling for listing pages. Describe individual products on their own product pages, and let the category page do its job of navigation and internal linking.

What happens if my schema price is out of date?

At best the search result shows a price the shopper will not find on the page, which costs you trust and a click. At worst it is treated as misrepresentation and the site collects a manual action for spammy structured markup, removing rich result eligibility until it is fixed. Generate the markup from live product data, never from a static field.

Do I need product codes like GTIN in the markup?

Include them when the product genuinely has one, because identifiers help match your listing to the same item elsewhere and are important for shopping surfaces. For handmade, custom or own-brand goods with no manufacturer code, use the identifiers you do have, such as your own SKU and brand, and leave the rest out rather than inventing values.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.