appeeky spec
← Learn

ASO · 7 min read

Localize without losing ranks

A new language is keyword research, not translation. Targets first, the spare keyword space a storefront already reads, then one measured launch.

People in each country search with their own words. A literal translation of an English keyword is often a term nobody types. Here is how to open a market so it can be measured.

Not translation

usmx · es-MXde · de-DE
sleep soundssonidos para dormireinschlafgeräusche
white noiseruido blancoweißes rauschen
rain soundssonidos de lluviaregengeräusche

Storefronts are countries; listing locales are languages. The spec keeps them apart: targets are per storefront, files are per locale, and coverage joins the two.

Start with spare room

The cheapest win is a locale a storefront already reads. The US App Store also indexes Spanish (Mexico), so the es-MX keyword field is 100 more characters for US searches. coverage says how much is free:

zsh
$ npx @appeeky/spec coverage --country us
4/5 covered · es-MX has 37 characters free

Targets first

Before writing copy for a new country, write down what it should be found for:

appeeky.spec.yaml
targets:
de: [einschlafgeräusche, weißes rauschen, regengeräusche]

Good sources: what competitors in that country use in their names and subtitles, store search suggestions, and suggest --country de with an Appeeky key. Ask a native speaker about the ones you are not sure of.

Write the file

appeeky/store/app-store/de-DE.yaml
name: Sleep Sounds: Einschlafen
subtitle: Regen, Ventilator & Rauschen
keywords: weißes,regengeräusche,baby,schlafhilfe,meer
  • Start with name, subtitle and keywords. Leave the description out until it is written properly; a missing field is not touched.
  • Keep the brand the same in every locale.
  • Google Play needs the title, short description and full description together for a new language.

Check, ship, measure

zsh
$ npx @appeeky/spec diff
de-DE new locale · name, subtitle, keywords
needs a version in Prepare for Submission

A new App Store locale ships with a version. Push with a note that names the market and the bet: push --note "Launch de-DE: einschlafgeräusche, weißes rauschen". On day 7, verify checks the German targets like any other.

Mistakes to avoid

  • Machine-translating the English keyword field

    Words people do not search for, in a field that only has 100 characters.

  • Copying the English subtitle everywhere

    The subtitle is the second most important field. Write it per market.

  • Ten locales at once, with no targets

    Nothing can be measured, so nothing can be learned.

  • Another app's brand as a keyword

    Against the store guidelines, and gets metadata rejected.

✓ One market, five targets, one push, measured: then the next.