Google Play Store Reviews Scraper

Try for free

A robust, high-performance utility designed for developer automation, data integration, and AI training. Features built-in captcha bypass, headful/headless browser execution, and proxy support to scrape Playstore Reviews data seamlessly, reliably, and at scale.

Pricing

from $4.99 / 1,000 results

Rating

0.0

(0)

Developer

Coding Frontned

Actor stats

Bookmarked

Total users

Monthly active users

9 days ago

Last modified

Input and behavior

appIds accepts 1–10 unique package names or exact Play app-detail URLs. Other hosts and Play paths are rejected.
maxReviews is a bounded per-app cap from 1 to 500.
sortBy accepts newest, rating, or helpfulness as supported by the public review client.
language is a lowercase two- or three-letter language code; country is a two-letter storefront country code.
maxRetries permits one to three bounded attempts per public metadata or review request.

The Actor processes apps sequentially and paginates only until the requested cap. It deduplicates app inputs and stable review identities. App metadata is best effort, but review rating and date are required. A source or no-data failure exits nonzero. If an earlier app completed before a later app failed, those rows remain available and OUTPUT_SUMMARY reports FAILED_PARTIAL rather than claiming complete success.

Output

Each real review has a stable recordId, canonical package and app URL, public app metadata when available, review ID/author/image, integer rating, review title/body/date, helpful count including zero, developer reply/date, app version, requested locale/sort, exact source provenance, availability flags, and extraction timestamp. Optional facts are omitted when the source does not publish them.

This Actor uses the open-source google-play-scraper client to read Google Play's publicly available app and review responses. It does not log in, use private accounts, solve access challenges, or fabricate reviews. Google can change response formats, ordering behavior, availability, and storefront results.

Every run writes OUTPUT_SUMMARY to the default key-value store with item/app counts, invalid-row count, data availability, duration, status, and a sanitized failure message when applicable.

Local verification

Run npm test, apify validate-schema, apify run --purge --input-file qa-inputs/local-validation.json, and npm run validate. The validator also accepts retrieved cloud JSON using node validate-datasets.js -.