Localization Analysis

• The public listing in each of 22 inspected languages, fetched from that language's home country, or from the audited storefront when the app is not sold there. Each language is read as one store locale: Spanish from Spain, Portuguese from Brazil, French from France. Chinese is read as both Simplified and Traditional.
• The title, subtitle and description on the App Store; the title, short description and description on Google Play.
• Traffic by country from App Store Connect or Google Play Console, when connected.
• On the App Store, how the category charts split by country.
• Screenshot captions, for measurement units that do not suit a market.

A 0 to 100 coverage score:

• A field counts as localized when its text differs from the default-language text. The title weighs most.
• A title kept the same in every language, as a brand name usually is, is left out of the score rather than counted as a gap, provided other fields are localized.
• Google Play's automatic translations count for half.
• No score when the default-language listing, or every other language, could not be read.

• One row per language with a gap, ranked by the strongest evidence available: the app's own traffic from that country, then the category's chart share there, then a default order.
• A screenshot row when captions use units that do not suit the market.

• Languages outside the inspected set. Every plan that includes the check inspects the same set. A plan's limit on target languages counts the languages a project manages, not the languages this check reads, so a target language outside the set is not checked.
• Other locales of an inspected language, such as Spanish (Mexico), Portuguese (Portugal) or French (Canada), and localizations a storefront indexes from another locale.
• Translation quality. A translated field counts whether the translation is good or not.
• The App Store keyword field, which is not public.
• Chart share by country for games.

Included on Basic, Pro, Elite and Enterprise. Compare plans