App Store Cross-Localization Guide: Double Your Keywords
Cross-localization is a strategy that uses one localization (for example, AR for US) to index an app in other countries and regions where this localization is available but not primary.
This allows you to significantly expand your appโs reach and visibility without having to create unique content for every locale.
For each territory, the App Store defines a โprimaryโ language. However, each territory also has several โadditionalโ supported languages.
Useful Tips for Cross-Localization
Section titled โUseful Tips for Cross-LocalizationโUse only relevant keywords to avoid reduced conversion rates. Our goal is to get installs, not just impressions.
Do not add empty localizations.
You can fill any localization with another language; you do not have to use the localizationโs native language.
Maximizing Cross-Localization
Section titled โMaximizing Cross-LocalizationโThe primary localization of the app is currently indexed in all countries.
Increase your appโs reach in the US by up to 10% by selecting a non-target localization as the primary localization, but filling it with your target language (English).
For example: ๐จ๐ฆ English (Canada): EN_CA, ๐ซ๐ฎ Finnish: FI, ๐ธ๐ฐ Slovak: SK, and others.
For example, letโs take the US, which has 10 localizations:
Primary localization: ๐บ๐ธ English (US): EN_US
Also indexed as cross-localizations:
๐ฆ๐ช Arabic: AR
๐จ๐ณ Chinese (Simplified): ZH_HANS
๐ญ๐ฐ Chinese (Traditional): ZH_HANT
๐ซ๐ท French: FR
๐ฐ๐ท Korean: KO
๐ง๐ท Portuguese (Brazil): PT_BR
๐ท๐บ Russian: RU
๐ฒ๐ฝ Spanish (Mexico): ES_MX
๐ป๐ณ Vietnamese: VI
If your app uses a different primary localization by default, you get additional fields (Title, Subtitle, and Keywords) for the current App Store indexing in the US from that localization.
Do Not Duplicate Keywords
Section titled โDo Not Duplicate KeywordsโThe App Store does not boost indexing by repetition. Each word is counted only once-even if it appears in multiple fields (Title, Subtitle, Keywords) or in different localizations.
Do Not Duplicate Keywords Across Fields in Different Localizations
Section titled โDo Not Duplicate Keywords Across Fields in Different LocalizationsโIt is not recommended to use the same word in different metadata fields, such as Title, Subtitle, and Keywords, even across different localizations.
If you use the same word in the Title and in the Subtitle of another localization, it may be indexed with less weight (Subtitle has lower weight).
Separators
Section titled โSeparatorsโThe App Store does not index phrases as-is-it combines words from the Title, Subtitle, and Keywords fields.
Do not write long phrases like best photo editor for iPhone.
Instead, use as many unique words as possible, separated by commas: best,photo,editor,iPhone-this way you get more combinations: best photo, photo editor, editor for iPhone, etc.
Compound Words in the Title Are Indexed by Parts
Section titled โCompound Words in the Title Are Indexed by PartsโThe App Store automatically splits compound words in the title, even without spaces.
Example:AppStoreConnect is indexed as:app, store, connect, appstoreconnect
Use camelCase and PascalCase for maximum reach.
Word Order Affects Phrases
Section titled โWord Order Affects PhrasesโWords at the beginning of the Title get the highest priority. Use your most important keywords there.
Keyword Phrases Are Combined Only Within a Single Localization
Section titled โKeyword Phrases Are Combined Only Within a Single LocalizationโIn general, duplicating keywords is not recommended, but for the most important phrases, it is acceptable.
The App Store does not combine words between locales; all phrases are formed within a single localization. For example:
- EN-US Title:
Apple - EN-GB Subtitle:
Music
โ The phrase Apple Music will not be indexed.
Do not add words that are automatically indexed for all apps
Section titled โDo not add words that are automatically indexed for all appsโThere is a list of free words that are automatically indexed for all apps.
For example, app, game, for, etc.
Keywords Without Spaces
Section titled โKeywords Without SpacesโKeywords written without spaces are split by capital letters during ranking.
Works only for the Title field.
For example, HelloWorld in the app name is split by capital letters into the words hello and world during ranking.
Do not mention AI in your metadata for mainland China
Section titled โDo not mention AI in your metadata for mainland ChinaโIn mainland China, mentioning AI in metadata is prohibited unless you have certification.
If you want to use cross-localization in mainland China, do not mention AI in your metadata.
This may result in your app being removed from the App Store for this region.
If you are not publishing in mainland China, or you have received accreditation, you can use cross-localization with AI mentions.


Localization Overview
Section titled โLocalization OverviewโApp Store Language Usage Statistics
One of the fastest ways to scale your ASO results is by choosing languages that work across several countries - but in our cross-localization article weโll show you a few hacks to make it even more powerful.
Language & Primary Country | Primary | Secondary | Total |
|---|
Complete list of all variations:
Section titled โComplete list of all variations:โCross-localization Interface
Section titled โCross-localization Interfaceโ Sort countries
Save changes to App Store
Refresh information
Settings
Go to documentation
Country sorting options:
- By name
- By population
- By GDP (nominal) per capita
Creating a New Version
Section titled โCreating a New VersionโMetadata editing is available when the app status is โReady for Submissionโ in the App Store.
If you havenโt created a new app version after an update that can be edited, the interface will prompt you to Create a new app version.
Country Card
Section titled โCountry CardโEach country displays a card showing:
- Country code
- Country name
- Population
- GDP (nominal) per capita
- List of languages for cross-localization
Clicking a country card opens the localization editor with metadata.
Localization Card
Section titled โLocalization CardโEach localization displays a card showing:
- Localization code
- Localization name
- List of countries using this localization โ clicking a country opens its card
- 3 input fields affecting cross-localization:
- Title
- Subtitle
- Keywords
Editor Input
Section titled โEditor Inputโ

Each input field contains several buttons:
- Metadata Editor: Quick access to the metadata editor.
- Bulk Metadata Editor: Quick access to the bulk metadata editor.
- Translate: Translates text from the primary localization to the current language.
- Reverse Translate: Translates the current text in the input field back to the base language set in settings screen.
- Copy from Previous Version: Copies content from the last modified version.
- Show Differences: If the value differs from the last saved version, this button will show the difference.
- Add to tracking list: Only for fields that support keywords. Adds all keywords from the input field to your tracked keywords list.
Clear button: Clears all entered data in the input field.
For memberships with access to the ASO analysis: Indie, Pro and Marketing
For fields that affect search results in the App Store, such as Title, Subtitle, and Keywords, additional keyword analysis features are available:
- Keyword Breakdown: The entered text is automatically split into individual keywords.
- Display Metrics: Relevant metrics for each keyword are shown, including:
- Current App Rating: The current rating of your app for this keyword.
- Search Ads Popularity (SAP): The popularity of the keyword in Apple Search Ads-hovering over it shows the date of the last update.
- Difficulty: The competitiveness of the keyword.
- Total Number of Apps: The number of apps using this keyword.
- Suggestions: The number of suggestions for this keyword in the App Store.
- Keyword Management: Buttons to add or remove keywords from your keyword list.
- Edit Field: Options to remove or add this keyword directly in the current input field.
For memberships with access to the ASO analysis: Indie, Pro and Marketing
For the Keywords field, Keyword Recommendations are also available, based on:
- Current App Keywords: Keywords for which your app already has search queries.
- Userโs Keyword List: Keywords from your personalized keyword list.
- Competitor Apps: Keywords used by competitor apps.
Each input field has a dynamic border that reflects the current state, unless disabled in the page Settings:
- Blue: Indicates that the field has been changed.
- Red: Displays when there is no data in the field.
- Gray: Shows when the field has no changes and is filled.
Additionally, each input field displays the character count and maximum field length, helping to ensure compliance with App Store requirements.
Settings
Section titled โSettingsโChanges indicator
Section titled โChanges indicatorโBefore each input field, a vertical colored stripe is displayed as a status indicator.
By default, the indicators are visible, but they can be turned off using the โHide change indicatorsโ setting.
Color scheme:
- Red: field is not filled
- Blue: field has been changed
- Gray: field has not been changed
Localization Providers
Section titled โLocalization Providersโ

You can configure the translation provider of your choice (Google Translate, DeepL, Chat GPT, Claude AI) in the ASO.dev settings and also set stop words for translations.
Google Translate
Google Translate is available by default as a free translation provider in ASO.dev.
If you donโt have API keys for other providers, Google Translate will be used automatically.
DeepL, Chat GPT, Claude AI, DeepSeek
DeepL, Chat GPT, Claude AI, DeepSeek are paid translation providers that offer more accurate and high-quality translations compared to Google Translate.
These providers use advanced technologies and AI models to ensure a high level of translation accuracy.
To use these providers, you need to obtain an API key, enter it in the settings, and, if necessary, select a model or specify additional parameters.
How to Set the Priority of Translation Providers
You can change the priority of translation providers by dragging their cards in the list.
The order determines which provider will be used first when translating content.
Disabling a Translation Provider
To disable a specific translation provider, simply toggle the switch to the โOffโ position.
This provider will no longer be used for content translation.
You can also change the order of providers to adjust their priority.
Excluding Specific Keywords or Phrases from Translation
Section titled โExcluding Specific Keywords or Phrases from Translationโ

If you need to exclude certain words or phrases from translation, such as brand names, follow these steps:
- Enter the keyword or phrase you want to exclude from translation.
- After entering a word, press Enter or .
Comma-Separated List: You can enter multiple keywords or phrases, separating them with commas.
Case Sensitivity: The list is case-sensitive, so make sure to enter keywords exactly as they are written.
Excluded words or phrases will remain in their original language and will not be altered during translation.
This is especially useful for maintaining consistency with brand names, technical terms, and other important phrases.
Using both primary and additional languages in ASO, as well as optimizing keyword metadata, can increase your appโs visibility in the App Store.
Cross-localization provides an interactive table displaying metadata for different localizations, allowing you to assess their performance and optimize your app for various regions and languages.







