Your Yelp, Google, and manual reviews — one feed, one render

A new customer about to buy from you reads reviews. They don't filter by platform. They scroll one wall of "people like me said this worked."

Most sites render one platform — usually whichever feed the org's marketing person remembered to wire up. Yelp on one site, Google on another, nothing on a third. None of them aggregate, because the integrations are a per-platform pain.

Business Dash pulls Yelp Fusion daily, syncs Google Business Profile reviews into the same table, and accepts manual entries via the dashboard. Read it through one SDK endpoint; render one component; trust one source of truth.

A daily cron at /api/cron/refresh-yelp-reviews pulls every org's latest snapshot — Yelp Fusion's free tier returns up to 3 reviews per call, so the cache builds up over time as new reviews land at the top.

The Google Business Profile integration uses the existing OAuth connection (the one your team set up in Settings → Integrations) and pages through every review on every refresh. Manual entries via the dashboard's "Add review" form sit in the same table with the same shape.

Dedup is by (orgId, source, externalReviewId). The same review never appears twice. New reviews insert; previously-seen rows refresh their lastSeenAt so you can detect "this review came back online" if a platform's API hiccups.

One endpoint: GET /api/package/v1/sites/{siteId}/reviews?limit=12. Returns an array of { rating, text, reviewerName, reviewerImageUrl, source, reviewUrl, timeCreated, verified } — everything a reviews wall component needs.

Pair with the SDK's typed client, render with your design system, decide whether each item links back to the platform or stays inline. The wall is a component you own; the data path is something we keep working.