Start with valid JSON-LD
Use Google’s Rich Results Test and Schema Markup Validator after schema changes. Fix errors before worrying about enhancements.
Keep reviews honest
Review stars should come from real customer reviews that are visible to shoppers. Hardcoded testimonials are not a substitute.
Do not fight the theme
If an app already emits schema, decide which source owns each property. Two competing Product objects can create contradictory signals.
Performance still matters
Rich-result eligibility does not excuse slow product pages. Product images, app scripts, and layout shifts affect real shoppers and search quality.
Related reading
Topic hub
This guide belongs to the trust hub hub.
Sources
FAQ
Which test should I use?
Use Google Rich Results Test for eligibility and Schema Markup Validator for broader schema validation.
Can I force rich results?
No. You can make pages eligible, but Google decides what to show.
Do reviews need to be visible?
Yes. Review markup should match reviews shown on the page.