UserReview

UserReview is a direct Review subtype for reviews written by end users: consumers, purchasers, attendees. Use positiveNotes and negativeNotes (inherited) for pros/cons lists.

The UserReview vs CriticReview distinction is signal-only (neither adds properties), but AI consumers weight them differently.

Full example of schema.org/UserReview json-ld markup

The markup is verified as valid with Rich Results Test from Google.

schema.org/UserReview

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "UserReview",
  "itemReviewed": { "@type": "Product", "name": "XooTee Classic" },
  "author": { "@type": "Person", "name": "Nora Lindgren" },
  "datePublished": "2026-03-20",
  "reviewBody": "Soft, well-fitting tee that has held up through 40+ washes. The print stays crisp.",
  "reviewRating": { "@type": "Rating", "ratingValue": 5, "bestRating": 5 },
  "positiveNotes": ["Soft fabric", "Durable print", "Roomy fit"],
  "negativeNotes": ["Sleeves run a little long"]
}
</script>

Minimal valid version

The smallest markup that still produces a valid UserReview entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/UserReview (minimal)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "UserReview",
  "itemReviewed": { "@type": "Product", "name": "XooTee Classic" },
  "author": { "@type": "Person", "name": "Nora Lindgren" },
  "reviewRating": { "@type": "Rating", "ratingValue": 5, "bestRating": 5 }
}
</script>

Google rich results this unlocks

UserReview is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). UserReview becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common UserReview mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

01
UserReview for a staff or critic review
Wrong
```
UserReview for an in-house editor's review
```
Right
```
CriticReview for editorial/professional; UserReview for consumers
```
Audience and authority differ; pick the signal that matches the reviewer type.

Schema properties in this example

UserReview Review CreativeWork itemReviewed Product author Person datePublished reviewBody reviewRating Rating ratingValue bestRating positiveNotes negativeNotes CriticReview

Also mentioned in 1 other example

UserReview also appears in CriticReview. See the full UserReview schema page for every reference.

About the example data

A fictional end-user review of the XooTee Classic product.

Comments

Loading comments...