About the main language
Unless it is a particularly localized product, generally speaking, the app developed by developers will consider multilingualism and going overseas, so it is best to consider the choice of the main language clearly from the beginning.
Personally, I prefer to choose American .
From experience (although I can’t say absolutely), the main language has an impact on the natural volume and vocabulary popularity of products on the App Store, that is to say, countries with the main language have more chances of natural display than non-main language countries ( especially in the early stages). I accidentally used mainland Chinese as the main language because I released a product, so that the natural volume in the early stage overseas was delayed.
Cross-regional keyword impact of multiple languages
Both the United States and the United Kingdom use English. Suppose we submit two languages, one in American English and one in British English, then we can naturally use two sets of keywords in the two regions.
Suppose there is a word called wind, and the keyword is only written in the United States, but not in the United Kingdom. Can the keyword wind form a search weight in the United Kingdom? Practice has proved that it is possible.
So some friends take advantage of the feature of the App Store to cover keywords in multiple languages. Is this approach effective?
In my experience, there is an effect on vocabulary coverage, but a very weak effect on vocabulary weight. Because if multilingual is set, then the vocabulary weight is still based on the high priority of keywords in the local area, and the coverage of keywords in other regions is only a supplement. If a product has a high degree of association with a certain word, but does not fill it in, but instead uses other words in order to compete for vocabulary coverage, the gain outweighs the gain.
Advantages of multilingual coverage
The biggest advantage of multilingual coverage is mainly reflected in the locality. For example, the three languages of Simplified Chinese in Mainland China, Traditional Chinese in Hong Kong, and Traditional Chinese in Taiwan are all Chinese, but they need to be differentiated for comparison in terms of keyword selection. Good to get ASO effect. Because Mandarin, Cantonese, and some vocabulary usages in Taiwan are very different. For example, "computer program" in mainland China is called "computer program" in Taiwan, and "software" is called "software" in Taiwan.
Another advantage is reflected in competing words and local hot words. For example, the word "chicken you are so beautiful" has more than 5,800 popularity on Master Cicada in mainland China, but it is meaningless in Hong Kong and Taiwan.
This also highlights that multilingual optimization needs to be combined with the understanding of local culture, and the requirements for operators are still relatively high.
Languages and regions worth localizing
Needless to say, English is a necessary main language.
For casual games, non-English-speaking regions such as Korean, French, and German have more opportunities to start, and the user value is also higher.
If you are not familiar with the area, it is more effective to look at the list of apps in the area through the data platform to see which app fits you well (in terms of type, function, and visual), and then put the app name Add your own key vocabulary (don't put it in the title, it's easy to review 4.3).
Then refer to the popular keywords of several competing products (available on the data platform), and choose the most popular ones to include in your keyword list, so that it is easy to fill up the keyword list.
Multilingual Audit Risks
This is very important to note, the more languages, the more titles, the easier it is to step on mine.
Especially non-English and Chinese languages, because of unfamiliarity, the probability of stepping on mines will greatly increase. Therefore, the selection of the title should be a little more cautious. It is best to search the corresponding vocabulary through the data platform to see if any vocabulary is actually a very popular product name. If it is, it means that you have stepped on the thunder. (Of course, risks and opportunities coexist. If you use this name and pass the review by Apple, and no one makes trouble, then maybe you can congratulate you, because you have successfully "scraped" a hot word).
Another risk lies in political, pornographic or cultural sensitive words, this topic can be a big one, depending on the policies of different regions. Of course, general products are not prone to this problem. Most of the time, basic common sense is enough to make a judgment. If you still get caught unfortunately, you can only say that you are unlucky. If you can prove or explain that you are not subjectively malicious, it can still be saved if something goes wrong.
Product multilingual and App Store multilingual are two different things
For example, you can use English inside the product, but the App Store releases in 8 languages. That's perfectly fine, and it's also the best value for money from an upfront cost perspective.
Because the workload of multilingual products is greater, from the product name, internal copywriting, if it is a content-based product, it also includes the text sent by the server, etc., the workload continues to explode with the increase in the number of languages.
However, the multilingual workload of the App Store is relatively small, only titles, subtitles, keywords and product descriptions are enough, but the returns they bring (reflected to the natural amount) are greater.
For most lightweight products, such as gadgets, casual games, etc., users don't mind it being in English. But the problem is that he may choose to search in the local language when searching, so he has no chance to see your product. This also highlights the fact that the App Store's multilingualism is more important than the product's multilingualism.
Therefore, developers should give priority to the App Store, even at the beginning of the product release, and then gradually make the product multilingual.
read more
How to effectively guide Apple’s review with note copywriting
How Developers Correctly Handle Apple App Infringement Disputes
Apple Developer Anti-Association Checklist for Opening New Accounts
Talk about what developers can do in the face of Apple's 14-day ban