Ask a marketing team how to translate a website and the answer is usually procedural. Export the strings, send them to a supplier, import them back, ship it. That description is accurate and almost useless, because it leaves out the part that decides whether the new version earns anything. A translated site is not the original wearing a different coat. It is a second attempt at convincing a reader who arrived with different assumptions, a different search habit and a different idea of what a credible company sounds like.
Companies that get this right tend to treat the work as a product launch rather than a document conversion. That single shift changes who sits in the room, what gets measured and how long the project is expected to take.
Start with the pages that actually carry weight
Very few sites need all of themselves in every language. Pull twelve months of analytics and you will normally find that a small group of pages does almost all of the commercial work: the homepage, two or three service or product pages, pricing, the contact form and perhaps a handful of articles that pull steady search traffic. Translate those properly and leave the rest for a later phase.
The urge to translate everything at once is expensive and it dilutes quality. A hundred mediocre pages perform worse than fifteen good ones, and they cost more to maintain every year afterwards.
Decide what "the same" is supposed to mean
Before a single word is written, someone has to answer a deceptively simple question. Should the German site say the same thing as the English one, or achieve the same thing? Legal notices, product specifications and safety information belong in the first category, where fidelity is the whole point. Headlines, calls to action and value propositions belong in the second, where a literal rendering usually lands flat.
Brands that skip this conversation end up with pages that read like the transcript of a marketing meeting. The pattern shows up again and again in the campaigns that went wrong when global brands underestimated localization, where every word was technically correct and the meaning still arrived bruised.
Website localization is a set of decisions, not a checkout button
The industry term for the wider job is website localization, and it covers everything that text alone cannot fix. Currency and payment methods. Date and address formats. Phone fields that accept the right number of digits. Photographs of people and places a local reader recognises. Legal pages that reflect the rules of the market you are entering rather than the one you left.
Serious website localization services ask about all of this before quoting. A supplier who does not ask is pricing the easy half of the job and will discover the other half at your expense.
The technical layer that quietly decides your rankings
Multilingual website SEO is where a lot of otherwise careful projects lose their return. Search engines have to be told which version belongs to which audience, which is what hreflang annotations exist for. Get them wrong and you will serve the Spanish page to readers in Mexico, the English page to readers in Spain, or neither page to anyone.
Two structural choices matter just as much. Pick a URL pattern early, whether that is subdirectories, subdomains or country domains, because changing it later means a migration nobody enjoys. And translate the metadata: title tags, descriptions, image alt text and slugs. A page with a beautifully written body and an untranslated URL looks half-finished to readers and crawlers alike.
Keywords do not travel
This is the step most often skipped. The phrase your English customers type is frequently not the literal translation of what your French or Japanese customers type. Sometimes the local market searches for the problem rather than the product. Sometimes it uses the English loanword. Sometimes the highest-volume term is one your brand would never choose for itself.
Translating a website without losing rankings is mostly an engineering problem: URLs, markup and internal linking have to survive the process. The content is only part of it. Doing it properly is closer to software localization than to document translation.
Research the target language on its own terms, then let the findings shape headings and page titles. Translating your existing keyword list simply imports one market's search habits into a country that does not share them.
Machine translation has a place, just not that one
Modern engines are genuinely strong on high-volume, low-stakes content: support articles, catalogues with thousands of near-identical entries, internal documentation. They remain unreliable on the pages where tone and precision earn money. A sensible split is machine output with human editing for the long tail, and human translation with a subject-matter reviewer for anything that persuades or carries legal weight.
Test in the language, not in the spreadsheet
Translations are usually signed off in a two-column file where nothing looks broken. Then the text lands in the design, German runs a third longer than English, a button label wraps onto three lines and a testimonial ends up under the wrong photograph. Build a staging version, ask a native speaker to click through it the way a customer would, and fix the problems that only appear in context.
Plan for the second year
Websites change. If the translated pages are not wired into the same publishing routine as the source, they drift, and a stale price or a discontinued product does more damage than no page at all. Decide who owns updates, agree how quickly translations follow the source, and keep a translation memory so recurring phrases stay consistent and cost less each time they appear.
Handled this way, the project stops being a one-off expense and becomes what it should have been from the beginning: a version of your business that a reader in another country can take seriously.
