Review schema

Definition

Review schema refers to specific types of structured data markup, using the Schema.org vocabulary, that are added to a webpage’s HTML code. This markup explicitly identifies content as being a review or a collection of ratings for a particular item, such as a product, service, business, recipe, movie, book, or other entity. It helps search engines like Google understand the details associated with the review, including what is being reviewed, the rating score provided (often on a 1-5 scale), the author of the review, and the review text itself.

The primary Schema.org types involved are:

• Review: Used to mark up individual reviews.
• AggregateRating: Used to mark up an average rating score based on multiple ratings or reviews.

These types are typically embedded (“nested”) within the schema markup of the item being reviewed (e.g., within Product, LocalBusiness, Restaurant, Hotel, Recipe schema). Proper implementation of Review schema can make a webpage eligible for “Review Snippets” (rich results displaying star ratings ☆☆☆☆☆) in Google search results, potentially increasing visibility and click-through rates (CTR).

Is It Still Relevant?

Yes, Review schema remains highly relevant and valuable for SEO in 2025, particularly for websites featuring products, services, or content where reviews significantly impact user decisions.

• Rich Result Eligibility: It’s the primary way to enable star ratings (review snippets) to appear directly in search results. These visual cues make listings stand out and can significantly boost CTR.
• Enhanced Visibility & Trust: Star ratings act as immediate social proof, building user trust even before they click through to the site. This can be crucial for businesses in competitive markets, like hotels or restaurants in Pattaya.
• Improved Search Engine Understanding: It provides clear, structured information about user sentiment and ratings associated with specific items, helping search engines better understand the entity being reviewed.
• Competitive Edge: Pages displaying review snippets often attract more attention and clicks compared to plain blue link results for similar items.
• Data for AI Features: Structured review data can be used by Google to inform AI-driven features, voice search answers, and knowledge panels, providing richer context about products or businesses.

However, its relevance is strongly tied to adhering to Google’s strict implementation guidelines. Misuse (e.g., marking up fake reviews, self-serving reviews incorrectly, or violating third-party review rules) can lead to the rich snippet not being shown or, in severe cases, manual actions.

Real-world Context

Review schema is widely used across different types of websites:

• E-commerce Site (e.g., selling local Pattaya crafts): A product page for a handmade item uses Product schema. Nested within it is an AggregateRating schema summarizing reviews collected directly from customers on that page (e.g., “Rating: 4.7 stars based on 25 reviews”). This can enable stars in the SERP listing for the product.
• Recipe Blog (e.g., featuring Thai recipes): A blog post with a Pad Thai recipe uses Recipe schema. It includes an AggregateRating section reflecting ratings submitted by users in the comments section, potentially showing stars in recipe search results.
• Hotel Booking Site (Aggregator): A site like Agoda or Booking.com displaying a hotel in Pattaya might use Hotel schema and include AggregateRating based on reviews collected on their platform. Google has specific guidelines for how third-party sites can display reviews.
• Local Business Website (e.g., a Spa in Pattaya): The spa collects testimonials on its own website. They might use LocalBusiness (or subtype HealthAndBeautyBusiness) schema and add an AggregateRating. **However, Google is often less likely to show rich snippets for `AggregateRating` added directly by the local business itself (considering it potentially self-serving) compared to ratings from independent platforms or for products/recipes.** Google often prefers showing its own Google Reviews stars for local businesses in the Local Pack.
• Affiliate Review Article: A travel blogger writes a detailed review of a specific Pattaya tour package. They might use Review schema to mark up their individual assessment and rating of the tour (which might be considered a Product or Service). This could potentially enable a review snippet for their article in search results.

The key is aligning the implementation with the specific content type and Google’s guidelines for that type.

Background

Review schema originated as part of the Schema.org collaborative initiative launched in 2011 by Google, Bing, Yahoo!, and Yandex. The goal was to create a standardized vocabulary for structured data markup to help search engines better understand web content.

• Early Inclusion: Types like Review and AggregateRating were included early on, recognizing the importance of user opinions and ratings online.
• Rich Snippet Incentive: Google incentivized adoption by introducing “rich snippets” – enhanced search results displays. Star ratings derived from Review schema quickly became one of the most visible and sought-after rich snippets.
• Guideline Development: As adoption grew, so did instances of misuse (e.g., spammy implementation, marking up hidden reviews, misleading ratings). This led Google to develop and refine specific, stricter guidelines over the years for implementing Review schema correctly. Key clarifications addressed:
  • Visibility requirement (markup must match visible content).
  • Prohibition against marking up reviews paid for or controlled by the business being reviewed in certain contexts (self-serving reviews).
  • Rules for associating reviews clearly with the specific item reviewed.
  • Criteria for using AggregateRating.
  • Rules concerning third-party review markup.
• Focus on Authenticity: The evolution of guidelines reflects Google’s ongoing effort to ensure that review snippets shown in search results are based on authentic, trustworthy, and correctly attributed review data.

What to Focus on Today

To implement Review schema effectively and responsibly in 2025, follow these best practices:

• Identify Valid Use Cases: Determine where genuine reviews or ratings exist on your site (e.g., product pages, user-submitted recipe ratings, detailed review articles).
• Select Correct Schema Types: Use Review for individual reviews, AggregateRating for summaries. Nest them within the most specific schema type for the item being reviewed (Product, Recipe, Book, Movie, LocalBusiness, etc.).
• Strictly Adhere to Google Guidelines: This is non-negotiable. Carefully read the official Google Search Central documentation for Review snippets and any specific guidelines for your content type (e.g., Product, Recipe, Local Business). Pay close attention to rules about:
  • Content visibility.
  • Self-serving reviews (especially for LocalBusiness/Organization).
  • Third-party reviews.
  • Required and recommended properties for each type.
• Use JSON-LD: Implement the markup using JSON-LD format, typically in the <head> or <body> of your HTML.
• Ensure Data Accuracy: The structured data must accurately reflect the review information visible on the page. Do not manipulate ratings or review counts in the markup.
• Validate Thoroughly: Test your implementation using:
  • Schema Markup Validator (schema.org): To check Schema.org syntax.
  • Google’s Rich Results Test: To check validity against Google’s requirements and eligibility for review snippets. Fix any errors or warnings reported.
• Prioritize Authenticity: Focus on collecting genuine reviews from real customers or providing authentic, detailed review content.
• Monitor Performance: Use Google Search Console to track the performance of pages with Review schema (via Performance report filtered by “Review snippet” appearance) and monitor the relevant Enhancement report for errors or warnings.

Correctly implemented Review schema can significantly enhance SERP visibility, but strict adherence to Google’s guidelines is essential for eligibility and to avoid potential issues.

Back to Glossary