Reviewed by the SEOPointz team · Last reviewed June 2026. Markup requirements here reflect Google’s current Product and merchant listing documentation. SEOPointz may earn a commission from some links; it never changes what we recommend.
Two stores can sell the same product at the same price, and one will get a search result with a star rating, a price, and an “In stock” label while the other gets a plain blue link. The difference is usually structured data — the machine-readable layer that tells Google exactly what your page is selling. Product schema markup is how you earn those richer listings, and the good news is that adding it has gotten far easier than the hand-coded JSON of a few years ago. The catch is that “adding schema” and “earning rich results” are not the same thing, and most stores get tripped up on the gap between them.
What product schema actually unlocks
Product structured data feeds two related experiences in Google. Product rich results can show ratings, price, and availability on a normal search listing. Merchant listing experiences — the shopping-style results — can surface your products in places like the Shopping tab and the popular-products carousels. Importantly, you can now be eligible for merchant listings by providing product data directly on your pages, without a Google Merchant Center account, as long as the page is one where a shopper can actually buy the item. Pages that merely link out to another retailer don’t qualify.
The properties Google actually wants
A Product needs a small core to be valid: name, an image, and an offers block containing price, priceCurrency, and availability. That’s the floor. To compete for the richer treatment, fill in the recommended fields too — brand, a sku or gtin (the barcode), description, and review data where you genuinely have it. Google uses identifiers like GTIN to match your product against known items, and listings with complete, accurate data tend to be favored. Availability must use Schema.org’s fixed values (InStock, OutOfStock, PreOrder, BackOrder, Discontinued) and should update automatically as stock changes — markup that claims InStock on a sold-out page erodes trust fast.
The fastest way to add it: let a plugin do it
On WordPress and WooCommerce you almost never need to write JSON-LD by hand. An SEO plugin reads your real product data — price, stock, SKU — and outputs schema that stays in sync automatically, which is exactly what you want for availability. There’s a meaningful difference between the popular options, though.
| Method | Product schema for WooCommerce | Cost | Best for |
|---|---|---|---|
| Rank Math | Built into the free version | Free (Pro optional) | Most WooCommerce stores |
| Yoast SEO | Needs the WooCommerce SEO add-on | Free core + paid add-on | Stores already standardized on Yoast |
| Dedicated schema plugin | Yes, granular control | Varies | Complex or non-standard catalogs |
| Manual JSON-LD | Full control, manual upkeep | Free (your time) | Custom builds and developers |
The honest note on Yoast: its free plugin does not output Product schema for WooCommerce products on its own — that requires the paid WooCommerce SEO extension. Rank Math includes product schema in its free tier. Neither is “better” in a vacuum, but if budget matters and you’re choosing fresh, that distinction is worth knowing before you commit.
The rule that breaks more sites than missing markup
Only one source should generate product schema. If you run two SEO plugins, or an SEO plugin plus a standalone schema tool, you can end up with duplicate or conflicting Product blocks on the same page — and Google often responds by ignoring the markup entirely. Before activating schema in a new plugin, disable schema output in the old one. This single conflict is behind a large share of “I added schema but nothing shows up” complaints.
Test it, then watch it
After adding markup, run the page through Google’s Rich Results Test. It tells you which rich result types were detected, flags warnings for missing recommended fields, and shows critical errors for missing required ones. Fix the errors first — warnings are optional polish. Then track the Merchant listings and Product snippets reports in Search Console over the following weeks. Remember that eligibility is not a guarantee: valid markup makes you a candidate for rich results, but Google decides when and whether to show them. Clean, complete, honest data is how you tilt that decision in your favor.
Frequently asked questions
Will product schema guarantee star ratings in search?
No. Markup makes you eligible, not entitled. Google chooses when to display rich results, and review snippets specifically require genuine, qualifying review data — product reviews are eligible to show, but self-serving business reviews on your own site are not.
Do I need a Google Merchant Center account?
Not for basic merchant listing eligibility. You can qualify by marking up purchasable product pages directly. A Merchant Center account and feed still help for paid Shopping and give you more control, but they’re no longer a hard requirement for the organic listings.
Why did my rich result disappear after it showed up?
Common causes are availability or price data that went stale, a second plugin injecting conflicting schema, or Google simply choosing not to display it for some queries. Re-run the Rich Results Test and confirm only one plugin is producing the markup.
Markup is the plumbing; the content it describes still has to earn the click. Strengthen the signals that ride alongside your schema with our guides to product reviews and SEO and using FAQs on product pages to capture featured snippets.
