On this page
Keywords come firstTitle, subtitle and short descriptionScreenshots and videoTest with the stores' own toolsRatings, reviews and repliesParts of the Korean market teams overlookKeep the listing aliveA habit-tracking app takes off in English-speaking markets and adds Korean. The team translates the store description, keeps the English screenshots and waits. Korean installs stay flat. When a Korean marketer finally looks, the problem is visible in ten seconds: the title uses a word Korean users do not search for, the screenshots are English, and the first line of the description is a literal translation of an American joke.
App store optimisation (ASO) in a new language is not translation of the existing listing. It is a second listing, built for how people in that market search and decide. This post covers ASO for Korea: keywords, the title and short text, screenshots, testing, reviews, and the parts of the Korean app market that teams from abroad tend to overlook.
Keywords come first
The store listing is a search result before it is anything else. Build a Korean keyword set before writing a word of copy:
- List how Korean users describe the app's job, not its English category name. A Korean speaker should write this list without looking at the English.
- Type each candidate into the Korean store search on a phone and record the autocomplete suggestions.
- Compare loanwords with native Korean terms for the same idea; users may prefer either, depending on the category.
- Check spaced and unspaced forms of compound words, since Korean users type both.
- Look at the top results for each candidate. If they are a different kind of app, the word means something else to Korean users.
The same research method applies to web search and marketplaces; we describe it in keyword research per language for listings.
Title, subtitle and short description
These fields carry most of the search weight and most of the first impression, and they are short. Check each store's current character limits and how it counts Korean characters, then write to the limit rather than trimming a translation.
Brand plus Korean keyword
EN: HabitFlow: Daily Habit TrackerKorean title: "HabitFlow:" followed by the phrase Korean users actually search for this kind of appIllustrative. The brand stays; the descriptive half comes from keyword research in the Korean store, and it may not be the literal translation of "habit tracker".Benefit, not joke
EN: "Finally, a habit app that doesn't nag. Much."Korean short text: a plain benefit statement (small daily routines, streak visible at a glance)Illustrative. English irony rarely survives in a store snippet. Lead with the concrete benefit and keep humour for inside the app, written by a Korean writer.Screenshots and video
Most users decide from the screenshots, not the description. For Korea:
- Write captions in Korean from scratch. They are short ad headlines, not labels.
- Show the app with Korean UI if it has one, and with realistic Korean content: names, dates in Korean order, prices in won.
- Check typography. Korean text set in a font designed for Latin script falls back to a system font and can look mismatched; choose a Korean typeface for the captions.
- If the app UI is not yet in Korean, do not hide it. Users who install expecting Korean and find English leave fast, and say so in reviews.
Test with the stores' own tools
Both major stores let you test listings natively. Google Play Console supports store listing experiments for testing listing assets, and custom store listings for showing a different listing to users in chosen countries. App Store Connect offers product page optimization tests for alternative icons, screenshots and previews. Use them to test one Korean variant against another, for example two screenshot sets with different first captions. Testing Korean against English answers a different question. Decide the metric and the stop point before the test starts.
For a broader view of small experiments before full localization, see lean localization experiments.
Ratings, reviews and replies
Korean reviews are both a ranking signal and a source of free research. Read them in Korean, tag them by issue, and reply in Korean. A short reply that says the problem has been fixed in the latest version does more than an apology in English. Reviews that mention translation are the clearest signal there is that your Korean needs work; we describe how to mine them in churn signals from poor Korean localization.
Parts of the Korean market teams overlook
| Item | Why it matters | What to do |
|---|---|---|
| Domestic app store | Korea has a domestic Android marketplace, ONE store, alongside Google Play and the App Store | Check whether your category is active there and whether its developer guide fits your distribution plan |
| Game ratings | Korea's Game Rating and Administration Committee has participated in the IARC system since 2017 | For games, rating questionnaires on IARC storefronts can produce the Korean rating; still check the Korean rating text in the listing |
| Search outside the store | Many users research apps on web search, blogs and communities before installing | Make sure a Korean web page exists for the app; see Naver vs Google SEO |
| Consistency | The same feature named differently in the listing, the app and ads | Keep store terms in the termbase used for the app |
Keep the listing alive
A Korean listing translated once and left alone drifts out of date as the app changes. Add the Korean listing to the release checklist: every update with new screenshots or features gets Korean captions and release notes on the same day. Review the keyword set each quarter against Korean search suggestions and competitors. For apps in specific sectors, the regulatory and wording issues differ; see Korean translation for software and apps and game localization in the Korean market.
Korean listing not pulling installs?
We research Korean store keywords, write titles, short text and screenshot captions from scratch, and set up variants for your store tests. Get in touch →