All tutorials

Store ListingLesson 19 of 502:56

Localization in Appalize: Translate, Then Check Search

Translating your App Store listing is not the same as localizing it. A translated keyword that nobody types in that country wastes your keyword field. In this tutorial, Appi localizes a real, live kids app, Toddly, in the Appalize ASO Editor: Translate All as a draft, cross-localization for the extra languages a storefront accepts, a side-by-side review in Split View, export for a translator, and a keyword check in Keyword Suggest.

Watch on YouTube

What you'll learn

  • Every locale has its own name (30 characters), subtitle (30) and keyword field (100). An empty locale gives Apple nothing to index in that language.
  • Translate All translates into every language already in your listing, so add the languages you want first. The result is a draft. Nothing goes live until you push it to App Store Connect.
  • Each storefront reads more than one language. The US store also accepts Spanish (Mexico). We at Appalize treat those extra languages as searchable there. Apple doesn't document that, so re-check it now and then, and never repeat a word between them.
  • Translations often run longer. Keep your brand name and localize only the words after it.
  • Before you ship, check translated keywords in the target country. Popularity is an estimate, not a count.

In this video

  1. Translated isn't searched
  2. Your locales and field limits
  3. Translate All: a draft, not a publish
  4. Cross-localization: extra languages per storefront
  5. Review each locale in Split View
  6. Export for a translator (and the free way)
  7. Check translated keywords in Keyword Suggest
  8. Recap and next: ASO Report

Open in Appalize

The screens this lesson walks through (sign-in required).

Transcript

The narration, with timestamps. Select a time to jump there.

Translated isn't searched

0:00 You translated your keywords, and nobody searches for them. 0:03 Let me localize a real kids app, Toddly, from one screen, and check every word before it ships. 0:09 If your listing only speaks English, start here. 0:12 First, let's see what Toddly already has.

Your locales and field limits

0:15 Look at the Localizations panel. 0:17 Each row is one language of your listing. 0:20 Toddly already has a few filled in, like English U.S., German, French and Japanese. 0:26 The rest are empty. 0:27 Here's the rule. 0:28 Every locale has its own name, thirty characters. 0:32 Its own subtitle, thirty. 0:34 And its own keyword field, one hundred. 0:37 An empty locale gives Apple nothing to index in that language. 0:41 Let's fill the empty ones.

Translate All: a draft, not a publish

0:42 Press Translate All. 0:44 It translates into every language already in your listing, so add the languages you want first. 0:49 The empty fields fill in, each in its own script, umlauts included. 0:54 Nothing falls back to English. 0:56 And nothing is live yet. 0:57 This is a draft. 0:59 Pushing it to App Store Connect is a separate step. 1:02 Common mistake: calling the draft finished. 1:05 A translation is a starting point. 1:07 So which extra languages does the US storefront read?

Cross-localization: extra languages per storefront

1:10 Each storefront reads more than one language. 1:13 Apple lists the extras. 1:15 The US store, for example, also accepts Spanish for Mexico. 1:18 We at Appalize treat those extras as searchable there. 1:22 Apple doesn't document that, so re-check it now and then. 1:25 That Spanish keyword field can work for US searches too. 1:29 So never repeat a word between them. 1:31 Open Cross-Localization. 1:32 It flags each repeat and shows its source locale. 1:36 Now let's check every language by eye.

Review each locale in Split View

1:38 Open Split View. 1:39 English on the left, German on the right. 1:42 Watch the counters. 1:43 Translations often run longer, and a name over thirty characters won't fit. 1:48 Appi tip: Toddly is Toddly in every language. 1:52 Keep the brand. 1:53 Localize only the words after it. 1:55 If you work with a translator, export the file.

Export for a translator (and the free way)

1:58 Choose JSON or CSV. 2:01 Every locale lands in one file. 2:03 Your translator edits it, and Import brings it back into the draft. 2:08 No tool at all? 2:09 In App Store Connect, add each language by hand, then fill its fields. 2:14 One question is left. 2:16 Does anyone search these words?

Check translated keywords in Keyword Suggest

2:17 Open Keyword Suggest. 2:19 Set the country to Germany. 2:21 Type one of the translated keywords from your German draft. 2:24 The popularity score is an estimate, not a count. 2:28 If it's low, look at the suggestions. 2:30 They show what people there actually type. 2:33 Pick the local term that fits your app best. 2:36 Swap it into the German keyword field. 2:38 Translated isn't searched until you check.

Recap and next: ASO Report

2:40 If you only remember one thing: translate first, then check every keyword. 2:45 There's a free plan, no card needed. 2:48 Next up, the ASO Report scores your whole listing in one pass. 2:52 Find it at appalize.com/tutorials.

Try it on your own app

Every tutorial shows a real Appalize screen. Sign up free and follow along with your own app.

Start free