38 App Store languages

Localized Metadata

The localization audit tells you which storefronts never got a translated listing. This writes the fields for one of them — localized, which for the keyword field means the terms that market actually searches, not the translation of yours.

Translating is not localizing

The name, subtitle and description can survive a good translation. The keyword field cannot: it has to carry the words people in that market type into search, and those are frequently not what your English keywords translate to. A literally translated keyword field is the most common reason a localized listing ranks for nothing.

Start with the localization audit to see which storefronts are missing a listing, then come back and write one.

Draft your listing for another App Store language

The localization audit produces a diagnosis and no deliverable. This is the other half: pick a storefront language and it drafts the name, subtitle, keyword field, promotional text and description, each editable with its own character count.

It is a localizer rather than a translator, and the keyword field is why. That field has to carry the words that market actually types into App Store search, which are frequently not what your English keywords translate to.

How it works

  1. 1Pick an app and one of the 38 App Store localizations.
  2. 2One AI call returns every field plus translator notes explaining the judgement calls it made.
  3. 3Each field is validated against Apple’s cap, and the keyword field against its mechanics — no space after commas, no word already used in the name or subtitle, no other company’s brand.
  4. 4Every field is editable, and renders with automatic text direction so Arabic and Hebrew drafts do not come out backwards.

What it cannot tell you

  • Nothing here has seen search volume in the target language. Generated keywords are candidates, and the rank checker is where you find out whether they are worth keeping.
  • It validates character caps and keyword mechanics. Whether the copy is good in the target language is exactly what a native reviewer is for, which is why that banner does not dismiss.
  • A literally translated keyword field is the most common reason a localized listing ranks for nothing — read the translator notes rather than skipping them.

Frequently asked questions

How many languages does the App Store support?

Apple offers 38 listing localizations. This drafts for any of them, and the localization priority tool ranks which one is worth doing first.

Can I just translate my English keywords?

That is the most common way a localized listing ends up ranking for nothing. People search in their own idiom, not in a translation of yours.

Do I still need a native speaker?

Yes. This gets you a structured first draft that fits Apple’s caps. Whether it reads naturally is a judgement no character count can make.