Skip to main content

Review statistics/analytics API

Judging by the abuse concerns raised here, a native business listing/profile page feature within the EMR platform probably isn't on the roadmap, and I support this decision. I've put together a simplified description below of how white-label partners could achieve this on their own agency or client websites using a CMS, but it depends on one missing piece.

Even if we embed the widgets manually, the structured data they provide is limited to total review count and average rating. That's not enough. The real value of a dedicated business review profile page, especially in the current AI search landscape, lies in the detailed statistics.

When Google AI Overviews, ChatGPT, or Perplexity answer a query like "is business good?", they look for specific, verifiable, crawlable data on a real web page. An iframe widget is invisible to these systems. The data inside it simply doesn't exist as far as AI crawlers are concerned. A properly built profile page with rich review statistics rendered as native HTML and structured JSON-LD schema is what actually gets cited. And it's only possible if the underlying data is accessible via API.

With a dedicated analytics endpoint, white-label partners could build CMS-driven profile pages that populate and update automatically. No manual maintenance, always fresh, always crawlable.

If it isn't too large a job, I'd like to kindly request a new read-only endpoint in the official documented API that exposes the review statistics already available in the dashboard.

Suggested parameters:

  • Time period (All Time, Last 7 / 30 / 90 Days, This Month, Last Month, This Year, Custom range)

  • Single location or multi-location rollup

  • Review source filter (default: all sources)

Minimum data points needed:

  • Total review count

  • Review count per source

  • Rating distribution (count per star level, 1 to 5)

  • Review velocity (new reviews within the selected time period)

  • Timestamp of the most recent review

Anything beyond that is a bonus.

Thanks in advance!

1 comment

Log in to comment and vote

Comments1

  • Severi

    •

    Apr 22

    @mannie@embedmyreviews.com this got pretty much resolved by the MCP release, but are you able to expose the actual metrics API endpoint (and other non-released endpoints) used by the MCP server, so we could also call them directly?

    Sure we can already do this with a JSON-RPC payload over a direct HTTP POST, but would be leaner to have the actual endpoints (+ documentation at some point) available.

    Thanks! The MCP was a really awesome release!