App Store and Google Play Keywords: a-z, question words avatar

App Store and Google Play Keywords: a-z, question words

Pricing

from $2.00 / 1,000 result rows

Go to Apify Store
App Store and Google Play Keywords: a-z, question words

App Store and Google Play Keywords: a-z, question words

App Store and Google Play autocomplete keyword suggestions as CSV/JSON rows, for ASO keyword research. Columns: seed, suggestion, position, store, id. Switchable expansions: a-z, question words, prepositions, comparisons, numbers. Suggestions only: no search volume, difficulty or app rankings.

Pricing

from $2.00 / 1,000 result rows

Rating

0.0

(0)

Developer

Tallyrake Data

Tallyrake Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

App Store & Google Play Keyword Scraper: a-z suggestions

App Store and Google Play search-box suggestions as CSV/JSON rows. Give it seed keywords; it requests the suggestions each store shows as a user types, for the seed, seed + a to z, question words, and prepositions (comparisons and numbers only if you enable those expansions), for the country and language you set, on Apple, Google Play, or both. One flat row per unique suggestion per seed per store, each with a stable id.

This is not app listings, not reviews, and not rankings. It does not return app IDs, titles, screenshots, ratings, review text, or chart positions. It is the dropdown list from each store's search box, nothing else.

Same engine, other search boxes: Google, YouTube, Amazon, Bing, DuckDuckGo, Etsy, Pinterest, TikTok. Same input shape, same flat rows, one run per engine.

What you get

FieldExample
idstable per store, seed and suggestion (sha1(store|seed|suggestion), first 16 hex)
keywordphoto (your seed)
queryphoto (the exact string sent)
suggestionphoto editor
rank1 (position in that store's list for that query)
storeapple or google-play
expansiondirect, alphabet, question, preposition, comparison, number, depth
modifierb, how, for, vs
depth1 or 2
language, countryen, us
fetchedAtISO timestamp

Rows are deduplicated per seed per store (case-insensitive), so a suggestion that appears under several modifiers is counted once, under the first query that produced it. The same phrase on Apple and Google Play is two rows, with different store and id values.

Example input

{
"keywords": ["photo"],
"stores": ["apple", "google-play"],
"expansions": ["alphabet", "questions", "prepositions"],
"depth": 1,
"language": "en",
"country": "us",
"proxyConfiguration": { "useApifyProxy": true }
}

Paste seeds one per line. The default expansions send 52 queries per seed per store (1 seed + 26 letters + 14 question words + 11 prepositions = 52). Comparisons and numbers are not in that 52; they are extra expansions. With both stores selected that is 104 requests per seed before depth 2. One seed sends many queries; the output is unique dataset rows, not queries.

Proxy defaults to Apify Proxy with no proxy group (datacenter). Apple localises with X-Apple-Store-Front and a country query param; Google Play localises with hl / gl. Pin a country on the proxy as well if you need a genuine other-market exit IP.

Recipes

ASO keyword list for one app idea. Seeds: the head terms you would put in the title. Expansions: alphabet. Depth 1. Stores: both. Output: the phrases each store suggests, ranked on the query that first produced them.

Question research. Seeds: your topic. Expansions: questions, prepositions. Depth 1. Output: the questions and phrasings people type into App Store and Play search.

Localized suggestions. Same seeds, language and country set per run (de/de, ja/jp, pt/br). Rows carry both codes so runs can be merged.

Brand and competitor monitoring. Seeds: brand names. Expansions: comparisons, questions. Schedule daily. Diff the suggestion column between runs, per store.

Reliability and cost

Billing terms are on the Pricing tab of the listing. Apify platform usage is a separate charge and is not the listing price. Empty queries produce no rows. Every request is paced with a jittered delay (pacingMs, default 200 ms). If a store answers 429 or 403, the run rotates its session and retries.

No soaked run has been measured on Apify yet, so this README does not state a success rate or a platform-usage cost.

Cost limit

If a run reaches the "Maximum total charge per run" you set, it stops in process rather than being aborted by the platform: the run ends with status SUCCEEDED, and the run status message on the run detail says how many rows were written and how many were found but not written. Re-running the same input writes the same prefix again, so raise the cap before re-running if you want the rest.

Bigger jobs

Need this as a one-off file instead of a run? Ask for a quote at https://tallyrake.com/datasets/. We may decline. A quote binds nothing, and a job exists only when we confirm it in writing, before any payment.

Limits

This is each store's suggestion list for the country and language you set, at the time of the run. It carries no search volume, no difficulty, and no ranking. Apple returned 10 hints per query on the build probe; Google Play returned 5. Export CSV for Excel and Google Sheets. Export JSON for pipelines.

It is not an app-listing scraper, not a reviews scraper, and not a rankings / top-charts scraper. It does not log in, does not download IPA/APK files, and does not walk search-result pages.

Where this sits on the shelf

Apify Store, read 2026-10-18. This actor is not published. Nothing in this build charges a custom event. One default dataset row is one result.

ListingUsers (30d)Total users
codingfrontend/app-store-keywords-discovery-tool12
tallyrake/appstore-autocomplete-scraper (this actor)00