Compare shared App Store ranking keywords

Supply exactly two existing numeric App Store IDs in the named entries 1 and 2. They are strings, not app names or bundle IDs. This route currently supports the United States with location_code 2840 and the full language_name English. It does not add a third app or query other markets through this Tool.

No. The required limit is 10, which caps returned keyword rows. A source-database match count can be larger than the number delivered; neither count establishes every shared keyword in the App Store. There is no paging control here. An empty or partial result does not prove the apps have no overlap elsewhere or at other times.

For a particular keyword, rank_group is the app’s position among search-result elements of the same type, while rank_absolute counts its position among all search-result elements. These are recorded organic keyword positions, not App Store chart rankings, ad positions, app quality scores or a prediction of future rank. Keep the two measures separate.

When available, it estimates average monthly searches for that keyword in the App Store. It is not Google search volume, unique searchers, app traffic, installs or Apple-audited usage. Do not read it as an exact current-month count or a forecast, or add estimates to claim a distinct audience.

The supplier documents weekly updates to its database, but that schedule does not establish the latest update of each returned record or a live position at query time. If present, keyword-data and search-result timestamps describe separate updates. Use those dates with the positions and estimates; keep absent dates or values unknown.