ASO Cross Localization

Cross-localization is the App Store Optimization (ASO) trick that lets you use more keywords in your App Store title (30 characters), subtitle (30 characters), and keyword field (100 characters). This powerful ASO technique allows you to increase the character space for your app’s metadata by utilizing metadata in different country App Stores. Scroll down past the chart below for the 10 top rules for using cross-localization effectively. This is only applicable to the App Store, not Google Play.

Cross-Localization of App Store Territories & Locales (2024)


United StatesEnglish (US)Spanish (Mexico), Russian, Chinese (Simplified), Arabic, French, Portuguese (Brazil), Chinese (Traditional), Vietnamese, Korean
United KingdomEnglish (UK)English (Australia)
AlgeriaArabicFrench, English (UK)
AngolaEnglish (UK)
AnguillaEnglish (UK)
Antigua and BarbudaEnglish (UK)
ArgentinaSpanish (Mexico)English (UK)
ArmeniaEnglish (UK)
AustraliaEnglish (Australia)English (UK)
AustriaGermanEnglish (UK)
AzerbaijanEnglish (UK)
BahamasEnglish (UK)
BahrainArabicEnglish (UK)
BarbadosEnglish (UK)
BelarusEnglish (UK)
BelgiumEnglish (UK)French, Dutch
BelizeSpanish (Mexico)English (UK)
BeninEnglish (UK)French
BermudaEnglish (UK)
BhutanEnglish (UK)
BoliviaSpanish (Mexico)English (UK)
BotswanaEnglish (UK)
BrazilPortuguese (Brazil)English (UK)
Brunei DarussalamEnglish (UK)
BulgariaEnglish (UK)
Burkina FasoEnglish (UK)French
CambodiaEnglish (UK)French
CanadaEnglish (Canada)French (Canada)
Cape VerdeEnglish (UK)
Cayman IslandsEnglish (UK)
ChadEnglish (UK)French, Arabic
ChileSpanish (Mexico)English (UK)
ChinaChinese (Simplified)English (UK)
ColombiaSpanish (Mexico)English (UK)
Costa RicaSpanish (Mexico)English (UK)
CroatiaCroatianEnglish (UK)
CyprusEnglish (UK)Greek, Turkish
Czech RepublicCzechEnglish (UK)
DenmarkEnglish (UK)Danish
DominicaEnglish (UK)
Dominican RepublicSpanish (Mexico)English (UK)
EcuadorSpanish (Mexico)English (UK)
EgyptArabicFrench, English (UK)
El SalvadorSpanish (Mexico)English (UK)
EstoniaEnglish (UK)
Federated States of MicronesiaEnglish (UK)
FijiEnglish (UK)
FinlandEnglish (UK)Finnish
FranceFrenchEnglish (UK)
GambiaEnglish (UK)
GermanyGermanEnglish (UK)
GhanaEnglish (UK)
GreeceGreekEnglish (UK)
GrenadaEnglish (UK)
GuatemalaSpanish (Mexico)English (UK)
Guinea-BissauEnglish (UK)French
GuyanaEnglish (UK)French
HondurasSpanish (Mexico)English (UK)
Hong KongChinese (Traditional)English (UK), Cantonese
HungaryHungarianEnglish (UK)
IcelandEnglish (UK)
IndiaHindiEnglish (UK)
IndonesiaIndonesianEnglish (UK)
IrelandEnglish (UK)
IsraelHebrewEnglish (UK)
ItalyItalianEnglish (UK)
JamaicaEnglish (UK)
JapanJapaneseEnglish (US)
JordanArabicEnglish (UK)
KazakhstanEnglish (UK)
KenyaEnglish (UK)
KuwaitArabicEnglish (UK)
KyrgyzstanEnglish (UK)
Lao People’s Democratic RepublicEnglish (UK)French
LatviaEnglish (UK)
lbaniaEnglish (UK)
LebanonArabicFrench, English (UK)
LiberiaEnglish (UK)
LithuaniaEnglish (UK)
LuxembourgEnglish (UK)French, German
MacauCantoneseEnglish (UK), Chinese (Traditional)
MadagascarEnglish (UK)French
MalawiEnglish (UK)
MalaysiaMalayEnglish (UK)
MaliEnglish (UK)French
MaltaEnglish (UK)
MauritaniaArabicFrench, English (UK)
MauritiusEnglish (UK)French
MexicoSpanish (Mexico)English (UK)
MoldovaEnglish (UK)
MongoliaEnglish (UK)
MontserratEnglish (UK)
MozambiqueEnglish (UK)
NamibiaEnglish (UK)
NepalEnglish (UK)
NetherlandsDutchEnglish (UK)
New ZealandEnglish (Australia)English (UK)
NicaraguaSpanish (Mexico)English (UK)
NigerEnglish (UK)French
NigeriaEnglish (UK)
North MacedoniaEnglish (UK)
NorwayNorwegianEnglish (UK)
OmanEnglish (UK)
PakistanEnglish (UK)
PalauEnglish (UK)
PanamaSpanish (Mexico)English (UK)
Papua New GuineaEnglish (UK)
ParaguaySpanish (Mexico)English (UK)
PeruSpanish (Mexico)English (UK)
PhilippinesEnglish (UK)
PolandPolishEnglish (UK)
PortugalPortuguese (Portugal)English (UK)
QatarEnglish (UK)
Republic Of KoreaKoreanEnglish (UK)
Republic of the CongoEnglish (UK)French
RomaniaRomanianEnglish (UK)
RussiaRussianEnglish (UK), Ukrainian
Saint LuciaEnglish (UK)
São Tomé and PríncipeEnglish (UK)
Saudi ArabiaArabicEnglish (UK)
SenegalEnglish (UK)French
SeychellesEnglish (UK)French
Sierra LeoneEnglish (UK)
SingaporeChinese (Simplified)English (UK)
SlovakiaSlovakEnglish (UK)
SloveniaEnglish (UK)
Solomon IslandsEnglish (UK)
South AfricaEnglish (UK)
SpainSpanish (Spain)English (U.K.), Catalan
Sri LankaEnglish (UK)
St. Kitts and NevisEnglish (UK)
St. Vincent and The GrenadinesEnglish (UK)
SurinameDutchEnglish (UK)
SwazilandEnglish (UK)
SwedenSwedishEnglish (UK)
SwitzerlandGermanEnglish (UK), French, Italian
TaiwanChinese (Traditional)English (UK)
TajikistanEnglish (UK)
ThailandThaiEnglish (UK)
Trinidad and TobagoEnglish (UK)French
TunisiaArabicFrench, English (UK)
TurkeyTurkishEnglish (UK), French
TurkmenistanEnglish (UK)
Turks and CaicosEnglish (UK)
UgandaEnglish (UK)
UkraineUkrainianRussian, English (UK)
United Arab EmiratesArabicEnglish (UK)
United Republic Of TanzaniaEnglish (UK)
UruguaySpanish (Mexico)English (UK)
UzbekistanEnglish (UK)
VenezuelaSpanish (Mexico)English (UK)
VietnamVietnameseEnglish (UK)
Virgin IslandsEnglish (UK)
YemenArabicEnglish (UK)
ZimbabweEnglish (UK)

Note: The chart has been sourced from Appfollow, Appradar, Phiture, MobileAction, and Sensor Tower.

10 guidelines for App Store cross-localization:

      1. Not all locales are indexed in all countries, so it is important to research which locales are indexed in the target country before utilizing cross-localization. Some localizations are exchangeable, meaning they can also be indexed in other countries. For example, if French (Canada) is not indexed in a particular country, but French (France) is, then the French (France) localization will be indexed in that country.
      2. Avoid repeating keywords from the primary localization in the secondary localization: Keywords should not be repeated between the primary and secondary localizations, as this will not result in additional keyword rankings.
      3. One exception to the rule against keyword duplication is if you want to use the same keyword in the title or subtitle for both localizations. In this case, using the same keyword in both the title and subtitle of one localization will not negatively impact your app’s ranking. However, suppose you use the same keyword in the title of one localization and the subtitle of another. In that case, it will be counted as if you only mentioned it in the subtitle, which carries less weight in terms of ranking. This also applies to the 100-character keyword field. It is generally best to avoid repeating the same keyword across different localizations, as you may unknowingly violate a keyword duplication rule.
      4. Use exchangeable localizations (if available) to expand the character space for metadata: If certain localizations are exchangeable, they can be used to expand the character space for metadata. For example, if French (Canada) is not open, but you have French (France), this localization will be indexed in French (Canada). Keep in mind that keywords and data do not cross between locales, so it is important to avoid repeating keywords from the primary localization in the secondary localization.
      5. Consider the target audience and include relevant keywords in the secondary localization: The secondary localization should be optimized for the target audience, not just for the purpose of expanding the character space for metadata. Include relevant keywords in the secondary localization that may be more relevant to the target audience or that your competitors are ranking for.
      6. Remember that keywords and data do not cross between locales: It is not possible to rank for keyword combinations that are separated by the two localizations. For example, if an app’s primary localization includes the keyword “yoga” and the secondary localization includes the keyword “meditation,” the app will not be ranked for the keyword combination “yoga meditation.” It is important to avoid repeating keywords from the primary localization in the secondary localization and instead includes other relevant keywords.
      7. In some cases, different dialects of the same language may be treated as separate localizations by app stores. For example, English (UK) and English (US) are considered separate localizations, so it is possible to include the same keywords in both localizations without facing duplication issues.
      8. If you use keywords that are spelled differently in different localizations, they will not be considered duplicates by the app store. For example, if you use the keyword “color” in an English localization and the keyword “colour” in a British English localization, they will not be considered duplicates.
      9. If you use keywords that have different meanings in different localizations, they will not be considered duplicates by the app store. For example, if you use the keyword “bank” in an English localization to refer to a financial institution and the keyword “bank” in a German localization to refer to the edge of a river, they will not be considered duplicates.
      10. Contrary to popular belief, you do not need to be a native speaker or have any knowledge in a particular language to localize your app’s listing on the App Store effectively. While it is certainly helpful to have a strong understanding of the language you are localizing for, many tools and resources are available, from Google Translate to spying on which keywords your competitors rank for using ASO software, that can assist with the translation process.

How cross-localization works in practice:

Here is a case study example to illustrate the benefit of cross-localization in app store optimization:

Imagine that you have developed a fitness app called “FitLife” released in the United States App Store. Your app has been doing well in the US, but you would like to expand the number of keywords you can include in your metadata to improve your app’s visibility and to rank even better in the U.S. One way to do this is through cross-localization.

You decide to utilize cross-localization by localizing your app in Spanish (Mexico). This allows you to add English keywords to your app’s Spanish (Mexico) localization, which will then count as English metadata for the US market. By adding these additional keywords, you are able to improve your app’s ranking in the US App Store and reach a wider audience of English-speaking users.

After implementing cross-localization for your app, you begin to see an increase in downloads and user engagement in the US market. Your app’s ranking in the US App Store improves, and you are able to reach a larger audience of English-speaking users in the U.S. Overall, cross-localization proves to be a valuable technique for expanding your app’s user base and increasing its visibility in the US market.

To adjust the localization metadata in App Store Connect:

  1. Go to the “My Apps” page in App Store Connect.
  2. Select the app you want to adjust the localization metadata for.
  3. Click on the “App Information” tab.
  4. Scroll down to the “Localization” section.
  5. Click on the language you want to adjust the metadata for.
  6. Edit the metadata fields (title, subtitle, and keyword field) as desired.
  7. Click “Save” to apply the changes.

If you don’t see the language you want to adjust the metadata for, you may need to add it by clicking the “Add Language” button in the “Localization” section. 

Get help localizing your App Store listing

If the thought of managing cross-localization for your app’s listing sounds like too much work, consider hiring Outrank Apps to handle it for you. Don’t miss out on the opportunity to expand your user base and boost your app’s success. Contact Outrank Apps to learn more about cross-localization services.

More App Store Optimization Content


Let's Talk About Your App Marketing