Google Play Keywords Discovery Tool
Under maintenancePricing
from $4.99 / 1,000 results
Google Play Keywords Discovery Tool
Under maintenanceDiscover untapped keywords and search suggestions from Google Play Store in real-time. Get comprehensive insights into search trends and long-tail opportunities to supercharge your ASO keyword research.
Pricing
from $4.99 / 1,000 results
Rating
0.0
(0)
Developer
Coding Frontned
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
19 days ago
Last modified
Categories
Share
Discovers Google Play autocomplete suggestions from the current Google suggestion endpoint. It emits one rich, flat record per unique suggested keyword, never invented search volume, trend, or difficulty values.
{"keywords": ["photo editor", "video editor"],"country": "us","language": "en","expandAlphabet": true,"maxQueries": 100,"maxKeywords": 200}
Use keywords for one to twenty seeds, or the compatibility alias keyword for one seed. Query generation is deterministic: every seed query is first, then optional expansionChars, then customSuffixes, up to maxQueries. The actor stops issuing expansion requests as soon as maxKeywords has been collected, retries each request at most three times, and fails when every seed request fails or no usable suggestions exist.
Each record includes the original suggestion and category/subtype codes, first discovery position/query/rank, all discovered-by query and source URL evidence, seed provenance, response metadata, request profile/proxy strategy, and truthful derived ASO helpers: normalized keyword, word/character counts, exact-seed/starts-with-seed flags, and added terms when they can be determined from a seed prefix.
proxyConfiguration is optional. Without it requests are direct; with it the actor uses the configured Apify proxy and an optional safe proxySessionId. Missing source fields are omitted recursively—never output as nulls or empty values.
Run npm ci, npm run lint, npm test, apify run --purge --input-file qa-inputs/local-search.json, and npm run validate for local verification. A bounded cloud check can use qa-inputs/cloud-validation.json.