da-eun.
Da-eun · Website Localization

Translated —
and still
foreign?

A page can be perfectly translated and still read as foreign to local visitors.
That gap is design, not words — I fix it.

I localize the design, not the text. Your copy stays yours. I rebuild the page so it reads native in Korea, Japan, or China — typography, density, and the trust cues local buyers look for.

01
Design, not translation
Your words stay yours — in any language. I rebuild how the page looks and reads, not what it says.
02
Evidence, not credential
Built to conventions drawn from top-performing real local sites, then proven with the before/after below.
03
Korea · Japan · China
CJK markets, where typography and layout conventions differ enough that design localization actually moves trust.
The gap

Translation isn't localization

A local font that's just inherited from your English one isn't a small thing — it's a signature. It means no one who reads your customers' language ever touched the site. The same page, three states:

01 · ORIGINAL

English

Clean, considered, built for a Western audience.

02 · JUST TRANSLATED

Local text, Western design

The type is inherited, the layout has none of the trust cues local buyers expect — what "just translate it" actually ships.

03 · LOCALIZED

Built for the market

Rebuilt to local conventions — native typography, trust up front, the right density, decisive CTAs. The content never changes; only the design does.

Before / After demos

See it, don't take my word

The same page — identical content — shown as English original, "just translated," and localized for each market. Evidence you can check, not a credential you can't.

Demo brand is fictional, for illustration.

How it works

Three steps

01

Audit

Map where the current design reads foreign — type, spacing, hierarchy, trust signals — against verified local patterns.

02

Design localization

Rework layout, typography, density, and trust elements to local convention. You supply the final copy.

03

Build & handoff

Implemented front-end plus an annotated before/after comparison. One revision round included.

What you provide
  • — Your live URL (or files/access if not live)
  • — Target market: Korea, Japan, or China
  • — Final copy in the target language — yours or your translator's
  • — Brand assets: logo, fonts, colors, any brand guide
Pricing

Per page, no surprises

Launch pricing — 30% off while the first reviews land. Same per-page rate for Korea, Japan, or China.

1 page

$99 $149
4 days · 1 revision

One page rebuilt to read native.

3 pages

$279 $399
7 days · 1 revision

Three pages, same site — bundle rate.

5 pages

$399 $599
10 days · 1 revision

Five pages — best per-page rate.

Tiers cover static marketing pages (landing, about, product). Interactive pages — checkout, multi-step forms — are quoted separately. Additional page or another market version: +$99 (launch) each.

FAQ

Questions

Do you translate my text?

No. I localize the design — layout, typography, density, trust signals. You or your translator provide the copy.

How is this different from a translator?

A translator makes the words correct; the page can still look imported. I fix how it is spaced, sized, and structured for local eyes.

Japanese or Chinese as well?

Yes — same method, same per-page rate. Korean is my lead specialty; Japanese and Chinese (Simplified or Traditional) use the same approach. For mainland China I also rebuild resources that do not load there (e.g., self-hosted fonts).

What about checkout or multi-step forms?

Those are interactive, not a static page — message me for a custom quote.

Do you build it or just hand off design files?

I implement the front-end and hand off the working page (with source) after payment; design files included. One revision round.

Contact

Tell me your URL and target market — I'll scope the gaps with you.