Google Play Scraper avatar

Google Play Scraper

Pricing

from $4.99 / 1,000 results

Go to Apify Store
Google Play Scraper

Google Play Scraper

A robust, high-performance utility designed for developer automation, data integration, and AI training. Features built-in captcha bypass, headful/headless browser execution, and proxy support to scrape Google data seamlessly, reliably, and at scale.

Pricing

from $4.99 / 1,000 results

Rating

0.0

(0)

Developer

Coding Frontned

Coding Frontned

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Share

Extract verified public Android app metadata from Google Play search results or direct app URLs. The Actor uses package IDs from the server-rendered search page and schema.org SoftwareApplication evidence from each detail page, so it does not depend on browser scrolling or brittle visual selectors.

Input

  • mode: search or productUrl.
  • query: search phrase, up to 120 characters.
  • productUrls: 1–20 Google Play app URLs in direct mode.
  • maxItems: 1–25 apps.
  • includeReviews: include public review snippets.
  • maxReviewsPerApp: 1–10 snippets per app.
  • gl, hl: lowercase country and language codes.
  • proxyConfiguration: optional Apify/custom proxy; direct requests are the default.
{
"mode": "search",
"query": "fitness tracker",
"maxItems": 5,
"includeReviews": true,
"maxReviewsPerApp": 3,
"gl": "us",
"hl": "en"
}

Output

Every app record includes its package ID, canonical localized detail URL, app name, developer, mode, country/language, source page, and timestamp. Source availability can add icon, description, category, operating system, content rating, rating/review count, price/currency, downloads label, ads/IAP flags, and update date.

When reviews are enabled, each snippet contains a deterministic hashed ID, rating, text, and available date/helpfulness count. Reviewer display names are deliberately excluded. Missing optional values are omitted rather than padded with placeholders.

The run is atomic: a failed search/detail request, challenge, malformed app page, or zero-result condition fails before the dataset is written. Live Google Play data and ordering can change between runs.