This tutorial shows how to scrape App Store reviews into a clean CSV using the App Store Reviews Scraper template for UScraper. You will import the workflow, replace the sample app IDs and country feeds, set the export path, run a small validation batch, and spot-check the review rows before scaling.
Before you start
Prerequisites for scraping App Store reviews
You need UScraper installed as a local desktop app, one or more App Store listing URLs or app IDs, the storefront country code you want to inspect, and a folder where the CSV can be written. Start with one app, one country, and one or two review pages so you can confirm the feed has rows before a larger run.
This tutorial covers public review feeds, not private dashboards, paid analytics, account-only data, CAPTCHA bypassing, or review responses. Apple also provides official App Store Connect API resources for customer reviews and responses; use that route when you are managing reviews for apps you own or administer.
Compliance first: collect only data you are allowed to use, keep pacing modest, avoid bypassing access controls, and treat review text and reviewer metadata as user-generated content.
Workflow anatomy
What the App Store reviews scraper does
The companion template follows a simple block path: Navigate -> Wait for Page Load -> Inject JavaScript -> Wait for Element -> Structured Export -> Sleep -> Loop Continue. Navigate holds the review feed URLs. The JavaScript block parses the JSON body, creates one .review-row per review, and Structured Export turns those rows into CSV columns.
The bundled JSON export is the source of truth. It uses Apple's public iTunes customer review RSS JSON feed, pages 1-10 per configured app, and appends rows into one CSV. A sample feed looks like:
https://itunes.apple.com/us/rss/customerreviews/page=1/id=324684580/sortby=mostrecent/json
To adapt that URL, change the country segment, page number, and app ID. Keep sortby=mostrecent when the goal is release monitoring or post-update feedback.
| Workflow piece | What to edit | Why it matters |
|---|---|---|
| Country code | us, jp, gb, or another storefront | Reviews differ by market and language. |
| App ID | Numeric ID from the App Store URL | Selects the app to export. |
| Page range | Usually page 1 through page 10 | Broadens coverage. |
| App URL map | App ID to listing URL | Keeps input_url useful for QA. |
| Save location | Structured Export folder | Avoids overwriting prior runs. |
Runbook
How to scrape App Store reviews to CSV
Import the template
Open App Store Reviews Scraper, download the JSON, import it into UScraper, and open the canvas.
Replace app inputs
In Navigate, replace the sample feeds with your country code, app ID, and page numbers. Keep one app for the first test.
Update the URL mapping
In the JavaScript block, update the app ID map so input_url points to the correct listing.
Set the export destination
Confirm apple-store-app-reviews-scraper.csv, headers, append mode, and the save folder.
Run a small validation batch
Run one app with one or two pages. Compare the CSV rows against the JSON feed.
Expand and rerun
Add more pages, countries, or app IDs only after the first rows check out.
Output
What the App Store reviews CSV contains
There is no bundled CSV sample, so use the JSON workflow and column list as the authoritative export shape. Each .review-row becomes one CSV row.
| Column | Meaning |
|---|---|
input_url | App Store listing URL mapped from the app ID |
app_review_page_url | Public iTunes review page URL |
reviewer_name | Reviewer display name |
reviewer_url | Reviewer profile URI when present |
review_date | Updated timestamp for the review |
review_rating | Numeric rating, usually 1 through 5 |
review_title | Short review title |
review_content | Full review body text |
review_version | App version associated with the review |
review_id | Review entry identifier for dedupe |
review_vote_sum | Vote score when Apple exposes it |
review_vote_count | Number of votes when present |
Validation
Fix common App Store review scraping issues
Most App Store scraping problems show up as empty rows, missing versions, or fewer reviews than expected. Work from the URL first, then the parser, then the export path.
| Symptom | Likely cause | Fix |
|---|---|---|
| No CSV file appears | Save folder is wrong or Structured Export did not run | Confirm the save location, headers, file name, and block connection. |
| CSV has headers but no rows | Feed returned no review entries or app ID is wrong | Open the feed URL directly and test page 1 for the same country. |
| Duplicate review rows | Same feed URL appears more than once | Sort by review_id, remove repeated URLs, and rerun. |
| Rows stop after one page | Loop Continue is disconnected or disabled | Reconnect the final block and confirm Navigate still has multiple URLs. |
Keep an audit note beside recurring exports: app ID, country, page range, run date, template version, and output filename.
Alternatives
App Store reviews API, Python scraper, or no-code template?
There are four common ways to collect App Store review data. Choose based on ownership, code needs, infrastructure, and data custody.
| Option | Best fit | Trade-off |
|---|---|---|
| UScraper local template | No-code CSV exports and visible QA | You manage feed URLs and validation. |
| App Store Connect API | Owned-app review access and responses | Requires authorized access. |
| Python or Node scraper libraries | Custom pipelines and notebooks | You maintain retries and schema drift. |
| Hosted scraping APIs and actors | Managed infrastructure or API responses | Data and billing flow through a vendor. |
If you searched for app store scraper python, use a library for code-heavy analysis. If you searched for app store reviews api, compare App Store Connect for owned apps against hosted APIs for public review collection. If you need a spreadsheet today, the UScraper path is: import, configure, run, validate, export.
FAQ
App Store review scraper FAQ
Yes. UScraper uses public iTunes customer review RSS JSON URLs and exports the fields Apple returns. App Store Connect is better when you are an authorized app owner and need official review management.
Next step
Download the App Store reviews scraper template
When you are ready to run the tutorial, download the JSON from App Store Reviews Scraper and keep this article open for validation. For adjacent workflows, browse the UScraper template library or the UScraper blog.