Picture a furniture manufacturer with a Turkish website that has started getting enquiries from abroad. The plan sounds simple: send the pages to a translator, paste the English text into the site, add a flag in the corner. Three weeks later the English pages are live.
Six months on, the picture is different. The Turkish product pages have new models that the English pages never got. The contact form says "Thank you" in English, but the confirmation email arrives in Turkish. A visitor from Germany sees prices with a comma where they expect a point. The flag in the corner takes everyone to the English home page, wherever they were.
None of this is a translation problem. It is a set of decisions that were never made. The eight below are the ones that decide whether a second language keeps working after launch day.
1. Who owns each language after launch?
Translation is a one-time job; keeping two languages in step is a permanent one. Every new product, price change, announcement or job listing now has to happen twice, and the second version is the one that gets forgotten.
Name a person responsible for each language, and agree on a rule: is a page published only when both versions are ready, or can one language go first with a deadline for the other? Either rule works. Having no rule is what leaves the second language a few months behind, quietly.
2. Does each language have its own address?
The language a visitor sees should come from the address, not from a hidden setting. A structure like /tr/... and /en/... lets people share a link and be sure the person who opens it sees the same language. It also lets search engines find and list each version separately.
Avoid sending visitors to a language automatically based on where they appear to be. A Turkish speaker abroad, a foreign manager in Istanbul and a company using a VPN all end up on the wrong version with no obvious way back. Suggest a language if you like, but let the visitor choose and remember the choice.
3. Does the language switch keep the visitor on the same page?
The flag or language menu should take the visitor to the same page in the other language, not to the home page. That sounds obvious, but it requires the site to know which page matches which. If page addresses are translated too, as they usually should be, that pairing has to be stored somewhere and kept up to date when pages are added or renamed.
When a page exists in only one language, the switch should say so, or lead to the closest page that does exist, rather than to an error page.
4. Are forms, emails and messages translated as well?
The visible pages are usually translated; the text around them often is not. Form labels, error messages ("please enter a valid phone number"), the confirmation email, the automatic reply, the PDF quote, the cookie notice and the text in the browser tab are all part of the site.
Make a list of every message the site sends or shows outside the main pages and translate it along with them. Then fill in each form once in each language and read what arrives in the inbox.
5. Are dates, numbers and prices written the way readers expect?
The same value is written differently in each language. 1.250,00 in Turkish is 1,250.00 in English. 21.10.2026 in Turkish is usually October 21, 2026 in American English. Phone numbers, addresses and units vary too.
Let the site format these according to the page's language instead of typing them into the text by hand. If you show prices to visitors abroad, decide which currency they see, whether it is converted automatically or set by you, and what happens to the price when the exchange rate moves.
6. Does the design survive longer and shorter text?
A button that fits "Teklif al" may not fit its translation in another language. Headings wrap onto a third line, menus overflow, table columns squeeze. Some languages run noticeably longer than Turkish or English; others need a right-to-left layout altogether.
There is also a quieter issue with Turkish itself. Turning text to capital letters in code without telling the browser the page's language can produce the wrong letters: "i" should become "İ" in Turkish but "I" in English. Setting the correct language on every page fixes this and also helps screen readers pronounce the text correctly.
Review the main templates with the longest real text in each language, not with the original.
7. What happens to pages that are not translated yet?
Not every page needs to exist in every language. Blog posts, local campaigns or job listings may stay in one. The question is what visitors and search engines see when they reach a page that has no translation.
Decide this per section: hide the page from the other language's menus and lists, show it in the original language with a short note, or wait until the translation is ready. What should never happen is a page that shows the other language's layout with the original text inside it, or an empty page.
8. Who reviews machine translation before it goes live?
Machine translation and AI tools give a useful first draft in seconds. They also translate product names that should stay as they are, choose a formal or informal tone at random, and miss terms your industry uses. In Turkish to English, a word like "cari" or "plasiyer" has no single dictionary answer; it depends on the business.
Use the draft, but have someone who knows both the language and the business read it before publishing. A short glossary of the terms you always translate the same way saves that person time and keeps every page consistent.
In short
A second language keeps working when each language has an owner, each page has its own address, the language switch keeps people on the same page, forms and emails are translated too, dates and prices follow the reader's format, the design is checked with real text, untranslated pages have a rule, and a person reviews machine translation before it goes live.
When we build multilingual corporate websites, we settle these eight points before the first page is designed, so that adding the next page in both languages is routine rather than a project.
Planning a project like this?
Plan it in 10 steps