DEV Community

Cover image for How to Scrape Google Play Reviews to CSV
veenkes
veenkes

Posted on

How to Scrape Google Play Reviews to CSV

How to Scrape Google Play Reviews to CSV

If you ship an Android app, Play Store reviews are one of the few places users tell you — in their own words — why they stay, churn, or leave one star. The official Play Console is fine for your own app, but it will not give you a clean CSV of a competitor's reviews, and it is awkward to pipe into a spreadsheet or a sentiment model. This guide shows how to scrape Google Play reviews to CSV (or JSON) in a few minutes, then how to do the same from Python.

You will use the Google Play Reviews Scraper on Apify. It accepts app IDs or Play Store URLs, can filter by star rating, language, country and date, and writes one flat row per review: rating, text, date, thumbs-up count, app version and the developer's reply.

By the end of this article you will have a CSV or JSON file on your machine, and a short Python snippet you can rerun or schedule. The same Actor is also callable from JavaScript and from AI agents through the Apify MCP server.

What you need

  • An Apify account. The Free plan is enough to try a small run.
  • A list of inputs for the Actor (URLs, IDs or search terms — details in the steps below).
  • Optional: Python 3 with the apify-client package if you want to automate the run.

You do not need a Google account, a browser automation script, or a Play Developer API key. The Actor reads the public review pages of the Play Store.

How to run it in the Apify Console

Step 1: Open the Actor

Go to https://apify.com/veenkes/veenkes-google-play-reviews and click Try for free. If you do not have an Apify account, create one; the Free plan includes monthly usage credit you can spend on this run.

Step 2: Add the apps

In the input form, paste a package name such as com.spotify.music or a full Play Store URL. You can add several apps in one run.

Step 3: Set a review cap and filters

Set Maximum reviews per app to something small first — 50 or 100 is enough to check the output. Optionally filter to 1–2 star reviews, pick a language (en, de, es, …), a store country, or a since date if you only want new reviews.

Step 4: Run and export CSV

Click Start, wait for the run to finish, then open the dataset and choose Export > CSV. You can also export JSON, Excel or XML. Each row is one review, ready for a spreadsheet or a pandas DataFrame.

Useful filters: Only reviews with text drops star-only reviews; Reviews since plus Newest sort is a good daily incremental job; reviewer names are off by default if you want to stay conservative on personal data.

How to run it from Python

Install the official client and call the Actor by its Store id veenkes/veenkes-google-play-reviews. Replace YOUR_APIFY_TOKEN with a token from Apify Console > Integrations. Do not commit the token to a public repository.

pip install apify-client
Enter fullscreen mode Exit fullscreen mode
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("veenkes/veenkes-google-play-reviews").call(run_input={
    "apps": [
        "com.spotify.music"
    ],
    "maxReviewsPerApp": 100,
    "language": "en"
})

# Write every dataset item, then export from the Console or keep going in code.
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)
Enter fullscreen mode Exit fullscreen mode

The JavaScript client (apify-client on npm) uses the same Actor id and the same input object. You can also start the run with a plain HTTP POST to the Apify API if you prefer.

Sample output

Here is a shortened example of one dataset record (field values are illustrative of the schema, taken from a real sample run shape):

{
  "appId": "com.spotify.music",
  "appTitle": "Spotify: Music and Podcasts",
  "appDeveloper": "Spotify AB",
  "appScore": 4.3483925,
  "appRatingsCount": 36631501,
  "appReviewsCount": 1858962,
  "appInstalls": "1,000,000,000+",
  "appGenre": "Music & Audio",
  "appVersion": "VARY",
  "reviewId": "13b5c818-6009-49e7-af2e-2a076f33aaf5",
  "reviewUrl": "https://play.google.com/store/apps/details?id=com.spotify.music&reviewId=13b5c818-6009-49e7-af2e-2a076f33aaf5",
  "rating": 2,
  "title": null,
  "text": "id rather this than apple but the quality of the app has gone down so much since ai, its almost as if features introduced were written by ai and not tested. random features break f…",
  "date": "2026-11-11T19:54:47.254Z",
  "thumbsUp": 0,
  "appVersionReviewed": "9.1.98.621",
  "developerReply": null,
  "developerReplyDate": null,
  "language": "en",
  "country": "us",
  "scrapedAt": "2026-11-12T20:02:33.121Z"
}
Enter fullscreen mode Exit fullscreen mode

Once the run has finished, open the dataset in the Console and use Export > CSV if a spreadsheet is your destination. JSON is usually better for code and for language models.

What to use the data for

Typical uses include ASO (what phrases show up in 1-star reviews), product research (which versions triggered a wave of complaints), competitor monitoring, and building a training set for a sentiment or topic model. Because the rows are flat, you can schedule a daily run, keep only reviews newer than yesterday, and append the CSV to a warehouse.

Pricing

Pay-per-result pricing starts at $0.25 per 1,000 reviews on the Apify Free plan, with lower unit prices on paid Apify plans, plus a small per-run start fee. Always check the live pricing on the Actor page, because plans and unit prices can change. For a first test, keep the input tiny so you can inspect the schema before you scale up.

Scheduling and automations

In the Apify Console you can schedule the Actor (daily or hourly) and leave the same input in place. For incremental jobs, prefer a "since" or "posted after" style filter when the Actor offers one, so you are not paying to re-collect old rows. When a run finishes you can send a webhook, or connect the Actor in Zapier, Make or n8n. AI agents can discover and call veenkes/veenkes-google-play-reviews through Apify's MCP server using the same input.

Good practices and limits

Reviews are public, but they may still contain personal data if you enable reviewer info, and the text itself can be copyrighted by the authors. Use the data in line with Google Play's terms and applicable law. This is not an official Google API, and the Actor is not affiliated with Google.

If a run returns fewer rows than you expected, check the input caps, language or country filters, and the Actor log. A zero-row run is usually a filter or an unavailable source, not a silent crash — read the log before you increase limits.

Next step

Open the Actor and run a small job: Google Play Reviews Scraper.

If you later want this on a schedule, save the input that worked, add a date filter where it applies, and export CSV automatically from the dataset or from the API snippet above.

Top comments (0)