Google Play App & Review Scraper
Pricing
Pay per usage
Google Play App & Review Scraper
Search Google Play by keyword, then collect the 1-3 star reviews of the matching apps: reviewer, rating, full review text and app id. Works without a proxy. Verified on the Apify platform on 2026-08-21.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
the anh nguyen
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Share
Search Google Play by keyword and collect the matching apps and their reviews.
⚠️ Requires a residential proxy
This target blocks datacenter traffic. Without Apify Proxy on a residential group the scraper reaches the site, is served a challenge page, and returns zero rows while exiting successfully — so check the row count, not the run status.
Residential proxy is not available on the Apify free plan. On a paid plan, enable Apify Proxy for the run and it will work as documented.
This is a requirement, not a defect: the code requests a residential proxy and logs a warning naming the cause when it cannot get one.
Input
| Field | Default | What it does |
|---|---|---|
searchTerms | a sample list | Keywords to search the Play Store with |
maxApps | see schema | Apps to take per keyword |
maxReviews | see schema | Reviews to pull per app |
Output
Every row follows the shared Pulse signal shape:
| Field | Type | Notes |
|---|---|---|
source | string | which scraper produced the row |
title | string | headline for the item |
text | string | body text |
url | string | link to the item |
author | string | public display name where the source has one |
date | string | ISO 8601 |
score | integer | source-native score (rating, votes, stars) |
scrapedAt | string | ISO 8601 timestamp of capture |
Source-specific fields are added alongside these; see the dataset schema on the run for the exact set.
Notes
Part of the Pulse scraper family. Rows share one schema across sources, so results from several Pulse Actors can be concatenated without reshaping.
No credentials are required. Author fields are public display names as published by the source; no e-mail addresses or private profile data are collected.
