Social proof elements (purchase count, trending badge) are factually accurate

Hardcoded social proof numbers — "Purchased 500+ times", "Best Seller", "4.8 stars" — violate the FTC Endorsement Guides on social proof and, when displayed in schema.org markup, cause Google to flag rich results as inaccurate. A product page that shows "Purchased 500+ times" backed by a literal JSX string rather than a database count misrepresents sales volume, which is deceptive advertising under FTC guidelines. The failure compounds as your catalog grows: the hardcoded number never updates, so the gap between claimed and actual performance widens automatically.

Move all social proof calculations to database aggregation queries in components/SocialProof.tsx — no numeric literals in JSX.

// components/SocialProof.tsx
export async function SocialProof({ productId }: { productId: string }) {
  const [purchaseCount, helpfulCount] = await Promise.all([
    db.orders.count({ where: { product_id: productId, status: 'completed' } }),
    db.reviewVotes.count({ where: { product_id: productId, vote: 'helpful' } })
  ])

  // Only render elements when count > 0 to avoid showing "0 people purchased this"
  return (
    <div className="social-proof">
      {purchaseCount > 0 && <p>{purchaseCount.toLocaleString()} verified purchases</p>}
      {helpfulCount > 0 && <p>{helpfulCount} people found these reviews helpful</p>}
    </div>
  )
}

Search for numeric literals adjacent to words like "purchased", "sold", "reviews", or "trending" in JSX/HTML files and replace each with a live query.