.svg)
review
review · Optional
Appears in
What is it?
review attaches one or more individual customer or editorial reviews directly to an Organization entity. Each review is a structured Review object containing the reviewer's name, rating, and written text. Where aggregateRating summarizes reputation as a single score, review provides the individual testimonials that make that reputation concrete.
Why this matters for AEO
AI answer engines draw on structured review data when constructing responses to queries like "what do customers say about [company]?" or "is [company] worth using?" A machine-readable Review object gives these systems reviewer attribution, a date, and a rating alongside the actual text, which is more reliable than scraping unstructured page content. When comparing vendors, AI systems weight structured reviews differently from marketing copy because they carry reviewer identity and a declared rating. Including one to three strong reviews in Organization schema increases the signal richness of your entity data without requiring a third-party integration.
What the specs say
Schema.org:review expects a Review object. A review of the item. The range of valid types includes Brand, CreativeWork, Event, Offer, Organization, Place, Product, and Service. [Source: https://schema.org/review]
Google: Not mentioned in Google's structured data documentation for Organization. Google does document reviews for Product, Recipe, and other types with rich result eligibility. For review snippet rich results on Organization, see the review snippet documentation. [Source: https://developers.google.com/search/docs/appearance/structured-data/review-snippet]
How to find your value
Use verified reviews you have the right to republish. Suitable sources include:
- Written testimonials collected directly from customers with their consent
- Published case studies where the customer approved public attribution
- G2, Capterra, or Trustpilot reviews where the reviewer's name is public and attribution is permitted under the platform's terms
Do not fabricate reviewers, manufacture ratings, or assign 5-star ratings to reviews that do not contain one. Google's review guidelines apply to all review markup, including on Organization.
Format and code
Each review is a Review object. Core properties: author (a Person object with name), reviewRating (a Rating object), reviewBody (the written text), and optionally datePublished.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Notion",
"url": "https://notion.so",
"review": {
"@type": "Review",
"author": {
"@type": "Person",
"name": "Sara Okonkwo"
},
"reviewRating": {
"@type": "Rating",
"ratingValue": "5",
"bestRating": "5"
},
"datePublished": "2024-11-14",
"reviewBody": "Notion replaced five separate tools for our team. The database views and linked pages made project tracking something people actually use instead of avoid."
}
}
To include multiple reviews, use an array:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Linear",
"url": "https://linear.app",
"review": [
{
"@type": "Review",
"author": {
"@type": "Person",
"name": "Marcus Hjelm"
},
"reviewRating": {
"@type": "Rating",
"ratingValue": "5",
"bestRating": "5"
},
"datePublished": "2024-09-03",
"reviewBody": "Issue tracking that feels instant. The keyboard-first design alone is worth switching from Jira."
},
{
"@type": "Review",
"author": {
"@type": "Person",
"name": "Priya Narayan"
},
"reviewRating": {
"@type": "Rating",
"ratingValue": "4",
"bestRating": "5"
},
"datePublished": "2024-10-18",
"reviewBody": "Cycles and roadmaps work well for small engineering teams. Would benefit from better reporting on cycle velocity."
}
]
}
Webflow implementation
Static pages
Add the JSON-LD block in Page Settings > Custom Code for your homepage or about page. Hardcode the review author, rating, and body text. Update when you collect new testimonials worth featuring.
CMS template pages
If your Webflow CMS stores testimonials in a collection, you can output a JSON-LD review array using embed elements with CMS field bindings. Each CMS item would contribute an author.name, ratingValue, datePublished, and reviewBody.
In Schema HQ
Support is available for review objects within your Organization schema through the org schema editor. You can enter structured review data without writing raw JSON. Schema HQ handles the correct nesting of Review, Rating, and Person objects.
Real examples
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Figma",
"url": "https://figma.com",
"review": {
"@type": "Review",
"author": {
"@type": "Person",
"name": "James Watkins"
},
"reviewRating": {
"@type": "Rating",
"ratingValue": "5",
"bestRating": "5"
},
"datePublished": "2025-01-08",
"reviewBody": "Replaced our entire design handoff workflow. Developers and designers work in the same file and that alone cut back-and-forth by half."
}
}
Related fields
FAQ
Does adding review to Organization generate rich result star ratings in Google Search?
Google's review snippet eligibility for Organization is not documented the same way it is for Product. Adding review to Organization schema improves entity data quality for AI systems and knowledge panels but does not guarantee visible star ratings in standard search results.
Can the review author be a person or organization?
author accepts both Person and Organization types. Use Person for individual customer reviews and Organization for editorial or institutional reviews from publications.
How many reviews should be included?
One to three reviews is practical for most implementations. More than five in a single JSON-LD block adds page weight without meaningful signal increase. If you have many reviews, pair a small review array with an aggregateRating that reflects the full dataset.
