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
| us | mx · es-MX | de · de-DE |
|---|---|---|
| sleep sounds | sonidos para dormir | einschlafgeräusche |
| white noise | ruido blanco | weißes rauschen |
| rain sounds | sonidos de lluvia | regengerä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:
$ npx @appeeky/spec coverage --country us4/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:
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
name: Sleep Sounds: Einschlafensubtitle: Regen, Ventilator & Rauschenkeywords: 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
$ npx @appeeky/spec diffde-DE new locale · name, subtitle, keywordsneeds 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.