Google Play Store App Search Scraper

Export public Google Play app search results by keyword, country, and language for ASO research and competitor discovery. Receive app IDs, titles, developers, visible ratings and listing URLs with each result's query and extraction position—without a Google account.

Quick start

1. Enter one or more search terms, then choose a country and language.
2. Start with a small per-query limit, such as 10.
3. Open the dataset to export results. Check RUN_SUMMARY for partial or empty searches.

{
  "searchQueries": ["meditation", "budget tracker"],
  "country": "US",
  "language": "en",
  "maxItemsPerQuery": 10
}

This requests up to 20 app-query rows from the initial public search responses, not every matching app. There is no app-detail enrichment or deeper pagination. Increasing the limit cannot produce apps absent from those responses.

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.

What you get

• Android package ID, app title, developer, icon, and canonical Google Play URL
• Search keyword and one-based result position
• Visible rating, rating/review count, price text, and free-download status
• Requested country and language plus the exact localized search URL
• Collection timestamp
• A RUN_SUMMARY with completed, empty, failed, and pending queries
• A PENDING_WORK checkpoint when a larger run reaches its safe runtime limit

Google Play search cards do not expose every app-detail field in every layout. category is always null in this search-only Actor. Other unavailable values remain null rather than being guessed.

Who is it for?

• ASO teams reviewing keyword visibility in a selected country-language edition.
• App publishers building source-linked lists of competing search results.
• Research agencies preparing recurring market-specific exports for clients.
• Market analysts and data engineers joining package IDs and visible search-card fields in their own reporting tools.

How you can use the data

• Review meditation and budgeting competitors. Use the existing two-query input with ten rows per query. Keep searchQuery, appId, appTitle, developer and detailUrl together because each row describes an app in the context of one search.
• Keep market comparisons separate. Use the existing US meditation, UK budget-tracker or German fitness recipes in separate runs. Compare like-for-like country and language snapshots yourself, retaining sourceUrl and scrapedAt rather than treating positions as universal ranks.
• Make an honest search-card review sheet. Retain visible rating, rating-count and purchase labels, while leaving absent values unknown. In-app purchases do not by themselves make a free download paid, and category remains null because this Actor does not enrich app details.
• Continue bounded work or start a new snapshot deliberately. Inspect summary outcomes and any saved pending work before resurrecting the same run with unchanged input. A fresh run starts a new snapshot. Compare later datasets in your own spreadsheet or warehouse, allowing for changed source results and checkpoint-write failures.

Input settings

Setting	JSON key	Description
Search queries	searchQueries	Required list of 1-20 keyword strings. Each query can contain up to 200 characters.
Maximum apps per query	maxItemsPerQuery	Number of visible results to save per query, from 1 to 100. Default: 10.
Country	country	Two-letter country code such as US, GB, DE, or IN. Default: US.
Language	language	Language code such as en, es, de, fr, or pt-BR. Default: en.
Safe runtime limit	maxRuntimeSecs	Runtime budget from 35 to 270 seconds. The default 240 leaves time to save progress before shutdown.

Up to 20 queries are accepted. Each run uses one country/language pair and direct public access. There is no proxy or connection selector.

Input recipes

• US meditation competitors: {"searchQueries":["meditation"],"country":"US","language":"en","maxItemsPerQuery":10}
• UK budgeting apps: {"searchQueries":["budget tracker"],"country":"GB","language":"en","maxItemsPerQuery":10}
• German fitness results: {"searchQueries":["fitness tracker"],"country":"DE","language":"de","maxItemsPerQuery":20}
• Multi-keyword snapshot: add several related terms to searchQueries. Each row retains its originating query.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Illustrative row shape, not a current search result or a guaranteed app position:

{
  "searchQuery": "meditation",
  "position": 1,
  "appId": "com.calm.android",
  "appTitle": "Calm - Sleep, Meditate, Relax",
  "developer": "Calm.com, Inc.",
  "rating": 4.4,
  "ratingCount": null,
  "installRange": null,
  "priceText": "In-app purchases",
  "isFree": null,
  "category": null,
  "detailUrl": "https://play.google.com/store/apps/details?id=com.calm.android",
  "iconUrl": "https://play-lh.googleusercontent.com/...",
  "country": "US",
  "language": "en",
  "sourceUrl": "https://play.google.com/store/search?q=meditation&c=apps&hl=en&gl=US",
  "scrapedAt": "2026-07-20T12:00:00.000Z"
}

More output fields

Field	Description
searchQuery	Keyword that produced the result.
position	One-based extraction order among usable, unique app results for that query—not a universal Google Play rank.
appId	Android package identifier.
appTitle	Public app name.
developer	Developer shown on the search card, or null.
rating	Visible average star rating, or null.
ratingCount	Visible compact rating/review count, or null.
installRange	Visible install/download range when present on the search card, otherwise null.
priceText	Visible price or purchase label, or null.
isFree	Whether the download is shown as free, or null when not determinable. In-app purchases do not make a free download paid.
category	Always null. Category enrichment is not supported.
detailUrl	Canonical public Google Play app URL.
iconUrl	Public app icon URL, or null.
country	Country code used for the search.
language	Language code used for the search.
sourceUrl	Localized public search URL used for the result.
scrapedAt	ISO 8601 collection timestamp.

The default key-value store also exposes RUN_SUMMARY, including status, saved, failedQueries, emptyQueries and pendingQueries. A valid no-match search is listed in emptyQueries after a source-health check. A successful platform run can still contain partial results: inspect the summary before comparing snapshots.

If the safe runtime or maximum Actor charge interrupts work, the Actor attempts to save PENDING_WORK. Resurrecting the same run with unchanged input resumes saved progress. A fresh run starts a new snapshot. Checkpoint writes can fail, and a resumed search can see changed source results, so resumption is not an unconditional completeness guarantee.

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

A run charges start once, then item only for each app row successfully saved. Resurrecting the same checkpointed run does not repeat the start charge. Empty searches, failed queries, warnings, RUN_SUMMARY and PENDING_WORK are not charged as items, while a start charge can apply even when no app is returned.

Bound work with query count, per-query app caps, the runtime budget and Apify's maximum charge per run. See the Actor's live Pricing tab for current event prices and account-tier discounts. Standard Apify platform or storage-access charges may also apply.

Tips for best results

• Start with one specific keyword and a small per-query cap. A larger cap cannot expose apps absent from the initial public response.
• Match country and language when comparing snapshots. Each run uses one market pair.
• Keep separate market tasks when scheduling exports. The existing monitoring workflow compares files downstream rather than tracking changes inside the Actor.
• Read RUN_SUMMARY before interpreting missing rows. It separates verified empty searches, query failures, charge-limit stops and safe-runtime stops.
• Use the same input when resurrecting a checkpointed run. Inspect pending work first and do not assume every checkpoint write or resumed search is complete.

Limits and caveats

• The Actor covers the public Google Play /store/search surface only. It does not fetch app-detail pages, reviews, charts, collections, developer catalogs, or private data.
• It does not log in, accept cookies, solve CAPTCHAs, use private endpoints, or attempt stealth bypasses.
• Google Play can vary results by country, language, time, and user context, so ranks are snapshots rather than permanent positions.
• Search cards expose fewer fields than app-detail pages. Missing values remain null.
• Temporary rate limits and source error pages are retried within a bounded run budget. One failed query does not discard valid rows from other queries.
• A no-match query finishes as a verified empty result when a bounded control search confirms that Google Play's result layout is healthy. If that control search is also empty, the query is reported as source drift instead of a misleading successful-empty result.

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-store-app-search-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "searchQueries": [
    "meditation",
    "budget tracker"
  ],
  "country": "US",
  "language": "en",
  "maxItemsPerQuery": 10
}
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-store-app-search-scraper').call({
  "searchQueries": [
    "meditation",
    "budget tracker"
  ],
  "country": "US",
  "language": "en",
  "maxItemsPerQuery": 10
});
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-store-app-search-scraper').call(run_input={'searchQueries': ['meditation', 'budget tracker'], 'country': 'US', 'language': 'en', 'maxItemsPerQuery': 10})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Google Play Store App Search 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 Store App Search 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-store-app-search-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 Store App Search Scraper by Fetch Cat, or give it the identifier fetch_cat/google-play-store-app-search-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 Store App Search Scraper to collect up to 5 app results per query for meditation and budget tracker in the US, in English. Keep originating queries, package IDs, listing links and visible ratings without adding app details.”
• “Collect up to 5 fitness tracker search-card results in Germany, in German. Show source search URLs and extraction positions, leaving category and unavailable install or count fields unknown.”
• “Retrieve up to 5 budget tracker app results in Great Britain, in English. Keep collection times and package IDs for my own later comparison, and check whether the summary reports verified empty, failed or pending queries.”

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.

Schedule Google Play keyword monitoring

Save one task per market, then use an Apify schedule to run it daily or weekly. Export each dataset to Google Sheets or a warehouse, or attach a webhook that notifies your workflow when the run finishes. Compare appId and position across snapshots to detect new competitors and ranking changes.

FAQ

Is this a Google Play Search API alternative?

It provides a structured API workflow for public Google Play search results, but it is not an official Google API and does not provide private account data or every app-detail field.

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

Yes. Apify datasets support CSV, Excel, JSON, JSONL, XML, RSS, and HTML exports, plus API access.

Does it require a Google account, cookies, or a token?

No. It reads public search pages without Google login credentials or cookies. You still need an Apify token when calling the Actor through the API.

Can I search multiple keywords?

Yes. Add up to 20 strings to searchQueries. maxItemsPerQuery applies separately to each query.

Can I compare countries and languages in one run?

One run uses one country and language pair. Use separate runs or saved tasks for clean market comparisons.

Why are installs, category, or counts sometimes null?

Install and review counts appear only when recognizable on the public search card. category is always null. This search-only Actor does not open app-detail pages or invent missing values.

What happens if one keyword fails?

Valid results from other keywords remain in the dataset. RUN_SUMMARY records the failed query and cause. A legitimate no-match keyword is recorded in emptyQueries and is not treated as a failure. The run fails only when no output or verified-empty query succeeds.

Is collecting public app search data legal?

The Actor collects publicly visible search information. Your use of the data must comply with applicable laws, Google Play terms, privacy obligations, and your organization’s policies.

Related Actors

• Google Play Apps Scraper for search plus direct app-detail enrichment
• Google Play Reviews Scraper for public Android review analysis
• Apple App Store Reviews Scraper for iOS reviews and ratings
• Google Trends Scraper for current country-level trending topics and traffic labels, without historical keyword-interest data
• Google Ads Transparency Center Scraper for competitor advertising research

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