Google Play Reviews Scraper

What this Actor does

Google Play Reviews Scraper collects review cards embedded in public Google Play app pages. Each dataset row contains a visible review and related app details from that page. The Actor does not access private review endpoints or return a complete review archive.

Google Play may load additional reviews only after opening its review dialog. Those reviews are not included unless they are present in the public page content the Actor can read. The page input is fixed at 1 because the public pages do not expose a stable review-page offset.

Input

Provide app package IDs, public Google Play app URLs, or search terms. You can submit multiple app IDs or searches. maxReviews limits the review cards read per app page, maxApps limits apps found per search, and maxItems limits total dataset rows.

{"appId":"com.spotify.music","maxReviews":25,"maxItems":100}

{"searchTerms":["navigation","podcasts"],"maxApps":8,"maxItems":100,"locale":"en-US"}

Input	Description	Default
appId / appIds	One or more Google Play package IDs.	—
startUrls	Public app, search, or category pages. sourceUrls and urls are aliases.	—
searchTerm / searchTerms	Search terms used to discover apps.	—
maxReviews	Maximum review cards read per app page (1–5,000).	50
maxApps	Maximum app pages followed per search page (1–100).	20
maxItems	Maximum review records across the run (1–5,000).	500
maxPages	Maximum public pages fetched across submitted and discovered sources (1–100).	20
deduplicate	Remove repeated review records.	true
locale / language / country	Choose the Google Play language and storefront.	en-US / en / US

page is fixed at 1: Google Play does not provide a stable public review-page offset. The Actor reads only review cards visible in the fetched page content.

Dataset output

Each row includes the app ID and review information such as reviewId when exposed, visible reviewer display label, rating, review title and text, date text, helpful count, app version, language, review images, and any public developer reply. App details from the same page can include title, developer, category, description, rating totals, downloads label, update notes, screenshots, and a compact Data safety summary.

Flat fields are available for tables, with nested app, review, reviewer, and developerReply objects for related values. Compatibility aliases such as title/appTitle and text/reviewText may also appear.

{
  "appId": "com.example.reviews",
  "appTitle": "Example App",
  "reviewId": "source-review-id",
  "reviewerDisplayName": "Asha",
  "reviewScore": 5,
  "reviewDateText": "September 1, 2026",
  "reviewDatePrecision": "day",
  "reviewTitle": "Easy to use",
  "reviewText": "Great app and fast navigation.",
  "reviewHelpfulCount": 12,
  "hasDeveloperReply": true,
  "replyText": "Thanks for sharing your feedback."
}

Only values available on the public page are included. Relative date labels are preserved as text; an exact date is provided only when the source gives one. A visible reviewer name is a display label, not a verified identity. Missing reply or app details are not inferred.

You can download dataset results in JSON, CSV, Excel, or other formats supported by Apify. The run page also shows a summary and health information.

Cost, coverage, and responsible use

Check the Actor's Pricing tab for current Actor and Apify platform charges. Search inputs first discover app pages, while app IDs and direct URLs target known apps. Start with small limits to see how many review cards are available for your chosen apps and market.

Results reflect public Google Play pages at run time and may vary by app, language, and country. Review bodies may contain personal information written by their authors. Use the data for a legitimate purpose, follow Google Play's terms and applicable privacy laws, and do not bypass access controls.