This tutorial shows how to scrape Google Play reviews from app detail URLs into CSV with the Google Play APP Avis Scraper for UScraper. You will import the workflow, replace the sample app URLs, set the export folder, run a small validation batch, and troubleshoot the common cases that make Google Play review exports return empty rows.
CSV
8
URLs
Stable
Local
Before you start
Prerequisites and policy checks
You need UScraper installed as a local desktop app, a short list of Google Play app detail URLs, and a folder where CSV exports can be written. Start with one or two app URLs before adding a full competitor list. Google Play pages can vary by region, language, app availability, account state, and layout changes, so your first run is a validation pass.
Use the Google Play APP Avis Scraper template as the download path for this tutorial. The template is designed for public app pages you can inspect in a browser. It is not a method for bypassing sign-in walls, bot checks, paywalls, account areas, or access controls.
Technical access is not permission. Before collecting or storing review data, review Google Play terms, your local privacy obligations, and the purpose for which the data will be used.
Workflow
How the Google Play reviews scraper works
The workflow uses a multi-URL navigation loop. For each app URL, UScraper waits for the page, checks whether an app title exists, looks for a "See all reviews" or localized "Afficher tous les avis" button, opens the review dialog, scrolls the active review container, expands longer comments, then exports loaded review cards.
If the app page is unavailable or the title check fails, the workflow continues to the next URL. If the review dialog button is not available but review cards already exist, a fallback Structured Export path can still write visible rows.
Paste Google Play app detail URLs into the Navigate block. Keep hl and gl parameters consistent so the exported reviews match the language and market you intend to analyze.
Steps
Scrape Google Play app reviews to CSV
Import the template
Open the related template page, download the hosted JSON, and import it into UScraper. Keep the original workflow unchanged for the first test run.
Replace the sample URLs
In the Navigate block, replace the three sample app detail URLs with the Google Play apps you want to review. Use complete URLs, including app IDs and any intended hl or gl parameters.
Set the export folder
Open the Structured Export block and choose the folder where google_play_app_avis_scraper.csv should be saved. The template uses append mode, so keep one file per project or clear the file before a fresh run.
Run a single-app test
Run one app URL first. When the page opens, confirm that the review dialog appears, the page scrolls, and rows are written before you add more URLs.
Validate the CSV
Open the CSV and compare several rows against visible Google Play reviews. Check app name, reviewer name, date, star rating, helpful votes, and comment text before trusting a larger batch.
Output
What the Google Play reviews CSV contains
The export shape comes from the template JSON. There is no separate sample CSV in the bundle, so the configured Structured Export columns are the source of truth.
google_play_app_avis_scraper.csvColumn
nom_du_App
App title from the current Google Play page.
Column
star_du_App
App-level rating when visible, such as 4.5 star.
Column
nombre_avis
Visible total review count parsed from the page.
Column
nom_du_client
Reviewer display name from the review card.
Column
date_commentaire
Visible review date.
Column
star_rating
Numeric star rating parsed from the review card label.
Column
nombre_avis_utiles
Helpful-vote count, defaulting to 0 when absent.
Column
commentaire
Review text, including expanded long comments when available.
Use this CSV for ASO keyword research, release feedback triage, competitor sentiment checks, QA reports, and manual labeling.
Validation
Validate the first run before scaling
After the first run, do not judge success by row count alone. Pick three exported rows and open the same app page in the browser. Confirm that reviewer name, review date, star rating, helpful votes, and comment text match the visible locale.
Also verify the app-level fields. nom_du_App should match the current app page, star_du_App should capture the visible rating when present, and nombre_avis should be treated as page text rather than a guaranteed count of exported written reviews.
Alternatives
Google Play reviews API, code libraries, and scraper tools
There are three practical ways to download Google Play reviews. Choose based on ownership, volume, and maintenance appetite.
| Method | Best fit | Trade-off |
|---|---|---|
| Official Google Play Developer API | Your own apps, authenticated review workflows, support tooling | Requires Play Console access and API setup; not a public competitor research path |
| Open-source google-play-scraper libraries | Developer-owned pipelines in Node.js or Python | You own code, limits, retries, exports, and maintenance |
| UScraper template | No-code CSV exports from known public app URLs | You still need policy review, validation, and selector maintenance |
UScraper is different because this path starts from a local desktop workflow and a transparent JSON template you can inspect and adjust.
Troubleshooting
Common issues when scraping Google Play reviews
Check that the app URL opens normally, the app title exists, and the reviews dialog appears. Then rerun with one URL and increase waits only after confirming that review cards are visible.
FAQ
FAQ
Is it legal to scrape Google Play app reviews?
Public Google Play reviews can be visible in a browser, but automated collection may still be limited by terms, robots rules, copyright, privacy law, and local regulations. Use conservative pacing and avoid bypassing access controls.
Do I need the Google Play reviews API for this workflow?
No API key is required because the template opens public app detail pages and exports visible review cards. The official API is usually better when you own the app and have Play Console access.
What fields does the Google Play APP Avis Scraper export?
The template exports nom_du_App, star_du_App, nombre_avis, nom_du_client, date_commentaire, star_rating, nombre_avis_utiles, and commentaire to google_play_app_avis_scraper.csv.
Why did the scraper return zero Google Play review rows?
Common causes include unavailable app URLs, locale mismatch, no visible review dialog, slow loading, changed markup, access checks, or export running before review cards load.
Can I use google-play-scraper from GitHub instead?
Yes. Node.js and Python google-play-scraper libraries are useful when your team wants code ownership. You will also own setup, retries, CSV formatting, and compliance review.
Where does UScraper save the Google Play reviews CSV?
The stock workflow writes google_play_app_avis_scraper.csv to the save folder configured in the Structured Export block, with headers enabled and append mode turned on. Change the save location before running a production batch.
For the shortest path, import the Google Play APP Avis Scraper, run a one-app validation export, and then expand your app list in controlled batches. You can also browse the full template library or return to the UScraper blog for related no-code scraping tutorials.