Multilingual corporate website: Showing every visitor the page in the right language

A multilingual corporate website is a site that presents the same organization’s content in more than one language, each with its own address, title and layout. The goal is that a visitor from Germany meets a page in German and a visitor from Turkey a page in Turkish. The problem is usually not the translation itself but the decisions around it; these are points that should be settled at the design stage of a web design project, and they are covered below in order.

The most common misunderstanding is tying multilingualism to a single translation plugin. Content left to browser translation or an on-page plugin may not be seen by search engines as separate pages, corporate terms get translated inconsistently, and the brand’s tone is lost. A multilingual site treats languages not as copies of a page but as complete versions: with their own title, description, links and, where needed, their own layout.

Decision 1: At which address will the languages live?

• Subdirectory (for example /en/): Managed under a single domain, easy to maintain and measure. For most corporate sites it is the most practical option.
• Subdomain (for example en.site.com): Separates the languages technically; however, each may be evaluated as a separate site by search engines and needs separate management.
• Separate domain: Suitable for country-specific corporate structures; but it is the option with the highest cost and maintenance load.

Whichever option you choose, each language’s page should have a permanent, readable address, and the address structure should follow the same logic in all languages. Changing the address scheme later misleads both the visitor and the search engine.

Decision 2: Telling the search engine which page is in which language

Language counterparts of the same page are communicated to the search engine with markers. The hreflang tag used for this states which language each page is in and at which address its counterparts in other languages live. This way someone searching from Germany sees the German version instead of the Turkish page. In addition, each language version should have its own page title and description; translating only the body text and leaving the title in Turkish is a common mistake. The sitemap should also cover all language versions.

Decision 3: How does the visitor reach the right language?

1. Add a visible language switcher. Every page should have an easy-to-find switcher in which the languages are written in their own names (Deutsch, English, Türkçe); flag icons represent a country, not a language.
2. Go to the counterpart of the same page. A visitor who changes language should be taken not to the home page but to the counterpart, in that language, of the page they were viewing.
3. Remember the choice. Once a visitor has chosen a language, they should be greeted in the same language on later visits.
4. Suggest, do not force. You can detect the browser language and offer a suggestion; but redirecting the visitor to another language without permission confuses both the user and the search engine robot.
5. Show a missing translation honestly. If a page has no counterpart, send the visitor not to an empty page but to the closest suitable page, and say so.

Translation quality and localization

A good translation does not end with writing the equivalents of words. You need to decide how product and service names will be written, date, currency and unit formats, the form of address and culture-specific expressions. Adding a corporate glossary to the translation process ensures the same concept appears the same way on every page. The design should also be prepared for the languages:

• In some languages, texts are noticeably longer than in Turkish; buttons and menus must not overflow.
• For right-to-left languages such as Arabic, the page layout needs to be mirrored.
• Fonts suited to the languages should be chosen; special characters must display completely.
• Text embedded in images cannot be translated; where possible, keep text and image separate.

How many languages should you start with?

Every new language means a permanent maintenance load. So it makes sense to start with the markets where customers, partners or candidates actually come from. Even so, the site’s structure should be built from the start to be ready for all languages: language addresses, menu, page templates and content fields should be planned so that adding a new language does not force you to redo the design from scratch. Many half-finished language versions inspire less trust than a few languages that are regularly maintained.

Upkeep: do not let the languages drift apart

The biggest risk of a multilingual site begins after setup. The Turkish page gets updated, the other languages stay old; the visitor sees different information for the same product. To prevent this, it should be decided up front which languages will be updated for every new piece of content, half-translated pages should not be published, and the person responsible for updates should be clear. Even a simple tracking list showing which page was updated in which language and when makes a big difference. Pages that tolerate no error, such as pricing, contact information and legal texts, should be at the very top of this list.

When the site is multilingual, the first contact with the visitor should be multilingual too. The YazSis AI Sales & Welcome Assistant works in the visitor’s site language, and seven languages are stated on the product page; this way there is no need to build a separate welcome team for each language.

If you would like to draw up a roadmap for a new multilingual site or for the language versions of your existing site, you can look at YazSis’s steps of discovering the brand and goal, validating the page architecture with a prototype, and measuring performance after launch on the Web Design page.