Google Play Apps Scraper

Google Play Apps Scraper exports public Google Play app search results and app detail metadata for ASO, market research, and competitor tracking.

Use it to collect Android app titles, package IDs, developers, ratings, installs, prices, categories, descriptions, screenshots and videos, release notes, Android requirements, public developer contacts, and localized metadata.

Quick start

Enter a search query and choose a small result limit:

{
  "queries": ["fitness tracker"],
  "country": "us",
  "language": "en",
  "maxResults": 10,
  "includeDetails": true
}

Run the Actor, then download dataset rows as CSV, JSON or Excel. This returns app listings and metadata, not individual review text or official category charts.

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:

• Extract metadata from Google Play app URLs
• Enrich Android package IDs with Google Play metadata
• Scrape Google Play search results for an ASO keyword

What you get

• Extracts: app ID, title, developer, URL, icon, rating, ratings/reviews counts, installs, price, ads/IAP flags, category, summary, description, media URLs, release/update data, developer website, and developer email when available.
• Inputs: search queries, direct app IDs, direct Google Play app URLs, country, language, maximum results, detail toggle, and price filter.
• Best for: ASO research, competitor discovery, app store market snapshots, lead enrichment, and product intelligence.
• Exports: Apify dataset rows downloadable as CSV, JSON, Excel, or available through the API.
• Login: no Google account, cookies, or Google API key are required.

What can it do?

• Export Google Play search results: Save app rows in returned search order for keywords, category terms, brands, or competitor searches. Category terms are searches, not official category charts.
• Enrich known apps: Fetch app metadata from direct package IDs or Google Play app URLs.
• Collect ASO fields: Capture titles, summaries, descriptions, ratings, installs, screenshots, categories, and pricing signals.
• Localize market snapshots: Use country and language inputs to compare localized rankings, prices, and metadata.
• Use as a Google Play apps API workflow: Run from API, schedules, webhooks, or MCP-compatible agents and export CSV/Excel/JSON.

Who is it for?

• ASO researchers reviewing keyword search results and available app-listing metadata.
• Mobile-product teams comparing known competitor packages in selected markets.
• Market analysts assembling source-linked snapshots of Android app listings.
• App-data engineers joining package identifiers to available public detail fields.

How you can use the data

• Review a fitness-keyword sample. Use the existing fitness tracker query with a ten-app cap and details enabled. Compare title, summary, rating, installs and category while keeping appId, appUrl and locale beside each row. The rank describes retained query candidates rather than an official chart position.
• Enrich known packages. Use package IDs such as the existing Spotify and Duolingo examples to request detail metadata. Direct IDs and URLs always fetch details, even when optional search enrichment is disabled.
• Compare localized listings yourself. Repeat a bounded known-package or keyword export with deliberate country and language choices. Keep prices, currency, locale and collection time together, and verify critical comparisons with direct IDs because upstream country and price filtering is best effort.
• Build your own competitor-change sheet. Save package IDs, release notes, versions, Android requirements and collection times, then compare later files in your database. Missing detail fields remain unknown, and the Actor does not track changes or send alerts itself.

Input settings

Setting	JSON key	Description
Search queries	queries	Google Play search terms such as app categories, brands, competitors, or keywords.
App IDs	appIds	Direct Android package IDs such as com.spotify.music.
Google Play app URLs	startUrls	Direct Google Play app detail URLs. Use queries for search discovery.
Country code	country	Two-letter Google Play country code used for localized rankings and prices.
Language code	language	Two- or three-letter language code. Default en.
Maximum apps	maxResults	Combined limit of 1–500 distinct apps. API default 25, form example 20.
Include detailed app metadata	includeDetails	Enrich search results. Default true. Direct IDs and URLs always request details.
Search price filter	price	Best-effort search filter: all (default), free, or paid. Does not filter direct inputs.
Detail request concurrency	maxConcurrency	Simultaneous detail requests, from 1 to 10. Default: 3.
Transient request retries	maxRequestRetries	Retries for rate limits, server errors, timeouts, and network failures. Default: 2.
Processing time limit	runTimeSecs	Soft limit for starting new work. Default 270 seconds. In-flight requests can continue.

Provide at least one nonempty query, valid app ID or app detail URL. Inputs can be combined. Duplicate app IDs are saved once. The combined limit reserves space for direct IDs and URLs, so search results cannot use all their slots.

Combined input example

{
  "queries": ["fitness tracker"],
  "appIds": ["com.spotify.music"],
  "country": "us",
  "language": "en",
  "maxResults": 10,
  "includeDetails": true,
  "price": "all"
}

Output data

Field	Description
query, rank, inputType	Query and 1-based position among retained candidates for that query, or null for direct inputs. Input type is search, appId, or url. Not an absolute Google Play chart rank.
appId, title, developer, developerId, appUrl	Core app identity and Google Play URL.
icon, screenshots, headerImage	Public image URLs when available.
rating, ratingText, ratingsCount, reviewsCount	Rating and review metrics when Google Play provides them.
installs, minInstalls, maxInstalls	Display and numeric install count fields when available.
price, originalPrice, priceText, currency, free	App purchase price and currency data, not Actor fees.
containsAds, inAppPurchases, inAppPurchaseRange	Monetization flags and purchase range when available.
category, categoryId, categories	Primary and additional category values.
summary, description	Short summary and long description when detail data is fetched.
contentRating, released, updated, version	Store metadata fields when available.
ratingHistogram, recentChanges	Rating distribution and latest public release notes when available.
size, androidVersion, androidVersionText	Download size and Android requirements when available.
video, videoImage, available, hasEarlyAccess, preregister, isAvailableInPlayPass	Promotional and availability metadata.
developerInternalId, developerWebsite, developerEmail, developerAddress, developerLegal*	Public developer identifiers, contact and legal fields when Google Play exposes them.
locale, scrapedAt	Request locale and scrape timestamp.

Example output

Synthetic shape-only illustration, not an observed app or a completeness guarantee. Unavailable scalar fields are null. Media/category arrays may be empty.

{
  "query": "fitness tracker",
  "rank": 1,
  "inputType": "search",
  "appId": "com.example.fitness",
  "title": "Example Fitness App",
  "developer": "Example Developer",
  "appUrl": "https://play.google.com/store/apps/details?id=com.example.fitness&hl=en&gl=US",
  "rating": 4.5,
  "ratingsCount": 12000,
  "installs": "1,000,000+",
  "free": true,
  "containsAds": true,
  "inAppPurchases": true,
  "category": "Health & Fitness",
  "locale": "en_US",
  "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 after input validation and result for each saved app row, including a lightweight search row preserved when detail enrichment fails. There are no paid status or error dataset rows. A run that saves no apps can still incur the start event.

Use a small combined app cap and disable optional search details for lighter results. Direct IDs and URLs still request details. See the Pricing tab for current rates and discounts.

Tips for best results

• Use package IDs for apps you already know. They avoid ambiguity in names and request detail metadata directly.
• Reserve enough of the combined cap for your intended inputs. Direct IDs and URLs have reserved slots, and duplicates are saved once.
• Choose country and language deliberately. Search order, prices and metadata can differ by locale, while upstream filters remain best effort.
• Keep details enabled when the extra fields matter. Developer contacts, screenshots, installs and full descriptions depend on detail availability.
• Keep original source links when comparing exports. Verify important market or price observations rather than inferring missing values.

Limits and caveats

• This is not a reviews scraper: use Google Play Reviews Scraper for review text and developer replies.
• Fields vary by app: some apps do not expose contact details, screenshots, install ranges, or update data.
• Search ranking changes: Google Play search order can shift by country, language, time, and personalization outside the Actor.
• Large runs can take longer: detail pages are richer but slower than search-card metadata.
• Google Play can vary search behavior: upstream Google Play responses have occasionally ignored country or price filters. Treat those filters as best-effort and verify critical market comparisons with direct app IDs.
• Partial runs preserve useful data: when search detail enrichment fails, the search-card row is kept when possible. Failed direct lookups have no card to preserve. RUN_SUMMARY records saved counts, failed lookups and whether the soft processing limit was reached. Currently a run with no saved apps fails.

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-apps-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "queries": [
    "fitness tracker"
  ],
  "country": "us",
  "language": "en",
  "maxResults": 10,
  "includeDetails": true
}
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-apps-scraper').call({
  "queries": [
    "fitness tracker"
  ],
  "country": "us",
  "language": "en",
  "maxResults": 10,
  "includeDetails": true
});
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-apps-scraper').call(run_input={'queries': ['fitness tracker'], 'country': 'us', 'language': 'en', 'maxResults': 10, 'includeDetails': True})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents notes

• “Search for budgeting apps on Google Play with country: gb, language: en, maxResults: 20 and includeDetails: true.”
• “Enrich com.spotify.music and com.duolingo, then compare ratings, installs, recent changes, and Android requirements.”
• “Export lightweight search results for fitness tracker without fetching app detail pages.”

MCP and AI agents

You can ask your AI assistant to collect data with Google Play Apps 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 Apps 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-apps-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 Apps Scraper by Fetch Cat, or give it the identifier fetch_cat/google-play-apps-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 Apps Scraper to collect up to 10 apps for fitness tracker in the US, in English, with details enabled. Show package IDs, source links and available ratings, installs and descriptions without calling the positions official chart ranks.”
• “Retrieve detail metadata for com.spotify.music and com.duolingo in the US, in English, with a combined cap of 2 apps. Keep available recent changes, Android requirements and collection times for my own comparison.”
• “Collect up to 5 budgeting-app search results for country GB in English with optional details disabled. Keep package IDs and source links, and mark unavailable detail fields rather than implying that direct lookups would skip details.”

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 export app data to CSV, Excel, JSON, or API?

Yes. Apify datasets support all of those access paths.

Does this require a Google Play account?

No. It reads public Google Play app data.

Can I scrape reviews with this Actor?

No. Use Google Play Reviews Scraper for review rows.

Why are some fields null?

Google Play does not expose every field for every app, and some fields require includeDetails: true.

Is this a Google Play API alternative?

It provides public app search and detail exports through the Apify API. It is not an official Google API, and it does not return review text, developer catalogs or official top charts.

Can I monitor competitors over time?

Compare exports from repeated runs in your own workflow. The Actor does not track changes or send alerts itself.

Related Actors

• Google Play Reviews Scraper — Collect public Android app review text, dates and available ratings or developer replies.
• Apple App Store Apps Scraper — Collect public iOS app listing metadata, developers, displayed prices and version details.
• Apple App Store Reviews Scraper — Collect public iOS app review text and available storefront or version metadata.
• Google Ads Transparency Center Scraper — Collect public ad records, advertiser identities and available creative text or media for advertising research.
• Chrome Web Store Scraper — Collect public extension listings, ratings, publisher information and available version metadata.

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. ♥