App Store Keywords Discovery Tool avatar

App Store Keywords Discovery Tool

Pricing

from $4.99 / 1,000 results

Go to Apify Store
App Store Keywords Discovery Tool

App Store Keywords Discovery Tool

Discover untapped keywords from Apple App Store search suggestions. Get real-time keyword data for ASO optimization and market research.

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

This Actor reads Apple’s public App Store search-hints service and is deployed as codingfrontend/app-store-keywords-discovery-tool.

Primary source: https://search.itunes.apple.com/WebObjects/MZSearchHints.woa/wa/hints

What it extracts

For a seed term and App Store country, the Actor makes bounded direct HTTPS requests to Apple’s public XML hints endpoint. It emits one source-backed keyword_suggestion record per unique normalized suggestion, including the seed, exact source query, country/storefront, query position, suggestion position, expansion suffix, official Apple search URL when supplied, response evidence, and quality flags.

Alphabet expansion issues the seed plus a-z and 0-9 variations, capped at 37 queries and the configured keyword maximum. Requests are serialized and optionally paced.

Input

{
"keyword": "photo editor",
"country": "us",
"expandAlphabet": true,
"maxKeywords": 200,
"maxQueries": 37,
"timeoutSecs": 30,
"requestDelayMs": 150
}

Limits and local verification

Only direct public Apple XML requests are used. There is no browser automation, Crawlee runtime, proxy, retry, stealth, login, or access-control bypass. HTTP errors, challenges, unexpected response types, and empty hint responses become diagnostics; no keywords are fabricated.

Run locally with:

apify validate-schema
apify run --purge --input-file qa-inputs/local-single-query.json
npm test

The cloud validation input is capped at ten suggestions and one request. The dataset uses source-backed records and the OUTPUT_SUMMARY key-value store. Invalid inputs fail before any HTTP request or dataset write. The runtime validator rejects null, blank, empty, and credential-like values.