Translate Website to Korean: Honorifics & Microcopy

If your brief says “translate the website to Korean,” stop treating Hangul as a font problem first. Korean on the web is an honorifics problem: a polished dashboard that mixes casual 반말 with stiff 합니다체 in the same checkout flow does not look bilingual—it looks careless.

This article is a launch guide for a Korean (ko) website version: locale choice, Hangul typography, crawlable URLs, checkout QA, MTPE vs human review, SEO pitfalls, and a checklist you can actually run.

What does it take to translate a website to Korean beyond swapping strings?

Beyond CMS fields, you need a speech-level policy that stays consistent across product UI, chat, and email; fonts that keep Hangul syllable blocks legible at caption size; particles and spacing that a native reviewer can catch in context; name and phone fields that match Korean expectations; and a real Korean URL whose body is actually Korean—not a translated chrome around English copy.

Questions this guide answers

• What does it take to translate a website to Korean beyond swapping strings?
• Which Korean locale or regional variants should you choose?
• What script, typography, and layout issues are unique to Korean?
• How should URLs, hreflang, and indexing work for a Korean site version?
• What onboarding and checkout nuances matter in Korean?
• Should you use AI translation, MTPE, or human review for Korean?
• What SEO mistakes specifically hurt Korean pages?
• How do you launch and measure a Korean website version?

Quick answer: translate your website to Korean the right way

A durable Korean launch looks like this:

1. Freeze honorific speech levels before anyone opens a file. Product, transactional email, and in-app chat must share one posture—or you document the few places they may differ.
2. Ship ko (often ko-KR) as its own crawlable URL—not a cookie-only switch.
3. Prototype nav, cards, checkout, and emails with real Hangul copy so clipped syllable blocks, cramped particles, and overflow show up before launch.
4. Research queries the way people type them—Korean phrasing is not a word-for-word map from English—then write on-page titles in natural Korean.
5. Add reciprocal hreflang, same-language canonicals, and sitemaps before you scale.
6. Put product nouns and speech-level rules in a glossary so MTPE cannot silently flip 해요체 to 합니다체 mid-journey.

CSA Research’s survey of 8,709 consumers in 29 countries found 76% prefer buying with information in their own language and 40% will never buy from websites in other languages. That still holds when some Korean speakers also read English: checkout, invoices, and support are where an English-only journey loses the sale. Google’s helpful-content guidance favors people-first pages; a Korean nav around English body copy is a weak locale. For market-versus-language strategy, read how international SEO differs from multilingual SEO.

Choose the right Korean locale

Most teams should ship ko with a Korea-oriented ko-KR URL if that is the first commercial market. That is a reasonable first release. It is not a license to mix North American Korean diaspora slang, overly literary written Korean, and chat-speak in one file and call it “the Korean locale.”

Korean is one language with well-known speech levels. You can still architect one ko message file on day one. You should not pretend a B2B 합니다체 glossary automatically sounds right for a consumer mobile checkout that wants polite 해요체. Put the audience and honorific policy in the brief: formal written UI vs everyday product voice, and whether support chat may be warmer than legal pages.

Overseas Korean readers exist, but currency, address formats, and legal pages still follow the market you sell in. A single ko file can be the right first ship if you are not localizing contracts yet—just do not treat English-mix K-community copy as the source of truth for a Korea storefront.

Also decide how you will handle names, addresses, and phone numbers. Korean names typically put the family name first; forms that force Western given-name / family-name order, reject Hangul in name fields, or expect US-style 10-digit phones will fail after the strings look “translated.” Korean mobile numbers commonly start with 010; postal addresses expect a different field order than US forms. Document those rules next to the locale code, not in a translator footnote.

Korean script, typography, and layout nuances

Korean uses Hangul. Syllable blocks must stay crisp in UI, email, and PDFs. A font stack that only tested Latin will look acceptable at 16px and fall apart in badges, table cells, and 12px helper text—where 받침 and vowels mash into noise. Prototype captions and dense settings screens with production fonts, not a designer’s laptop fallback.

Spacing is part of meaning. Korean does not put spaces between every word the way English does, but particle choice (은/는, 이/가, 을/를, 에/에서) changes what a sentence highlights. Machine translation that drops a space, glues a particle to the wrong noun, or picks the wrong topic marker feels especially unnatural—native readers notice before they can explain why. Reviewers need screenshots plus string IDs, not a spreadsheet of isolated stems.

Layout rules that prevent launch-week screenshots:

• Prototype key screens with real Korean copy—including long compound nouns in settings and legal lines.
• Check line-height so syllable blocks have vertical room; Hangul looks tighter than Latin at the same px size.
• Allow buttons to wrap; do not shrink Hangul to keep a one-line English CTA.
• Ship production fonts with Hangul coverage in UI, email, and PDFs (including CJK punctuation if you mix Chinese product names).
• Watch card titles, badges, and table headers—these are where clipped blocks show first.

Dates and numbers are part of the layout contract. Korea typically expects year-month-day in many official contexts, a period or hyphen date style that matches the market, and currency formatting for KRW when you actually sell in Korea. Sorting Korean lists as if they were English ASCII is not a collation policy.

Train reviewers to protect payment clarity while giving the homepage enough room to sound like Korean, not translated English.

Crawlable URLs, hreflang, and indexing

Google recommends different crawlable URLs for each language or region version rather than cookies or browser language alone. Google determines page language primarily from visible content—so a translated nav around English body copy is a weak Korean version. Give Korean its own folder or host pattern (/ko/, /ko-kr/) and keep that pattern consistent across templates, analytics, and internal links.

Hreflang annotations must be reciprocal across the alternate set you declare. Each locale URL should carry a clear canonical that prefers the same-language preferred URL when duplicates exist. Do not canonical a Korean page to its English equivalent.

Bing Webmaster Guidelines emphasize crawlable, useful content and clear site structure across markets. Build once for shared foundations, then monitor Google Search Console and Bing Webmaster Tools where you operate both. Google advises against automatically redirecting users based on assumed language or location; offer a visible selector that links to the Korean URL instead. IP-guessing “Korea → /ko” traps travelers, VPNs, and crawlers.

URL policy and on-page policy can differ: you may use Latin slugs for operational reasons, but titles, H1s, and body copy should be Korean. Mixing romanized Korean titles with Hangul body, or publishing two competing Korean URLs without a canonical, hurts both readers and indexing. If you fold slugs, redirect consistently.

Onboarding, trust, and checkout in the target language

Korean trust pages do more work than a translated feature list. Sites that sell to Korea typically need privacy, terms, and (where relevant) payment and after-sales copy that read as real pages, not leftover English templates. That is not a ranking tactic; it is what users look for when they decide whether a checkout is legitimate. Treat those pages as first-class localization.

Honorific consistency is a conversion issue. If the homepage uses polite 해요체, the invoice uses 합니다체, and the chatbot drops into 반말, users do not think “flexible brand”—they think the product was assembled from three vendors. Freeze the policy, then audit email, SMS, and in-app chat against it.

Practical Korean conversion checks:

• Homepage, ads, and product UI use the same speech level.
• Forms accept Hangul for names and addresses, or they explain why a Latin field is required (passport names, international shipping).
• Family-name-first display matches how you store and greet users.
• Phone fields accept Korean mobile formats; country code handling does not strip leading zeros incorrectly.
• Cookie and consent strings are reviewed in the actual banner—these run long and wrap badly in Hangul.
• Pricing, invoices, and currency language match the market you claim to serve.
• Support macros and transactional email keep the same honorifics as the product.
• Error messages name the fix rather than a vague polite apology that hides the next step.

You do not need every blog post on day one. You do need homepage and product explanation, authentication, pricing, checkout/billing, privacy basics, support entry points, and the legal pages your market expects.

AI, MTPE, and human review for this language

Should you use AI translation, MTPE, or human review for Korean? Use risk to choose the workflow—not tool branding:

• Raw machine translation: fine for internal drafts only. Models flip speech levels, drop particles, and produce textbook Korean on consumer screens.
• MTPE (machine translation + post-editing): a solid default for many product and support pages when the glossary locks product nouns and honorifics.
• Human translation / brand editing: homepage, pricing, campaigns, cookie/consent, and any legal-adjacent page.

A practical review loop for Korean:

1. MTPE draft against the glossary (speech level and product nouns locked).
2. Brand editor pass on homepage, pricing, and key landing pages.
3. Product linguist pass on errors, billing, and dynamic UI—especially particles, spacing, and buttons.
4. Staging QA in Korean at mobile widths, including email and PDF Hangul renders.
5. Add a publishing check that flags mixed honorifics or suspiciously English-heavy bodies on ko URLs.

People-first helpful content expectations apply in every language. Low-quality machine-only Korean pages can look complete in a CMS while still failing users and search quality bars. Particle mistakes stand out immediately; do not ship empty states and errors without a native pass.

Korean-specific SEO pitfalls

Korean searchers look for language they can read. Translating English head terms word-by-word misses how people actually search. Do Korean keyword research, then write titles and H1s that sound like Korean results pages—not calques of your English metadata.

Localize titles, meta descriptions, and headings per Korean URL. Do not reuse one English metadata set across locales.

Mistakes that specifically hurt Korean pages:

1. Honorific drift across product, email, and chat.
2. Boilerplate-only translation — chrome Korean, body still English.
3. Illegible Hangul at small sizes in production fonts, email, or PDFs.
4. Particle and spacing errors that make “correct” strings feel off.
5. Cookie-only language switches that hide the Korean URL from crawlers.
6. Broken hreflang (missing return links).
7. Automatic geo redirects that trap users and bots.
8. Thin MT-only locales that fail helpful-content expectations.
9. English-calque titles that ignore native query phrasing.

Fix honorifics, fonts, and architecture before you scale content volume. Tooling should enforce the process—not invent ranking promises.

Launch checklist

Use this checklist when you are ready to ship Korean:

• Locale matrix approved (ko / ko-KR) with honorific policy documented
• Crawlable Korean URL pattern chosen and shared with engineering
• Primary screens prototyped with real Hangul copy (nav, cookies, tables, checkout)
• Priority templates translated with reviewed main content—not chrome only
• Titles, descriptions, and Open Graph localized per Korean URL
• Hangul glyph coverage verified in UI, email, and PDFs at small sizes
• Line-height and truncation checked on mobile cards and buttons
• Empty states and errors reviewed by a native speaker (particles included)
• Name, address, and phone field rules checked against Korean expectations
• Dates, numbers, and KRW formatting checked where you sell in Korea
• Privacy / terms pages reviewed as first-class content
• Language selector links to crawlable alternates (no forced redirect)
• Canonical policy verified per locale (same-language preferred URL)
• Reciprocal hreflang generated
• XML sitemaps list Korean URLs
• Glossary and review workflow live for ongoing English source updates
• Honorific-consistency check enabled across product, chat, and email
• Search Console / Bing coverage checks scheduled for the Korean URLs

Where GlotEO fits

Korean is a strong fit for translation memory: product nouns recur, and they must not change speech level in the next English drop. Glossary and memory in the website localization platform keep honorifics, particles, and feature names stable while layout-tested copy ships. Pair that with multilingual SEO tooling so Korean URLs, hreflang, and metadata stay reviewable as you expand. Compare GlotEO pricing and plans when you scope the first ko release, or start from a broader website translation workflow if you are still choosing languages.

Explore GlotEO website localization when JSON dictionaries and unmarked MT drafts are no longer a safe way to ship ko.