Google Play Reviews Scraper avatar

Google Play Reviews Scraper

Pricing

from $0.15 / 1,000 review results

Go to Apify Store
Google Play Reviews Scraper

Google Play Reviews Scraper

Scrape Google Play reviews by app URL, package ID, or search query. Extract review text, ratings, dates, app versions, developer replies, helpful votes, reviewer data, app metadata, countries, and review languages.

Pricing

from $0.15 / 1,000 review results

Rating

0.0

(0)

Developer

Kelopr

Kelopr

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

2 days ago

Last modified

Share

Extract app discovery and review intelligence with language, rating, version, date, and developer-reply filters.

Request-based Google Play reviews scraper. Extract review text, ratings, dates, app versions, developer replies, helpful votes, reviewer data, app details, and search-based app discovery.

All examples below use fictional DEMO-* identifiers, reserved .test domains, and masked contact details. They do not represent real people, listings, products, or companies.

๐Ÿš€ What this Actor does

  • Flexible collection: Direct apps, App discovery, Review intelligence, Output selection.
  • Structured output: clean JSON records organized into reviews, apps views.
  • Production-ready: concurrency, retries, proxy support, limits, and source-aware diagnostics are exposed through the Actor input.
  • Easy automation: run from the Apify Console, API, schedules, webhooks, Make, Zapier, or any HTTP client.

๐ŸŽ›๏ธ Modes and workflows

Mode or workflowWhat it does
Direct appsResolve exact package IDs or Google Play URLs.
App discoverySearch Google Play by keyword, country, and language.
Review intelligenceFilter reviews by rating, version, keyword, date, language, or developer reply.
Output selectionReturn reviews, apps, or both with outputMode.

๐Ÿ’ก Common use cases

  • App-review monitoring
  • Release and version quality analysis
  • Competitor and market discovery

๐Ÿ“ฅ Input schema

Configure the Actor in the Input tab or send the same JSON through the API. Fields not needed for your workflow can be omitted.

FieldTypeDescriptionDefault
appIdsOrUrlsarray<string>Use this for exact targets. Examples: com.supercell.brawlstars or https://play.google.com/store/apps/details?id=com.spotify.music.[]
searchQueriesarray<string>Use this when you know the app name or niche, but not the package ID. Examples: Brawl Stars, fitness app, habit tracker.[]
maxAppsPerSearchintegerHow many apps to take from each search query before scraping reviews.5
countriesarray<string>Google Play country codes. Examples: us, gb, de, fr, br, jp.["us"]
reviewLanguagesarray<string>Select one or many review text languages in the same run. The Actor checks the detected language of each review before saving it.["en"]
customReviewLanguagesarray<string>Optional. Add extra Google Play language codes that are not in the dropdown. Examples: is, ga, eu, gl, iw.[]
strictReviewLanguagebooleanDetect the language of every review text and skip reviews written in other languages. Recommended for clean datasets.true
languagesarray<string>Deprecated. Use Review languages instead. This field is kept only for old tasks and API clients.[]
maxReviewsPerAppintegerMaximum matching reviews to save for each app/country/review-language combination. Set 0 to collect app details only.100
sortstringOrder used by Google Play before rating, text, date, reply, and language filters are applied. Allowed: newest, relevant, rating.newest
ratingsarray<string>Return only selected star ratings. Leave empty to collect all ratings.[]
keywordsarray<string>Return only reviews containing at least one of these words or phrases. Case-insensitive.[]
excludeKeywordsarray<string>Skip reviews containing any of these words or phrases. Case-insensitive.[]
dateFromstringReturn reviews published on or after this date. Format: YYYY-MM-DD.``
dateTostringReturn reviews published on or before this date. Format: YYYY-MM-DD.``
recentDaysintegerReturn only reviews from the last N days. Set 0 to disable.0
onlyWithDeveloperReplybooleanReturn only reviews that have a developer reply.false
onlyWithoutDeveloperReplybooleanReturn only reviews that do not have a developer reply.false
appVersionsarray<string>Return only reviews created for selected app versions. Exact match.[]
outputModestringReviews only is best for sentiment analysis. Apps only is useful for discovery. Apps and reviews is best for QA. Allowed: reviews, apps, both.reviews
includeAppDetailsbooleanFetch app metadata such as title, icon, developer, score, installs, genre, version, screenshots, and Google Play URL.true
dedupebooleanSkip duplicate reviews across repeated apps, countries, and review languages.true
fetchPageSizeintegerHow many reviews to request from Google Play per page before local filters are applied.200
maxPagesPerAppintegerSafety limit for pagination. Increase if strict filters need more pages to find enough matching reviews.25
maxConcurrencyintegerHow many app/country/review-language combinations can run in parallel.5
requestDelayMsintegerOptional delay in milliseconds after each review page request.0

โ–ถ๏ธ Example input

{
"searchQueries": [
"habit tracker"
],
"countries": [
"US"
],
"reviewLanguages": [
"en"
],
"maxAppsPerSearch": 5,
"maxReviewsPerApp": 50,
"outputMode": "both"
}

๐Ÿ“ฆ Output schema

Each successful item is written to the default dataset. Select a dataset view in the Apify Console or export the full dataset as JSON, CSV, Excel, XML, or RSS.

reviews โ€” Reviews

One record or grouped payload for reviews, depending on the source schema.

Fields: appIcon, appTitle, rating, text, publishedAt, appVersion, thumbsUpCount, developerReplyText, developerReplyDate, reviewerName, reviewerImage, appId, country, language, detectedLanguage, appUrl

apps โ€” Apps

Structured apps records for this Actor.

Fields: appIcon, appTitle, developer, genre, score, ratingsCount, reviewsCount, installs, version, appId, country, language, appUrl

๐Ÿ“ค Example output

{
"appTitle": "Demo Habit Tracker",
"rating": 5,
"text": "Simple example review for documentation.",
"publishedAt": "2026-08-01T10:00:00Z",
"appVersion": "2.4.0",
"thumbsUpCount": 12,
"reviewerName": "Demo User",
"appId": "test.example.habits",
"country": "US",
"language": "en"
}

Missing source values are returned as null, empty arrays, or documented availability/status fields; the Actor does not invent unavailable source data.

๐Ÿ”Œ API example

Replace the placeholder with an Apify token and send the same input used in the Console:

curl -X POST "https://api.apify.com/v2/acts/trakk~google-play-reviews-app-intelligence/runs?token=<YOUR_APIFY_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"searchQueries": ["habit tracker"], "countries": ["US"], "reviewLanguages": ["en"], "maxAppsPerSearch": 5, "maxReviewsPerApp": 50, "outputMode": "both"}'

For synchronous integrations, use the run-sync-get-dataset-items API endpoint. For larger jobs, start an asynchronous run and consume its default dataset when the run succeeds.

๐Ÿงฉ Automation and exports

  • Schedule recurring runs from the Apify Console.
  • Trigger downstream systems with webhooks when a run succeeds or fails.
  • Reuse named monitoring keys or stores where the selected workflow supports change tracking.
  • Export dataset views to JSON, CSV, Excel, XML, or RSS, or access items through the Apify API.

โ“ FAQ

Do I need a login or browser session?

Use only the inputs shown in the Actor schema. If authentication or cookies are supported, the relevant encrypted field is explicitly available in the Input tab; otherwise no account is required.

Why can some fields be empty?

Source pages vary by region, content type, privacy settings, and availability. Optional enrichment also depends on the selected mode. Empty values are preserved honestly instead of being guessed.

How should I run this at scale?

Start with a small representative input, inspect the dataset and cost, then raise item limits and concurrency gradually. Use Apify Proxy when the schema exposes it, and use schedules plus monitoring keys for recurring collection.

Is the example data real?

No. Every example in this README is intentionally fictional and uses demo identifiers, reserved domains, or masked contact values.