Find App Store keywords an app already ranks for

Use one known App Store app ID: the numeric identifier after id in its App Store page URL, rather than the app’s name or bundle identifier. This endpoint currently supports United States location_code 2840 and the full language_name English only. Finding an ID from an app name is a separate task.

limit must be 10, setting the maximum returned keyword records; fewer can be available. The supplier documents descending search-volume order by default, which is not the app’s highest-position order or a recommendation of its best keywords. Delivered rows differ from a supplier database total. There are no native custom sorting, filtering or pagination inputs, and the list need not cover every keyword.

For a returned keyword, rank_group describes the app’s position among results of the same type. rank_absolute describes its position across all result elements. Keep these scopes separate. They record an organic keyword search result, not an overall App Store chart rank, an independent quality score or a prediction of traffic.

No. It is the supplier’s approximate average monthly number of App Store searches for that keyword. It does not measure Google searches, unique people, actual app impressions, visits or installs. The exact averaging window and estimation method are unspecified; a missing volume remains unknown rather than zero.

The supplier describes weekly database updates, but that does not confirm the age of these records or a fresh capture. Keyword-data and search-result update timestamps describe different data and should stay separate. Available app titles, ratings and prices are recorded search context, rather than a freshly retrieved full profile or checkout quote. Store-page and icon URLs are address information, not delivered page or image files.