Google Play App Search & Reviews Scraper

The Google Play Reviews Scraper searches Google Play for apps by keyword, or takes package IDs and store URLs directly, and extracts their reviews — star rating, review text, author, thumbs-up count, review date, the app version the review was written against, and the developer's reply.

What you get

One dataset row per review. Keyword runs also write one row per matched app, carrying its title, developer, rating, installs, price and category.

{
  "review_id": "8f0a3b7c-2d41-4c6e-9e2b-7a1c9d3f5b20",
  "app_id": "com.spotify.music",
  "author_name": "Jordan P.",
  "rating": 2,
  "text": "Shuffle stopped respecting my queue after the last update. Was perfect before.",
  "thumbs_up_count": 412,
  "review_date": "2026-05-28T14:02:11Z",
  "app_version": "9.0.34.610",
  "dev_reply_text": "Thanks for flagging this — please send us the details via the in-app form.",
  "dev_reply_date": "2026-05-29T08:11:00Z",
  "scraped_at": "2026-06-01T10:15:03+00:00"
}

app_version is the field most of this data is bought for: it ties a spike in one-star reviews to the release that caused it.

What it costs

Event	Free	Bronze	Silver	Gold+
Actor Start (apify-actor-start)	$0.001	$0.001	$0.001	$0.001
App (app-search-result)	$0.0025	$0.00233	$0.00217	$0.002
App review (review)	$0.00055	$0.00053	$0.00052	$0.0005

You pay per review received — $0.55 per 1,000 on the Free tier, $0.50 per 1,000 on Gold — plus $0.001 to start the run. A keyword search also charges for each app it resolves, which is what max_apps_per_search caps; naming package IDs in App IDs or URLs skips that charge entirely. An app with fewer reviews than you asked for is billed for what it actually returned. The residential proxy is included in the price of the run.

Input

Field	Type	Required	Default	What it does
app_ids	array	no	—	Apps to take reviews from, one per entry, as a package ID such as com.spotify.music or a full Play Store URL such as https://play.google.com/store/apps/details?id=com.spotify.music. Give at least one of app_ids or search_queries; leave empty when you are supplying search_queries instead.
search_queries	array	no	—	Keywords to search Google Play with, one per entry, for example meditation app. Every matching app is written to the dataset as its own row and then has its reviews taken. Give at least one of app_ids or search_queries; leave empty when you already know the package IDs and are listing them in app_ids.
max_apps_per_search	integer	no	10	How many apps to keep from each keyword search, from 1 to 250. Default 10. Every app kept is charged and then has its reviews taken, so this is the setting that decides what a keyword run costs.
max_reviews_per_app	integer	no	200	How many reviews to take from each app, from 1 to 50000. Default 200. An app with fewer reviews than this returns what it has, and you pay only for the reviews you receive.
sort	string	no	"most_relevant"	Which reviews you get first: most_relevant for the ones Google surfaces, newest for the most recent, rating to walk the stars. Default most_relevant. Use newest together with date_from to pull a fixed window.
rating_filter	array	no	—	Keep only reviews with these star ratings; pick any of 1, 2, 3, 4 and 5. Leave empty to keep every rating. Selecting 1 and 2 is the quick way to read only the complaints.
date_from	string	no	—	Keep only reviews written on or after this date, as YYYY-MM-DD. Leave empty for no lower bound. Works best with sort set to newest, which walks reviews in date order.
date_to	string	no	—	Keep only reviews written on or before this date, as YYYY-MM-DD. Leave empty for no upper bound.
country	string	no	"us"	Play Store country code, which decides which apps and which reviews are visible at all. Default us. Use the market you care about, for example gb, de or vn.
language	string	no	"en"	Play Store language code for app titles, descriptions and the review text Google returns. Default en.
proxyUrls	array	no	—	Leave empty and the run uses a residential proxy that is included in the price of the run. To route through your own account instead, add one gateway URL per entry, for example http://user:pass@host:port. Works with DataImpulse, Bright Data, Oxylabs, Smartproxy or any provider that issues URLs. When you set this, only these URLs are used.

Give at least one app, as a package ID or URL in App IDs or URLs or as a keyword in Search Queries.

How to run it

1. Open the actor on Apify Console and click Try for free.
2. Paste package IDs or Play Store URLs into App IDs or URLs, or type keywords into Search Queries and let the run find the apps.
3. Run it. Reviews stream into the dataset while the run is still going; export them as JSON, CSV or Excel, or read them from the Apify API.

{
  "app_ids": ["com.spotify.music", "com.netflix.mediaclient"],
  "max_reviews_per_app": 500,
  "sort": "newest",
  "rating_filter": ["1", "2"],
  "date_from": "2026-01-01",
  "country": "us",
  "language": "en"
}

Minimal input:

{
  "app_ids": ["com.spotify.music"]
}

Available as the MCP tool herus13--google-play-reviews-scraper on mcp.apify.com and through the Apify API; send the same JSON.

Why this scraper

• Search and reviews in one run. Give it a keyword and it finds the apps that rank for that term, then pulls their reviews, so competitor work does not need two actors and a join.
• Version-tagged feedback. Each review carries the app version it was written against, which turns a pile of complaints into a per-release quality signal.
• Developer replies included. Both the reply text and its date come back, so reply rate and reply latency are measurable, not guesses.
• Filters that cut the bill. Star rating, date window and a per-app cap all apply before you are charged, so a "one and two stars since January" run costs what it sounds like it should.
• Any market. Country and language codes select the Play Store you actually want; app availability and review language both follow.

Use cases

• App feedback mining — rating, text, thumbs-up count and the app version in one row. The version field is what lets a spike in complaints be traced to the release that caused it.
• Developer-response auditing — replies come back with the reviews, so you can measure what share of negative feedback was answered and how that rate moves over time.
• Competitor research — a keyword search shows which apps rank for a term, and their reviews show what those users are unhappy about, which is usually a more honest roadmap than the published one.
• Release-quality tracking — thumbs-up counts separate one frustrated user from a widespread regression that hundreds of people endorsed.
• ASO and store research — matched-app rows carry title, developer, installs, price and category, which is a ready-made competitive set for a keyword.

FAQ

Do I need a proxy? A residential proxy is included in the price of the run. To use your own, paste gateway URLs into Your own proxy URLs. Scraping at volume? Your own DataImpulse account is cheaper per GB.

What do I put in App IDs or URLs? Either the package ID, such as com.spotify.music, or the full Play Store link for the app. Both work, one per line, and you can mix them.

Why do I get fewer reviews than I asked for? max_reviews_per_app is a ceiling, not a quota. An app with 80 reviews returns 80 however high you set it, and you are charged for 80. Rating and date filters trim further.

How do I read only the complaints? Set Rating Filter to 1 and 2, and sort by newest. Add Reviews From Date to hold the window to a single release.

Do reviews come back in English? They come back in the language they were written in, in the Play Store you selected. Set Country and Language to the market you want to read.

Is this legal? The actor collects publicly available app and review data only. You remain responsible for complying with Google's terms and with the law that applies to you, including handling personal data such as reviewer names on a lawful basis.

Related actors

• Google Play Review Monitor — the scheduled sibling: run it on a cron and it returns only reviews that are new since last time.
• Apple App Store Scraper — the same job on iOS, for cross-platform reputation tracking.
• Google Maps Reviews Scraper — place reviews with photos, owner replies and reviewer details.
• Google Trends Scraper — search demand for the app category you are researching.