Understanding App Store Keyword Rankings Across Countries
Yusuf Yılmaz · November 16, 2026 · 8 min read
Every App Store country or region is a separate storefront with its own apps, languages and search results, so the same keyword can put your app near the top in one country and nowhere in another. Which of your localizations a storefront shows and searches depends on the languages Apple supports there. To judge international performance, track each important keyword in each country separately, every day, and compare each country with its own history rather than with other countries.
Why country-level rankings matter
There is no single ranking for a keyword. There is a ranking in the United States, another in Germany, another in Türkiye, and so on. Apple lets you release your app in any of the 175 countries or regions where the App Store is available, and in App Store Connect you choose whether it goes to all of them or only to specific ones. If your app is available in many countries, its search visibility is really a collection of many separate result lists.
This matters most for indie developers, whose downloads often come from a handful of countries. If you only search on your own phone, you see one storefront. A slow slide in a country you never check can go unnoticed for weeks, while your home store looks fine.
Different storefronts, different local searches
When someone in Germany searches the App Store, they search the German storefront. Its result list is built from the apps available there, and that set is not the same everywhere, because each developer decides in which countries their app is offered. An app that is not available in a country cannot appear in that country's results, and some of your strongest competitors in one market may simply not exist in another.
Apple describes the inputs to search results in general terms: text relevance (matches for your app's title, subtitle, keywords and primary category) and user behavior (downloads, ratings and reviews, and more). Apple does not publish how these are weighted or how they differ between countries, so be skeptical of anyone who claims exact numbers. What you can do is measure the outcome in each storefront.
Language and localized metadata
Your metadata is localized by language, not by country, and Apple's App Store Connect Help explains how the two meet. If English is your primary language and your only localization, your metadata appears in English in every country or region. If you add French, that localization is shown to users whose language setting is French and in countries or regions where the App Store supports French but not English. Apple also states that users can search for your app using localized keywords in all countries or regions where the App Store supports French. If no localization matches, the next most relevant one is used; otherwise the primary language is shown.
Apple publishes a table of App Store localizations that lists, for each storefront, a default language and any additional supported languages. A few rows as Apple lists them at the time of writing:
| Storefront | Default language | Additional supported languages |
|---|---|---|
| English (US) | Arabic, Chinese (Simplified), Chinese (Traditional), French, Korean, Portuguese (Brazil), Russian, Spanish (Mexico), Vietnamese | |
United Kingdom | English (U.K.) | None |
Germany | German | English (U.K.) |
Türkiye | English (U.K.) | Turkish |
Japan | Japanese | English (US) |
Two things follow. First, a localization can matter in more storefronts than its name suggests: English (U.K.) appears in the rows for Germany and Türkiye, not only the United Kingdom. Second, Apple notes that the language each customer sees can also depend on their device's language settings, the languages you have added and your primary language. Check Apple's current table before you plan, because it can change.
Why the same keyword gives different results
Take Meyu: Pregnancy Tracker and the keyword “pregnancy tracker”. Searched on the same day in five storefronts, it can produce five different positions. The usual reasons:
- Different competitors. Each storefront has its own set of available apps, including local apps that are only offered there.
- Different metadata in play. Which of your localizations a storefront uses decides which name, subtitle and keyword field can match the search.
- Different language habits. An English phrase is a natural search in the United States; in a storefront whose default language is Japanese, people often search in their own language, so the English phrase behaves very differently.
- Different user behavior. Apple lists downloads, ratings and reviews among the inputs, and how people respond to the results is not the same from one market to another.
- Different meanings. A word can mean something else in another language. “Gift” is a present in English and poison in German, so the same string reaches very different searches.
How personalization can affect observed rankings
Apple's App Store privacy page says it uses your interactions with the App Store, such as what you have searched for, viewed, downloaded or reviewed, to help you discover relevant content, and that you can turn off Personalized Recommendations for your Apple Account. Apple does not document exactly how this changes the order of search results.
The practical lesson: a search on your own phone is one view. You have probably opened your own app and your competitors' pages many times, and you only see one storefront at a time. Rank trackers read the public search results for a country, and individual users can see slightly different, personalized results. Treat a tracked rank as a consistent reference measurement and focus on its direction over time, not on whether a single person sees exactly the same position.
Why ranking history matters
Rankings move from day to day. A one-off check can catch a good day or a bad one. A daily history per country tells you whether a move is a trend, which countries moved after a release, and whether a competitor overtook you in one market only.
History is also how you judge metadata changes. Because metadata is localized, an update to one localization should show up in the storefronts that use it. Note the date of each change and compare a few weeks before and after in those countries. Keep in mind that competitors and seasons change too, so a before/after comparison is a measurement aid, not proof that your change caused the move.
Comparing country-level performance
Do not compare raw positions between countries as if they were the same race. Position 20 in a crowded storefront and position 20 in a quieter one are not equivalent. Compare each country with its own past, and use bands rather than exact numbers: top 10, 11–50, 51–200, and not in the first 200.
| Country | 4 weeks ago | Today | Reading |
|---|---|---|---|
| #31 | #27 | Small gain, same band | |
United Kingdom | #22 | #14 | Clear gain |
Germany | #48 | #63 | Dropped a band; check what changed |
France | #11 | #9 | Entered the top 10 |
Japan | 200+ | 200+ | Probably the wrong keyword for this storefront |
Illustrative example: keyword “pregnancy tracker” for Meyu: Pregnancy Tracker. The positions are made up to show how to read a comparison; they are not real data and say nothing about these markets.
Read it country by country. The German drop is worth a look: did you edit the localization that storefront uses, or did a new competitor appear? The Japanese row suggests the English phrase is not how people search there, so measuring Japanese keywords would tell you more than waiting for this one to move.
Common international ASO mistakes
- Checking only your home store. Your phone shows one storefront; most of your countries stay invisible.
- Assuming one English localization covers everything. Look up which languages each important storefront supports, then decide which localizations to fill.
- Leaving new keyword fields empty. When you add a language, its properties default to those of the primary language except the description and keywords, so you have to write the keyword field for each new language yourself.
- Translating keywords word for word. Use the words people in that market actually type, not a dictionary translation.
- Wasting characters. The keyword field is limited to 100 characters, separated by commas without spaces, and Apple advises against repeating words already in your app name, subtitle or category.
- Putting keywords in promotional text. Apple states that promotional text does not affect search ranking.
- Tracking countries where the app is not available. Check your availability settings in App Store Connect first.
- Reacting to a single day. Wait for a trend across several days before changing anything.
A practical country-tracking workflow
- Confirm which countries or regions your app is available in.
- Pick three to five priority countries: where your users already are, or where you want to grow.
- Look up each one in Apple's App Store localizations table and note which of your localizations applies there.
- Choose a few keywords per country in the language people there search in. Countries that share a language can share keywords.
- Record the position for the same keyword in the same country every day, and record “not in the first 200” when you are not found.
- When you change a localization, write down the date and compare a few weeks before and after in the countries that use it.
- Review weekly, then adjust each localization's keyword field. The keyword field guide covers how to fill those 100 characters.
With AsoGlass, this workflow runs on your iPhone. It supports all 175 App Store countries and reads each country's public App Store search results every day for the keywords you choose, up to the first 200 results, and keeps the history. Individual users can see slightly different, personalized results, so treat the numbers as a consistent daily reference. When you mark the date of a change, AsoGlass compares the 14 days before and after for each country and target keyword. For the single-country basics, see how to track App Store keyword rankings.
Keyword rank tracking feature →
FAQ
Why does my app rank well in one country and not at all in another?
Each storefront has different available apps, different supported languages and different user behavior. Your localization may not match the language people search in, or the competition may be much stronger there.
Do I need a separate localization for every country?
No. Localizations are per language, and one localization can be used in several storefronts. Apple's App Store localizations table shows which languages each storefront supports.
Can keywords from one localization be found in another country?
According to Apple, users can search using a localization's keywords in all countries or regions where the App Store supports that language. Check the table to see where each of your localizations applies.
Why does my phone show a different position than my rank tracker?
Your phone shows one storefront, possibly with results influenced by your own App Store activity, and the check may have happened at a different time. A tracker reads the public results for each country in the same way every day.
How many countries should I track?
There is no fixed number. Start with the countries that bring or could bring most of your users, and add more once you have a routine.
United Kingdom
Germany
Türkiye
Japan
France