Schema.org Review Markup: A Step-by-Step Walkthrough That Lifts CTR 35 Percent
How Schema.org Review and AggregateRating markup turn reviews into rich-result stars in Google Search. Implementation walkthrough for Shopify, WordPress, custom sites. Plus the validation tools that catch errors before they hit production.
Schema.org Review markup is one of the highest-ROI SEO investments most small businesses skip. Properly implemented, it lifts click-through rates from Google Search results by 30 to 40 percent compared to identical pages without schema. The work is configuration, not custom development. Most modern e-commerce platforms (Shopify, WooCommerce, BigCommerce) and CMS systems (WordPress with Yoast or RankMath, Squarespace, Wix) support schema natively or through plugins.
This piece is the implementation walkthrough. What schema to use, how to validate, what trips up most implementations, and platform-specific instructions for the most common stacks.
What Schema.org Review markup does
Schema.org provides standardized structured-data formats that tell search engines about specific content types. For reviews, two main schemas matter:
- Review: Individual review with author, rating, body, date
- AggregateRating: Summary rating across multiple reviews (average, count, best/worst values)
When Google's crawler reads a page with valid Review or AggregateRating markup, it can display:
- Yellow star ratings in search-result snippets
- Review counts ("based on 247 reviews")
- Aggregate ratings under product names in Shopping results
- Rich-result placements in some featured snippets
The visual difference between a result with rich-result stars and one without is dramatic on the search results page. The 30-to-40-percent CTR lift is the conversion equivalent of bumping up two ranking positions, without actually changing your ranking.
The required fields
For AggregateRating to be eligible for rich-results display, four fields are required:
{
"@context": "https://schema.org",
"@type": "AggregateRating",
"ratingValue": "4.6",
"reviewCount": "127",
"bestRating": "5",
"worstRating": "1"
}
The schema is JSON-LD format, embedded in a <script type="application/ld+json"> tag in your page HTML, typically in the <head> or right before </body>.
For individual Review markup, additional required fields:
{
"@context": "https://schema.org",
"@type": "Review",
"author": {
"@type": "Person",
"name": "Jane Doe"
},
"reviewRating": {
"@type": "Rating",
"ratingValue": "5",
"bestRating": "5"
},
"datePublished": "2026-01-15",
"reviewBody": "Excellent service, would recommend."
}
In practice, Review markup is usually combined with the schema for the parent entity (Product, LocalBusiness, etc.) and AggregateRating to give Google the full picture.
Platform-specific implementation
Shopify
Most Shopify themes support Review schema through the Yotpo, Stamped, or Loox apps. Each app injects schema automatically when you display reviews on product pages.
To verify: open a product page with reviews, view the page source, search for application/ld+json. You should see schema referencing Product, AggregateRating, and Review entities.
If schema is missing, the most common cause is theme customization that removed the Liquid template hooks where the apps inject schema. Re-installing or contacting the app support usually fixes it.
WordPress
WordPress with Yoast SEO or RankMath plugins handles schema injection through the SEO plugin's settings. Both plugins offer Schema configuration panels under their respective settings menus.
For e-commerce on WordPress (WooCommerce), the Schema and Structured Data plugin or Yoast's WooCommerce Schema add-on handles Product + Review + AggregateRating injection.
Custom sites
For custom-built sites or sites without a CMS, you embed the JSON-LD directly in HTML. Most modern static-site generators (Next.js, Hugo, Astro) support schema through templates.
Example for a service detail page:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Your Business Name",
"image": "https://yoursite.com/logo.png",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "City",
"addressRegion": "State",
"postalCode": "12345"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.7",
"reviewCount": "89"
}
}
</script>
Validating your markup
Two validation tools every implementation should pass:
1. Google Rich Results Test: search.google.com/test/rich-results
Paste your URL or HTML. The tool reports whether Google considers the page eligible for rich results, which schemas it detected, and any errors or warnings.
2. Schema.org Validator: validator.schema.org
Paste your URL or HTML. The tool validates against the full Schema.org specification and reports any violations.
Run both tools after every schema change. Errors that pass one but fail the other are usually edge cases that work in practice but might break with future updates.
Common implementation errors
Five errors that prevent rich-result display:
1. Missing required fields. AggregateRating without ratingValue or reviewCount fails. Schema.org docs list required fields for each schema type.
2. Schema for content not visible on the page. Google requires that schema describes content actually visible on the page. Adding Review markup for reviews not displayed on the page is a violation that gets the page de-indexed for rich results.
3. Wrong schema for the page type. AggregateRating belongs on pages that aggregate multiple reviews (product detail pages, service detail pages). It does not belong on the home page if reviews are not displayed there.
4. Invalid ratingValue ranges. ratingValue must fall within the bestRating-worstRating range. A 6-out-of-5 rating fails validation.
5. Missing required parent entities. AggregateRating must be inside a parent entity (Product, LocalBusiness, Service, etc.). Standalone AggregateRating without a parent is invalid.
What rich results look like
When working correctly, your Google search snippet shows:
- Yellow stars below the page title
- Numerical rating (e.g., "4.7")
- Review count (e.g., "Rating: 4.7 based on 127 reviews")
These elements appear directly in the SERP without the user clicking through. The visual prominence is what drives the 30-to-40-percent CTR lift.
How Review Manager fits Schema.org strategy
Review Manager is built primarily for the customer-side review-collection workflow. The Schema.org markup specifically requires reviews on your own site (not Google Business Profile reviews, which Google handles natively).
Where Review Manager helps:
- For businesses also collecting reviews via Trustpilot or other platforms that provide widgets, Review Manager's branded short URL drives customers to those collection surfaces
- Auto-routing landing page captures unhappy customers privately, keeping the on-site review pool higher quality
- 14-day free trial on Pro and Business
For pure on-site product reviews with Schema.org, dedicated tools like Yotpo, Loox, Stamped, or the WordPress plugins above handle the workflow more directly than Review Manager.
The free tier covers a single platform. Pro at 5.99 EUR per month adds custom branding. Business at 19.99 EUR per month supports up to 5 review links.