Cross Localization

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.

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.

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.

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.

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).

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.

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.

Words at the beginning of the Title get the highest priority. Use your most important keywords there.

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.

There is a list of free words that are automatically indexed for all apps.
For example, app, game, for, etc.

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.

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.

100%

Cross Localization

100%

Cross Localization

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

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.

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.

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

100%

Editor input

100%

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.

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

100%

Localization Providers Settings

100%

Localization Providers Settings

Provider connections and task priorities are configured separately in ASO.dev.

In Settings → Integrations, search for a provider and enter the connection fields shown on its card: API key, base URL, region, supported capabilities and default models, where applicable. The fields depend on the provider. Google Translate is available as a built-in translation option.

Then open the relevant task section:

• Translations: Provider — enable translators and arrange their fallback priority.
• AI: Provider — enable providers for text generation and analysis, with their own priority and models.
• Images: AI Model — enable image-generation providers and choose their image models.

A configured connection can serve more than one task. Enabling a provider for translations does not automatically enable it for text or image generation. Change keys and connection details in Integrations, and change task order in the corresponding provider section.

You can configure the translation provider of your choice (Google Translate, DeepL, Chat GPT, Claude AI) in the ASO.dev settings and also set translation exclusions.

Google Translate

Google Translate is available by default as a free translation provider in ASO.dev.

It is enabled in the default translation configuration. Keep it enabled in Translations: Provider if you want to use it as your main translator or a fallback.

DeepL, Chat GPT, Claude AI, DeepSeek, Gemini, OpenRouter

DeepL, OpenAI, Claude, DeepSeek, Gemini and OpenRouter provide alternative translation options with their own API keys, plans and limits.

DeepL is a dedicated translation integration. The AI providers can also serve text-generation tasks when enabled in AI: Provider. Compare translation quality on your own metadata, terminology and target languages.

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

In Translations: Provider, change priority by dragging active provider cards or using their move buttons.

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.

100%

Settings: Brand Names

100%

Settings: Brand Names

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 .

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.