Do video testimonials convert better than text reviews? Discover the data behind video vs text testimonials, when to use each, and how to combine both for maximum conversions, trust, and SEO impact.
What Rich Snippets Are and Why They Matter
When you search for a product or service on Google and see some listings with star ratings, review counts, and reviewer names displayed directly beneath the title and URL — that's a rich snippet. Rich snippets are the visual enhancements that search engines apply to certain listings when they detect structured data code embedded in the page's HTML.
For testimonials and reviews, the relevant rich snippet type is the review star rating: a line of orange or yellow stars, typically followed by an average rating score and a review count. This display is not granted to all pages — only those that have correctly implemented Review or AggregateRating schema markup and meet Google's quality standards for the content.
The commercial value of this feature is substantial. Studies consistently find that listings with star ratings in search results achieve 15–30% higher click-through rates than equivalent listings without them — at the same ranking position. This means that two websites ranked equally on a search results page will receive fundamentally different amounts of traffic based solely on whether one has star ratings displayed. For high-competition commercial keywords, this CTR advantage can be worth as much as a one or two position ranking improvement.
And unlike ranking improvements — which require sustained, resource-intensive SEO work — implementing schema markup is a one-time technical task. Once it's in place and Google starts displaying your rich snippets, the CTR benefit is essentially permanent for as long as your structured data is valid.
FEATURED Q&A What is schema markup for testimonials? Schema markup for testimonials is structured data code added to a web page's HTML that communicates to search engines — in a formal, machine-readable format — that the page contains customer reviews and ratings. When implemented using Review or AggregateRating schema from the Schema.org vocabulary, and when Google determines the content meets its quality standards, Google may display star ratings, average scores, and review counts directly in search results as 'rich snippets.' These visual enhancements significantly increase click-through rates without requiring a higher ranking position. |
The Two Schema Types You Need to Understand
Review Schema (Individual Reviews)
Review schema is used to mark up a single, individual customer review or testimonial. The required properties are: @type (must be 'Review'), author (the customer's name, as a Person type), reviewRating (containing a Rating type with ratingValue and bestRating), reviewBody (the text of the review), and itemReviewed (the product, service, or business being reviewed).
Optional but valuable properties: datePublished (the date of the review — important for freshness signals), reviewAspect (which specific aspect of the product or service the review addresses), and publisher (for platform-hosted reviews).
AggregateRating Schema (Aggregate Ratings)
AggregateRating schema is used to mark up a summary rating that represents multiple reviews. You've seen this in practice when a Google listing shows '4.8 stars (347 reviews)' — that display is powered by AggregateRating schema. Required properties: @type (must be 'AggregateRating'), ratingValue (the average score), reviewCount or ratingCount (the number of reviews in the aggregate), bestRating (the maximum score, typically 5), worstRating (the minimum score, typically 1).
AggregateRating is most powerful when added to your product or homepage — it's the schema that produces the summary star rating line in search results. Individual Review schema produces individual review display. Combining both types gives Google the most complete picture of your review landscape.
Implementation Method: JSON-LD (Google's Recommended Approach)
There are three ways to add schema markup to a page: JSON-LD (JavaScript Object Notation for Linked Data), Microdata, and RDFa. Google explicitly recommends JSON-LD for all new implementations, and it is the easiest to implement and maintain.
JSON-LD is added as a script tag in the <head> or <body> of your HTML — it doesn't require any changes to your visible page content, and it doesn't need to be physically adjacent to the content it's describing. This means you can add it programmatically without redesigning your page.
Here is a complete, valid JSON-LD implementation for a SaaS product page with both AggregateRating and individual Review markup:
|
Schema Types by Business Category
Using the correct parent schema type is critical — Google's eligibility criteria for rich snippets varies by schema type, and using a mismatched type can prevent your rich snippets from appearing even if your schema is technically valid.
Business Type | Parent Schema Type | Use With |
SaaS / Software | SoftwareApplication | AggregateRating + Review |
Local service business | LocalBusiness | AggregateRating + Review |
E-commerce product | Product | AggregateRating + Review |
Online course | Course | AggregateRating + Review |
Physical product | Product | AggregateRating + Review |
Professional service | Service | Review (AggregateRating more limited) |
Gridapps and Schema: Automatic Implementation
Gridapps testimonial widgets automatically generate valid JSON-LD schema markup for all embedded testimonials and aggregate ratings. When you embed a Gridapps widget on your site, the structured data is injected as part of the widget's output — you do not need to write, maintain, or update any schema code manually.
This means every testimonial you collect and publish through Gridapps is immediately eligible for Google rich snippets from the moment it's embedded on your site. As you add new testimonials and your aggregate rating updates, the schema is automatically updated to reflect the new count and average score. There is no manual intervention required at any point.
Gridapps also ensures that your schema stays compliant with Google's regularly updated structured data guidelines. Google has made several revisions to its review schema requirements over the past three years — changes that invalidated implementations that hadn't been maintained. Gridapps schema is updated automatically to remain compliant.
The Seven Most Common Schema Implementation Mistakes
Mistake 1: Marking Up Self-Written Testimonials as Customer Reviews
Google's review structured data guidelines explicitly prohibit marking up testimonials that were written or curated by the business rather than submitted organically by genuine customers. If your schema describes testimonials that you wrote yourself (or that you significantly edited), you risk a manual review action that removes your rich snippets and can impact other aspects of your site's trust signals in Google Search.
Mistake 2: Inconsistency Between Schema Data and Visible Content
The rating, review count, and review text in your schema must match what's visibly displayed on the page. If your schema says 'ratingValue: 4.8, reviewCount: 143' but your page visually shows 72 reviews with an average of 4.6, Google's quality review process will flag the inconsistency. Always ensure your schema reflects the actual visible state of your reviews.
Mistake 3: Using the Wrong Schema Type for Your Content
Using Product schema for a service business, or SoftwareApplication schema for a physical product, can prevent your rich snippets from qualifying. Match your schema type precisely to your business category.
Mistake 4: Including Only One Review in the Schema
AggregateRating requires a minimum of one review in the schema to be valid, but Google's practical threshold for displaying rich snippets appears to be higher — typically at least 5–10 verified reviews. Include as many individual Review items as practical, and ensure your reviewCount accurately reflects your total review count.
Mistake 5: Missing Required Properties
AggregateRating requires at minimum: ratingValue and reviewCount (or ratingCount). Missing either of these makes the schema invalid. Review requires at minimum: author and reviewRating. Use Google's Rich Results Test tool (search.google.com/test/rich-results) to validate your implementation before relying on it.
Mistake 6: Hiding or Displaying Only Reviews Selectively
Google's guidelines require that the reviews marked up in your schema be representative of your overall review set — not just the positive ones. Selectively marking up only 5-star reviews while hiding negative feedback violates these guidelines.
Mistake 7: Not Updating Schema When Content Changes
If you remove testimonials from your page, update your average rating, or change your review count, your schema must be updated to match. Stale schema that no longer reflects your page content can trigger quality review processes. Gridapps avoids this problem by auto-updating schema whenever your testimonial library changes.
Using Google's Tools to Validate and Monitor Your Schema
After implementing schema markup, use Google's Rich Results Test (search.google.com/test/rich-results) to verify that your implementation is valid and eligible for rich snippets. Enter your page URL, and the tool will show you exactly which schema types it detects, which properties are present or missing, and whether the page is eligible for rich results.
In Google Search Console, navigate to the 'Enhancements' section to see which pages have valid review schema, how many impressions your rich snippets are generating, and whether there are any warnings or errors that need attention. Monitor this dashboard monthly to catch any schema validation issues before they impact your search performance.
