What Is Product Schema? How It Works

Product schema is structured markup in a product page's HTML. It uses the schema.org vocabulary to describe the item and its offer. Google reads this data to understand the name, price, availability, and rating. The markup belongs on a single-product page or a page for variants of one product.

How Product schema works

Google reads Product schema through separate requirements for product snippets and merchant listings. Product snippets can add details such as ratings, price, and availability to a text result. Merchant listings apply to pages where shoppers can buy the item and support more shopping details.

The markup uses schema.org's Product type and nests an Offer with price, currency, and stock status. Google's product guidance says a page that meets merchant-listing rules can also qualify for product snippets. Product snippets need a name and either an offer or rating. Merchant listings need a name, image, and offer.

A product feed sends store data to a platform such as Google Merchant Center. Product schema stays in the page HTML. The two can carry overlapping facts.

Valid markup only makes a page eligible. Google's structured data guidelines say its systems may still show a normal text result when that fits the searcher better.

Why Product schema breaks on a dropshipping catalog

Product schema breaks when a supplier change leaves the page, markup, and Merchant Center item showing different values. Dropshipping stores often import price and stock data. A delayed sync can make the visible offer disagree with the JSON-LD or feed.

Google compares Merchant Center data with the landing page and its structured markup. Its landing-page guidance warns that JavaScript markup can make Shopping crawls less reliable when price or stock changes quickly. A mismatch can lead Google to update an item or disapprove it.

Suppose a supplier marks a blue shirt variant out of stock. The buy button changes to "sold out," but the schema Offer still reports InStock. Google's next crawl sees two stock states for the same variant.

Match the page's price and stock with the schema Offer and Merchant Center item. Repair the supplier sync that caused the gap. Google's automatic updates can fix an occasional error, but they don't replace regular data updates. Google may still disapprove items that change often or have many mismatches.

FAQ

Does Product schema have to use JSON-LD?

Product schema can use JSON-LD, Microdata, or RDFa. Google recommends JSON-LD because it's easier to maintain, but all three formats can qualify.

Do I need Product schema if I already have a product feed?

A feed and Product schema can work together, but Google Search can use either source. Using both gives Google more ways to understand and verify your product details, provided the values match.

What's the difference between a GTIN and an MPN?

A GTIN is global, while an MPN is unique only within one maker's catalog. Use the maker's real codes because made-up values can cause Merchant Center errors or disapprovals.