Website localization
A localization service quotes you per word, per market, per round of review. Proxylang is the tool underneath that work: it localizes your existing site into 68+ languages, and hands you the controls for everything a machine should not decide on its own.
Free for your first 2,000 words. No card, no sales call.
Localization is not one job. These are its parts, split by who should be doing each one.
| Part | Handled for you | Under your control |
|---|---|---|
| Page text | Every visible string is translated with the whole page as context, so a word is rendered the way its sentence uses it. | Any string can be corrected in the dashboard, and your version is what visitors see from then on. |
| Brand and product terms | Terms you pin are carried through untouched in every language, including inside longer sentences. | You build the glossary. It is the single most useful thing to set up before launching a language. |
| Metadata and alt text | Meta titles, meta descriptions, link titles, form labels and image alt text are all translated, not just the body copy. | Override any translated title or description per language when the automatic one is not the one you want to rank with. |
| Right-to-left languages | Arabic, Hebrew, Persian and Urdu are laid out right-to-left rather than having their text swapped inside a left-to-right layout. | Check your own custom components. Anything positioned with fixed pixel offsets is worth a look after you switch a language on. |
| Search visibility per market | Each language gets its own indexable URL, matching hreflang tags, and its own entries in the sitemap, from the Start plan. | Submit the sitemap in each market’s search console. Naver in particular needs a guided one-time setup. |
| Text inside images | Alt text is translated for every image automatically. | Text painted into the image itself is translated for the images you opt in, one attribute per image, and cached per language after that. |
Four things a localization agency sells that no translation layer should claim, ours included.
Numbers in your page are preserved exactly, not recalculated. If you want to sell in local currency, that belongs in your store or billing system, and Proxylang will translate whatever it outputs.
German runs roughly a third longer than English and Japanese runs shorter. We do not redesign your components to absorb that, and we do not commission market-specific photography. Both are design work.
Terms, privacy notices and anything with regulatory weight are translated accurately, but an accurate translation is not a legal review for that market. Have a person sign those off.
The translation is good enough to publish and it is consistent. It is not a local copywriter rewriting your positioning for that culture. If a market matters enough, hire one and paste their wording in as an override.
The practical shape most teams land on: run every language through the tool, watch which markets actually send traffic, then spend human money on the two that do. See how each language is performing on the multilingual SEO side, and how the pages reach search engines in the first place on the translation proxy page.
Website localization is adapting a site so it works for a market, not only translating the words on it. It covers the copy, the metadata search engines read, the reading direction for languages such as Arabic and Hebrew, the terms you never want changed, and giving each language its own address so it can be found. Translation is one part of localization; a localized site is one a visitor in that market never has to work around.