Individual Review schema is present for displayed reviews

Individual Review schema.org blocks make each shopper review eligible for its own rich result — author name, star rating, and date displayed inline in SERPs alongside the product. Without them, your reviews exist only in HTML that search crawlers cannot interpret as structured endorsements. The schema.org Review.reviewRating mapping requires ratingValue as a number and author as a Person object with a name field — omitting either means Google's parser rejects the block silently. Stores with per-review schema see measurably higher long-tail SERP presence because individual reviews can surface as standalone snippets for "[product] review" queries.

Add a Review JSON-LD block to components/ReviewItem.tsx populated from the review database record.

// components/ReviewItem.tsx
export function ReviewItem({ review }: { review: Review }) {
  const schema = {
    '@context': 'https://schema.org',
    '@type': 'Review',
    author: { '@type': 'Person', name: review.author_name ?? 'Anonymous' },
    reviewRating: {
      '@type': 'Rating',
      ratingValue: review.rating, // number, not string
      bestRating: 5,
      worstRating: 1
    },
    reviewBody: review.text,
    datePublished: review.created_at.toISOString()
  }

  return (
    <>
      <script
        type="application/ld+json"
        dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
      />
      <article className="review">
        <strong>{review.author_name ?? 'Anonymous'}</strong>
        <StarDisplay rating={review.rating} />
        <time dateTime={review.created_at.toISOString()}>{formatDate(review.created_at)}</time>
        <p>{review.text}</p>
      </article>
    </>
  )
}

Validate the output with Google's Rich Results Test after deploying — the ratingValue type mismatch (string vs number) is the most common silent failure.