aggregateRating in structured data matches visible on-page values

A JSON-LD aggregateRating block that shows 4.5 stars while the page displays 4.3 stars is an active schema-org policy violation — Google's Rich Results guidelines prohibit structured data that misrepresents visible content. Discovery of the discrepancy triggers manual review and can result in a site-wide rich-result penalty. Beyond compliance, rating mismatch is a data-integrity failure: users who click a listing based on an inflated SERP star count and see a lower on-page rating experience an immediate trust collapse. The ratingValue and reviewCount in schema-org AggregateRating must be computed from the same database query that drives the visible UI.

Derive the JSON-LD aggregateRating from the same source as the rendered rating — never hardcode or cache independently. Compute both from a single database read per listing.

// In your listing data fetcher
const listing = await db.listing.findUnique({
  where: { id },
  select: {
    name: true,
    averageRating: true,
    reviewCount: true,
    // ...
  },
});

const jsonLd = {
  "@type": "LocalBusiness",
  ...(listing.reviewCount > 0 && {
    "aggregateRating": {
      "@type": "AggregateRating",
      "ratingValue": listing.averageRating,
      "reviewCount": listing.reviewCount,
    },
  }),
};

The guard listing.reviewCount > 0 prevents an empty aggregateRating block, which is separately flagged as invalid by Google's structured data validator.