- A page presents one purchasable product.
- A SaaS offer has one clear product and visible price.
- A merchant needs offer, availability, shipping, or return fields.
- An editorial product review needs product snippet logic.
Examples and reference
Match Product markup to the real purchase and review model
Product examples need one clear product focus, visible commercial data, accurate offers, genuine reviews, and a decision between product snippet and merchant listing requirements.
Example library
5 decisions
6 checks
Reviewed 2026-07-27
Current platform reality
Separate Schema.org meaning from Google feature eligibility.
Reviewed 2026-07-27
Google distinguishes product snippets from merchant listings. SaaS and digital product pages should use Product only when the visible page genuinely presents one product and the fields can be maintained.
Use and avoid
Apply the type only when the visible role and evidence support it.
- Using Product on category or comparison hubs.
- Adding price or availability that differs from the page.
- Inventing ratings.
- Mixing merchant listing and editorial review assumptions.
Implementation model
Make the page role, identity, fields, and validation decisions in order.
Choose the product path
Decide product snippet, merchant listing, or semantic product identity.
Confirm one product focus
The page must primarily describe the named product.
Match the offer
Use current visible price, currency, availability, and URL.
Add genuine review data only
Follow review snippet rules and visible content requirements.
Maintain commercial fields
Set owners and update triggers for price and availability.
Acceptance checks
Do not approve the markup because the JSON parses.
The content, entity ownership, canonical URLs, policy state, and maintenance source must also pass.
One product
The URL is not a broad category or multi item comparison.
Offer accuracy
Price, currency, availability, and URL match.
Review compliance
Reviews are genuine, visible, and specific.
Brand identity
The brand references a stable Organization.
Policy ownership
Shipping and return data are maintainable.
Correct Google path
The selected requirements match the intended product feature.
Implementation examples
Use the examples as a starting structure, not production data.
Replace every placeholder with approved visible values. The examples do not create eligibility or guarantee a search appearance.
Product with a visible offer
Copy exampleProduct identity without rating data
Copy examplePrimary sources
Use current Google and Schema.org documentation as the source of truth.
Google structured data introduction
Open the official sourceGoogle general structured data guidelines
Open the official sourceGoogle structured data testing tools
Open the official sourceGoogle product structured data overview
Open the official sourceGoogle review snippet rules
Open the official sourceSchema.org Product
Open the official sourceQuestions
Product Schema Examples for SaaS and SEO Product Pages questions.
What is the difference between a product snippet and merchant listing?
Product snippets suit pages without direct purchase, while merchant listings support richer commerce fields for pages where customers can buy.
Can a SaaS page use Product?
Yes, when one visible product and offer are the clear page focus.
Should every product include ratings?
No. Add only genuine visible review data that follows the current rules.
Can the examples be copied unchanged?
No. Replace placeholders with approved current data and validate the live page.
Next route
Prepare schema cues after visible copy, entity ownership, and URLs are approved.
MIRENA can audit the page role, identity, fields, current feature support, and validation route. Production markup still needs human review and live testing.
Founder access is €20 every 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.