Google Play Store Scraper - Apps & Reviews

What does Google Play Store Scraper do?

This Actor extracts app metadata and unlimited user reviews from the Google Play Store. Give it package names, or just a search keyword — it will find the apps for you, then pull full app details, ratings, install counts, and every review you ask for.

Google's own page caps a review request at roughly 150. This Actor pages through automatically, so asking for 5,000 reviews on an app simply returns 5,000 reviews.

Results export as JSON, CSV, Excel or HTML, and are available through the Apify API.

Why use this scraper?

• Monitor your own app — catch a rating drop or a spike in one-star reviews the day it happens, not at the end of the month.
• Competitor intelligence — track rival apps' ratings, install milestones, release cadence and what users complain about.
• ASO and market research — search a keyword and pull the whole competitive set with ratings, pricing and install counts in one run.
• Feature and bug mining — thousands of reviews are the cheapest product research you will ever run. Pipe them into an LLM and cluster the complaints.
• Sentiment tracking — correlate review sentiment against your release versions using the version field on every review.

How to use it

1. Either paste app package names (com.spotify.music) or full Play Store URLs, or type a search query to discover apps by keyword.
2. Choose What to scrape: reviews, app details, or both.
3. Set Max reviews per app — it pages automatically, so go as high as you need.
4. Set Country and Language to match the store you care about.
5. Click Start, then export from the Storage tab.

Finding a package name

It's the id parameter in any Play Store URL:

https://play.google.com/store/apps/details?id=com.spotify.music
                                              ^^^^^^^^^^^^^^^^^^

You can paste the whole URL — the Actor extracts it for you.

Input

Field	Type	Description
appIds	array	Package names or Play Store URLs.
searchQuery	string	Discover apps by keyword instead of naming them.
searchLimit	integer	How many apps to take from the search. Default 10.
mode	select	reviews, apps, or both. Default reviews.
maxReviews	integer	Reviews per app. Pages past 150 automatically. Default 200.
reviewSort	select	newest, rating, or helpfulness.
country / language	string	Two-letter store codes. Default us / en.

{
    "searchQuery": "meditation",
    "searchLimit": 5,
    "mode": "both",
    "maxReviews": 500,
    "reviewSort": "newest",
    "country": "us",
    "language": "en"
}

Output

Every row carries a type field so app rows and review rows are easy to split.

Review row:

{
    "type": "review",
    "appId": "com.spotify.music",
    "appTitle": "Spotify: Music and Podcasts",
    "reviewId": "da61d7a3-6fde-4ae8-a4eb-28fe3286dd81",
    "userName": "Kiran Kumari",
    "score": 5,
    "text": "Amazing awesome fantastic",
    "thumbsUp": 0,
    "version": "9.1.64.1676",
    "date": "2026-08-24T04:41:09.954Z",
    "replyText": null,
    "url": "https://play.google.com/store/apps/details?id=com.spotify.music"
}

App row includes title, developer and contact details, score, ratings, the full star histogram, installs, pricing and IAP range, containsAds, genre, content rating, released / updated / version, required Android version, icon and header images, and the privacy policy URL.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Key data fields

Field	Description
type	app or review — filter on this to split the dataset.
appId / appTitle	Package name and display title, present on every row.
score	Star rating. On app rows this is the average; on review rows, that user's rating.
histogram	Count of 1–5 star ratings. App rows only.
installs / minInstalls	Install count as displayed, and as a number.
version	On review rows, the app version the user was running — ideal for regression spotting.
replyText / replyDate	The developer's public response, when there is one.
thumbsUp	How many users found that review helpful.

How much does it cost?

Billed per row returned, so cost tracks exactly what you get. An app row and a review row cost the same. Set Max reviews per app to keep any run inside a firm ceiling.

Scraping app details only (mode: apps) is extremely cheap — one row per app.

Tips

• version on reviews is the killer field. Group one-star reviews by app version and you'll see exactly which release broke something.
• Use histogram on the app row to see rating distribution rather than just the average — a 4.3 made of 5s and 1s is a very different app from a steady 4.3.
• Sort by newest and schedule a daily run to build your own review-monitoring pipeline.
• reviewId is stable — use it as the unique key when de-duplicating across scheduled runs.
• Reviews are localized. To see reviews from a specific market, set country and language together.

FAQ, disclaimers, and support

How many reviews can I actually get? As many as Google will page through. A single request caps near 150; this Actor keeps paging until it hits your maxReviews or Google stops returning a pagination token. Very old reviews on huge apps may not all be reachable.

An app returned fewer reviews than I asked for. That app doesn't have that many reviews in the country and language you selected. Smaller apps commonly have only a few dozen.

One of my apps failed. Check the FAILED_APPS record in the run's key-value store — it lists each failure with the reason. The run continues past failures rather than aborting.

Is this legal? The Actor reads only publicly visible Play Store listings and reviews. You are responsible for complying with Google's Terms of Service and applicable data protection law — review text is user-generated content and may contain personal data.

Need another store or a custom field? Open an issue on the Issues tab.