Scrape Google reviews - or stop maintaining a scraper

Same data, delivered as an API. No selectors to fix, no proxies to rotate, no blocks at 3am.

Most people searching for a Google reviews scraper want the reviews, not the scraping. Repuso does the collection and hands you normalized JSON, with a webhook when something changes.

Get an API key See the Google reviews API

Why a scraper stops being worth it

It breaks. Google changes its markup and your parser returns nothing - usually silently, usually noticed days later.
Proxies and rate limits. Blocks, retries and IP rotation become a permanent maintenance cost.
No change detection. A scraper gives you a snapshot; you still have to diff it to know a review arrived.
One site at a time. Every extra platform is another scraper, another schema, another thing to fix.

What you get instead

One normalized schema across Google, Tripadvisor, Trustpilot and 50+ platforms.
Full history on first sync, then incremental updates.
Signed webhooks on new reviews and rating changes.
Rating history and per-review sentiment.
An MCP server, so ChatGPT, Claude and Cursor can query your reviews directly.

Compared with scraping APIs

Tools like Outscraper, SerpApi, Apify and DataForSEO sell requests: you ask, they scrape, you get raw results and keep the state yourself. Repuso monitors a profile continuously - it keeps the history, notices changes, and pushes them to you. If you need a one-off export, a scraping API is fine. If you need reviews to stay current inside your product, the difference shows up quickly.

Side-by-side: Repuso vs the scraping APIs.

Exporting your own reviews

If you just want your reviews out of Google once, add the profile, wait for the first sync and call /reviews/get. That is the whole export.

curl -u :$REPUSO_KEY "https://api.repuso.com/public/v1/reviews/get?profile_id=49812&limit=500"

← Repuso for developers