Website Localization Services: What a New-Market Launch Really Involves

· 8 min read
Paper cut-out illustration of a polished storefront facade held up from behind by beams and supports, standing for the unseen work behind a localized website.
On this pageFive layers, only one of them textLocal search: tell search engines which page is for whomTrust signals that do not translatePayments and formsLegal pages: localize, do not just translateMonth two: keeping the local site currentWhat to ask a website localization providerLaunch checklistIn brief

Most website localization services are bought as a translation job: export the pages, translate them, publish them under a new folder. The site goes live, the copy reads well, and the new market still underperforms. The reason is usually outside the text: search engines showing the wrong version, a checkout that offers the wrong payment options, legal pages copied from headquarters, and a local version that stops being updated after the first month.

This guide is for the teams that end up owning a localized corporate website: marketing and web teams, localization managers, legal and privacy teams, and the product or e-commerce owners who run checkout. It covers what a full launch involves and what to ask a provider before the work starts.

Five layers, only one of them text

A localized site has to work on five levels at once. Translation is the most visible one and rarely the one that fails.

LayerWhat it coversTypical owner
ContentPage text, metadata, image text, forms, error messages, emails the site sendsMarketing, localization
SearchURL structure, hreflang, local keyword research, sitemapsWeb or SEO team
TrustLocal contact details, prices in local currency, formats, references and proof that fit the marketMarketing, sales
TransactionsPayment methods, address and phone fields, tax and delivery informationE-commerce, product
LegalPrivacy notice, cookie information, terms, imprint or provider details, consumer informationLegal, privacy

A useful provider asks about all five during scoping, even if your team keeps some of them in-house. If the quote only counts words, the other four layers have no owner yet.

Search problems are the most common reason a well-translated site gets no traffic. Google's guidance on multilingual sites settles several questions that teams often argue about:

  • Use separate URLs for each language version. Google recommends different URLs per language rather than switching content with cookies or browser settings. Country domains, subdomains and subdirectories all work; URL parameters such as ?lang= are marked as not recommended.
  • Visible text decides the language. Google says it uses the visible content of the page to determine its language, not the lang attribute or the URL. A page with translated navigation and an untranslated body is, for search purposes, still an English page. Google also notes that translating only the boilerplate while the bulk of the content stays in one language can create a bad experience when the same content appears several times in results.
  • Connect the versions with hreflang. Hreflang annotations can go in the HTML head, in HTTP headers, or in an XML sitemap. Each version must list itself and every other version; if two pages do not point to each other, the annotations can be ignored. An x-default entry tells Google which page to show users who match none of your versions, typically a country or language selector.
  • Do not guess the visitor's language. Google advises against automatic redirects based on what you think a user's language is, and against using IP analysis to adapt content. Offer a visible selector and links between language versions instead.

Then do keyword research in each market, not keyword translation. The phrase people type for your product category is often not the dictionary equivalent of your English term. Our piece on why multilingual websites lose rankings after launch goes through URL structures, canonical tags and hreflang errors in more depth.

The canonical trap. When a CMS template copies the main site's canonical tag onto every local page, each translated page tells search engines that the original is the real version. Check canonicals on a sample of local pages before launch, and again after every template change.

Trust signals that do not translate

Visitors decide quickly whether a company is real and reachable in their market. The signals that persuade them are mostly not sentences:

  • A contact route that works in that market: local phone format, business hours in the local time zone, a support address someone actually answers in that language.
  • Prices in local currency, with tax treatment stated the way local buyers expect, and dates, numbers and units in local formats.
  • Proof that fits: case studies, certifications and references that mean something to local buyers. A logo wall of companies nobody in the market knows does little.
  • Images and examples that do not look borrowed from another market.

None of these is hard. They are simply easy to forget when the brief says "translate the website".

Payments and forms

If the site sells anything, checkout is where localization pays back or fails. Payment habits differ sharply by market. In the Netherlands, for example, Stripe describes iDEAL as the main payment method used by the vast majority of Dutch webshops; a checkout that offers only cards is asking Dutch buyers to change their habits at the last step. Each market has its own version of that story.

Forms cause quieter failures: address fields that assume a US or UK layout, postcode validation that rejects valid local formats, name fields that force a first and last name, phone fields that reject local numbers. Our article on checkout localization and conversion shows how to test a checkout field by field.

Legal pages are where a word-for-word translation of the headquarters version can be accurate and still wrong. Requirements differ by market, and some markets require pages that the main site never needed.

Provider identificationGerman law (section 5 of the Digital Services Act, DDG) requires commercial websites to carry an imprint that is easily recognizable, directly accessible and always available, with items such as name and address, contact details, register and VAT numbers where applicable.
Consumer informationUnder EU rules for online sales, sellers must give consumers clear information before the contract, including total price, payment and delivery arrangements, and withdrawal conditions. The standard withdrawal period is 14 days.
Privacy informationThe GDPR requires privacy information in a concise, transparent, intelligible and easily accessible form, using clear and plain language. Other markets add their own required contents and formats.

The practical approach: your legal team (or local counsel) decides what each market's pages must contain, and the translator works from that brief. The translator flags passages that refer to laws, authorities or rights that do not exist in the target market, instead of rendering them faithfully. Our article on privacy notices that are translated but not localized walks through one market in detail.

Month two: keeping the local site current

Most local sites look their best on launch day. Then the main site publishes new pages, updates prices, changes the privacy notice, and the local version falls behind without anyone deciding it should. Plan for upkeep before launch:

  1. Connect the CMS to the translation workflow. New and changed pages should be flagged automatically, not discovered months later.
  2. Agree update turnaround in writing. For example, legal and pricing changes within days, campaign pages before the campaign starts, blog content on a monthly batch.
  3. Keep a translation memory and glossary you own. Updates then cost only what changed, and terminology stays consistent across releases.
  4. Review a gap report every month. List pages that exist on the main site but not in each local version, and decide deliberately which ones to add or leave out.
  5. Recheck hreflang and canonicals after template changes. A redesign of the main site is the most common moment local search settings break.

What to ask a website localization provider

When you compare providers, ask questions that cover the whole launch, not only the word rate:

  • How do you receive content: CMS connector, export files, or copy and paste? What happens to text in images, PDFs and forms?
  • Who does local keyword research, and how does it reach the translators?
  • Do you check the staging site in context before launch, including mobile layouts, forms and checkout?
  • How are legal pages handled, and who confirms what each market requires?
  • What is your process and turnaround for updates after launch?

Our general guide on how to choose a professional translation agency covers pilots, security and service levels, and the scoping advice in running large document translation programs applies to the PDFs and downloads that sit on most corporate sites.

Launch checklist

  1. Every local page has its own URL, one language per page, and a visible link to other versions.
  2. Hreflang is reciprocal, includes a self-reference, and has an x-default where you need one.
  3. Canonical tags on local pages point to themselves, not to the main site.
  4. No automatic redirects based on IP or browser language.
  5. Titles, meta descriptions, image text and form messages are localized, not only page body text.
  6. Prices, contact details, formats and payment options fit the market.
  7. Legal pages were checked against that market's requirements, not only translated.
  8. An update process, owner and turnaround are agreed for after launch.

In brief

What is the difference between website translation and website localization?

Translation converts the text. Localization also adapts what surrounds it: search setup for each version, prices and payment options, contact details, legal pages, formats, images and the process that keeps the version current after launch.

Should we redirect visitors automatically to their local version?

Google advises against redirecting users automatically based on what you think their language is, or using IP analysis to adapt content. Offer a clear language or country selector and links between versions instead.

Is the lang attribute enough to tell Google the page language?

No. Google says it uses the visible content of a page to determine its language, not code-level information such as the lang attribute or the URL. Keep one language per page, and use hreflang to connect the versions.

Can we translate our privacy notice word for word from the global version?

The translation is a start, not the finish. Laws differ by market on what a privacy notice must contain, and the GDPR requires information in clear and plain language. Have the local version checked against the rules of the market it serves.

How do we keep localized pages up to date?

Connect the content management system to the translation workflow so new and changed pages are flagged automatically, agree a turnaround for updates, and review a list of pages that exist on the main site but not in each local version every month.

Planning a new market site?

If you are planning a new market site and want a second opinion on the scope, or need English-to-Korean website localization done with search, checkout and legal pages in view, see our services or get in touch.

Work with us

Your site, ready for Korean users on day one.

Website and software localization into Korean, tested in context before launch.

Get a free quote