ASO tool · 58 storefronts
Localization Audit
What this checks
Each of 57 storefronts is looked up and its title and description compared against the US listing. A storefront counts as localized when EITHER differs — some apps keep one product name worldwide and translate everything else. Identical on both means Apple is falling back: nothing localized was submitted for that storefront.
About this tool
Which storefronts are reading your English listing?
An app can be sold in 175 countries and still show the same English name and description in every one of them. This page checks each storefront and tells you which ones have a genuinely localized listing and which are serving your original text.
It is the diagnosis half of localization. The priority page ranks which of those gaps is worth closing first, and the metadata generator drafts the replacement copy.
How it works
- 1Pick an app. The audit fans out across the scan storefronts, eight requests at a time.
- 2Each storefront’s title and description are compared against the US listing.
- 3A storefront counts as localized when EITHER its title or its description differs. The test is an OR on purpose: some apps keep an identical product name worldwide while translating everything else.
- 4The table names which half differs — title, description, or both — because a translated description under an English title is the common real shape, and Apple indexes the title separately.
- 5Rows that come back identical link straight through to the localized metadata writer for that language.
What it cannot tell you
- It measures the App Store LISTING, not the app. A binary can support twenty languages and still show an English listing everywhere, which is a different problem — the language coverage tool measures that side.
- It cannot judge translation quality. A storefront that differs from the US is localized; whether the copy reads well to a native speaker is not something a string comparison can answer.
- A storefront whose lookup failed is reported as unknown and offered a retry — never as unlocalized. It is kept separate from "not sold here", which is Apple answering that there is no listing in that storefront: one is a hole in the measurement, the other is a finding.
- It cannot say what localizing is worth. Apple publishes no ranking factor for it and no per-storefront conversion data is public, so nothing here estimates installs, ranking or lift.
Questions
Do I need to translate my app to localize the listing?
No. The App Store listing — name, subtitle, keyword field, description, screenshots — is localized separately from the app binary in App Store Connect. Many developers translate the listing first because it is far cheaper than translating the product.
Which language should I do first?
Run the localization priority tool. It ranks storefronts where you already have ratings but no translated listing, so you start where users have already found you.
Does localizing the listing improve App Store search ranking?
Apple indexes your name, subtitle and keyword field per localization, so a localized listing gives Apple terms to index in that language that it did not have before. What that is worth in traffic depends on the market and nobody publishes the figure.
Written up on the blog
- How many languages your app declares, and why counting them is harder than it looksThe App Store's language field repeats one code, treats empty as unknown, and describes the binary rather than your listing. Three traps in a number that looks trivial.
- A translated keyword field is why your localized listing ranks for nothingApple supports 50 App Store localizations and measures the keyword field in bytes. Localizing a listing is a different job from translating it, and the keyword field is where the difference shows.
Localization & reach
Or browse every free App Store optimization tool.
Paid tools do this too. App localization tools, compared — 5 of them, described the same way and in alphabetical order.