Google Play Reviews Scraper

Google Play Reviews Scraper exports public Google Play review rows with ratings, dates, helpful votes, app versions, and developer replies when available.

Use it for ASO review mining, release monitoring, support triage, product feedback analysis, and competitor review tracking.

Quick start

Enter a Google Play package ID, choose a small review limit, and run the Actor:

{
  "apps": ["com.instagram.android"],
  "country": "US",
  "language": "en",
  "sort": "newest",
  "maxReviews": 20
}

Open the Dataset tab to inspect or export saved reviews. The limit applies across all apps. Date filters narrow the fetched sample rather than guarantee every review in a date window.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Instagram Google Play reviews scraper
• Get Helpful German Google Play Reviews
• Compare Android Reviews for YouTube and Instagram

What you get

• Extracts: app ID, app URL, app name, review ID, review URL, reviewer display fields, rating, review text, review date, helpful votes, developer reply, app version, locale, sort order, and scrape time.
• Inputs: app IDs or Google Play URLs, country, language, sort order, maximum reviews, optional start date, and optional end date.
• Best for: mobile app feedback analysis, ASO audits, release monitoring, support workflows, and competitor review snapshots.
• Exports: Apify dataset rows downloadable as CSV, JSON, Excel, or available through the API.
• Run diagnostics: a RUN_SUMMARY record reports completed apps, per-app errors, and pending apps when a bounded run stops early.
• Login: no Google account, cookies, or Google API key are required.

What can it do?

• Export public review rows: Save ratings, review text, review dates, helpful votes, app versions, and review URLs.
• Monitor app feedback: Use country, language, sort, and date filters for release monitoring or support triage.
• Compare competitors: Run several package IDs with the same locale and compare review themes and ratings.
• Capture developer replies: Include public developer reply text and dates when Google Play exposes them.
• Use as a Google Play reviews API workflow: Run from API, schedules, webhooks, or MCP-compatible agents and export CSV/Excel/JSON.

Who is it for?

• Mobile-product teams reading public feedback and version context after releases.
• Support and customer-experience analysts grouping returned review text for manual triage.
• ASO and market researchers comparing bounded competitor samples in a chosen locale.
• Community teams reviewing available public developer-reply text and dates.

How you can use the data

• Review a small Instagram feedback sample. Use the existing Instagram package with newest order and a twenty-review total cap. Keep reviewText, rating, appVersion and reviewDate together before grouping themes in your own tool.
• Compare the apps you selected. Use the existing YouTube-and-Instagram example with one locale and a small shared cap. Keep each package ID and source link: the cap applies across all apps, and sort order affects each app's sample rather than making one global ranking.
• Inspect available public replies. Export developerReplyText and developerReplyDate with their review IDs. Null reply fields show no visible reply in that returned record, without establishing full response coverage.
• Make your own release-window or monitoring sheet. Use date bounds to filter the retrieved sample, then retain review IDs, versions and collection times in later comparisons. The Actor does not fetch until a historical window is filled, apply keyword/star filters or send monitoring notifications itself.

Input settings

Setting	JSON key	Description
App IDs or Google Play URLs	apps	One or more package IDs such as com.instagram.android or full Google Play app URLs.
Maximum reviews	maxReviews	Total maximum review rows to save across all apps. The Actor caps this at 10,000.
Country	country	Two-letter Google Play country code used for localized reviews.
Language	language	Two-letter language code used for review text and app metadata.
Review sort order	sort	newest, rating, or helpfulness.
Start date	startDate	Only save reviews on or after this date. Leave empty to disable the lower bound.
End date	endDate	Only save reviews on or before this date. Leave empty to disable the upper bound.
Work budget	maxRuntimeSecs	Work budget in seconds, default 270. Stops starting new work near the limit.
Runtime safety margin	runtimeSafetySecs	Time reserved for saving completed rows and RUN_SUMMARY, default 30. Must be lower than the work budget.

API callers may also supply package IDs in appIds, or app URLs in startUrls (strings or objects with a url key). These sources are combined with apps. At least one valid source is required. The app field's form prefill is not an API default.

Example input

{
  "apps": ["com.instagram.android"],
  "country": "US",
  "language": "en",
  "sort": "newest",
  "maxReviews": 20,
  "startDate": "2026-06-01"
}

Output data

Field	Description
appId, appUrl, appName	App package ID, Google Play URL, and app title when available.
reviewId, reviewUrl	Google Play review identifier and review URL.
reviewerName, reviewerImageUrl	Public reviewer display fields when available.
rating	Review rating from 1 to 5 when available.
reviewText	Public review text.
reviewDate	Review date returned by Google Play.
thumbsUpCount	Helpful vote count when available.
developerReplyText, developerReplyDate	Visible developer reply fields when present.
appVersion	Reviewed app version when Google Play provides it.
country, language, sort	Locale and sort settings used for the request.
status, warning	SAVED for stored review rows. warning is currently always null. Per-app errors appear in RUN_SUMMARY.
scrapedAt	Timestamp when the row was scraped.

More example output

Illustrative shape only, not an observed review or testimonial. Optional fields may be null.

{
  "appId": "com.instagram.android",
  "appUrl": "https://play.google.com/store/apps/details?id=com.instagram.android&hl=en&gl=US",
  "appName": "Instagram",
  "reviewId": "example-review-id",
  "reviewUrl": "https://play.google.com/store/apps/details?id=com.instagram.android&reviewId=example-review-id",
  "reviewerName": null,
  "rating": 4,
  "reviewText": "Illustrative review text", 
  "reviewDate": "2026-07-01T12:00:00.000Z",
  "thumbsUpCount": 3,
  "developerReplyText": null,
  "developerReplyDate": null,
  "reviewerImageUrl": null,
  "status": "SAVED",
  "warning": null,
  "appVersion": "1.0.0",
  "country": "US",
  "language": "en",
  "sort": "newest",
  "scrapedAt": "2026-07-03T09:00:00.000Z"
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing charges start once when validated extraction begins and review for each saved review. An empty or unsuccessful extraction can still incur the start charge. Validation errors occur before that charge, and no separate error or status rows are saved or charged as reviews.

Use a small shared review cap for an initial export. See the live Pricing tab for current rates and discounts. Apify platform usage may be charged separately.

Tips for best results

• Use package IDs rather than ambiguous app names. Full Google Play app URLs are also accepted.
• Set locale intentionally. Available review samples and text can differ by country and language.
• Keep a realistic shared cap across your app list. A total cap does not promise an equal sample for every package.
• Apply your own date, keyword and star filters after export. Date settings already filter a fetched sample rather than ensure complete historical coverage.
• Read per-app summary errors before comparing exports. Completed reviews can remain available after another app fails.

Limits and caveats

• Only public reviews are returned: private account data and hidden reviews are not available.
• Review availability is controlled by Google Play: some apps, countries, or languages may return fewer rows than requested.
• Developer replies are optional: reply fields are null when no public reply is visible.
• Sort order affects coverage: newest, rating (highest first), and helpfulness affect each app sample, not a global ordering across apps. There is no built-in keyword or star-rating filter. Apply those filters after export.
• Date windows are sample filters: the Actor does not guarantee a complete historical archive or keep fetching until a date window is filled.
• No built-in monitoring: each run is a snapshot. Any scheduling or notifications are configured separately in Apify.
• Unexpected upstream failures are explicit: if one app fails in a multi-app run, completed review rows remain available and RUN_SUMMARY records the affected app. If no requested app can be read, the run fails instead of reporting a successful empty dataset.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~google-play-reviews-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "apps": [
    "com.instagram.android"
  ],
  "country": "US",
  "language": "en",
  "sort": "newest",
  "maxReviews": 20
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/google-play-reviews-scraper').call({
  "apps": [
    "com.instagram.android"
  ],
  "country": "US",
  "language": "en",
  "sort": "newest",
  "maxReviews": 20
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/google-play-reviews-scraper').call(run_input={'apps': ['com.instagram.android'], 'country': 'US', 'language': 'en', 'sort': 'newest', 'maxReviews': 20})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Google Play Reviews Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Google Play Reviews Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/google-play-reviews-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Google Play Reviews Scraper by Fetch Cat, or give it the identifier fetch_cat/google-play-reviews-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Google Play Reviews Scraper to collect up to 10 newest public reviews for com.instagram.android in the US, in English. Include available app versions and developer replies, marking missing fields.”
• “Collect up to 10 reviews in total across com.google.android.youtube and com.instagram.android in the US, in English, using helpfulness order. Keep app IDs and review links and compare the returned samples without claiming equal coverage.”
• “Retrieve up to 5 newest reviews for com.instagram.android in the US, in English, dated on or after 1 June 2026. Show ratings, dates and text, and explain that the date condition filters a limited fetched sample rather than a complete archive.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I scrape multiple apps in one run?

Yes. Put multiple package IDs or app URLs in apps.

Can I scrape by country and language?

Yes. Use country and language to request localized review data.

Can I export to CSV, Excel, JSON, or API?

Yes. Apify datasets support all of those access paths.

Does this require my Google account?

No. It reads public Google Play review data.

Is each row one review?

Yes. Each saved dataset item is one public review row.

Why did I get fewer reviews than requested?

Google Play may return fewer rows for the selected app, locale, sort order, or date window.

Related Actors

• Google Play Apps Scraper — Collect public Android app listings and available detail metadata for app-market research.

• Apple App Store Reviews Scraper — Collect public iOS app review text and available storefront or version metadata.

• Apple App Store Apps Scraper — Collect public iOS app listing metadata, developers, displayed prices and version details.

• Shopify App Reviews Scraper — Collect public Shopify App Store review text, ratings and visible developer replies for app research.

• Amazon Reviews Scraper — Compare feedback for products rather than mobile apps.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥