How to prepare a multilingual website

A multilingual website is not made difficult by the language switching button itself. Problems begin when different versions of pages live separately: translations become outdated, links lead to the wrong places, forms send notifications in the wrong language, and search engines don’t understand the relationship between versions.

It’s best to start preparing before translation. It is necessary to determine the address structure, list of materials, owner of each version, publication rules and verification method. Then adding a new language becomes a controlled process, rather than copying pages manually.

Below is a practical procedure that is suitable for a corporate website, catalog, service and client dashboard. The specific platform may differ, but the responsibility for the data, URL and translation quality remains the same.

1. Distinguish language from region

Language determines what language the material is written in, and region determines what country or market it is intended for. An English version for all users and separate English pages for the UK and US are different tasks. In the second case, prices, contacts, delivery, currency, legal conditions and assortment may differ.

Google Search Central also separates multilingual and multi-regional sites. Before development, create a table: language, region, domain or section, currency, units of measurement, contact information, required documents and responsible editor.

Don’t create a regional copy just for the sake of another flag in the menu. If the content is the same, the language version is sufficient. If the market requires separate conditions, record them as separate data, rather than manually inserting them into the text of each page.

2. Choose a stable URL structure

Each language version requires a separate permanent address. Practical options are subfolders like /en/ and /pl/, subdomains, or individual domains. The choice depends on the infrastructure and markets, but the design should be consistent across all page types.

Google recommends using different URLs for language variations, rather than changing the contents of one URL just by cookie or browser setting. Automatic redirection to the intended language may prevent the user and the search robot from opening the desired version. It is better to offer a switch and remember the choice without prohibiting manual transition.

Create rules in advance: what the address of the main page, services, articles, categories, cards and service pages looks like. Don’t unnecessarily translate old URLs after indexing. If the address does change, prepare a precise permanent redirection from the old version to the corresponding new one.

3. Map content and responsibilities

Make an inventory before starting the translation. It includes not only pages and posts, but also menus, footers, buttons, forms, error messages, letters, SEO titles, descriptions, alt texts, documents, images with captions and client dashboard elements.

For each piece of content, record the source language, translation status, date of last update, translator and the person who checks the meaning. The statuses “draft”, “in translation”, “under review”, “ready” and “needs updating” are useful. A translation cannot be considered ready just because a field is filled in.

Determine what happens if there is no translation yet. It is safer to display a deliberate placeholder or hide a link than to discreetly mix languages. Machine translation can speed up the draft, but prices, terms, terminology, calls to action and legal language must be reviewed by a human.

4. Translate the interface as well as articles

The user perceives the entire page. If the title is translated, but the menu, filters, submit button and message after the form remain in another language, trust decreases. Interface components should receive strings from a single dictionary, and not contain text inside a template or script.

The language switcher should lead to the appropriate page, and not always to the main page. Save the selected product, article or service if a linked version exists. It is better to write the names of languages ​​in the languages ​​themselves: “Polski”, “English”, “Russian” – this is clearer than a set of flags, since one language can be used in several countries.

Check search, breadcrumbs, pagination, filters, empty states, cookie banner and system notifications. For a multilingual catalogue, separately test sorting, transliteration, declensions and searching for words with diacritics.

5. Configure hreflang, canonical URLs and sitemaps

Linked language pages must be mapped explicitly. Google’s documentation on localized versions states that each version should list itself and other variants via hreflang, and backlinks should be reciprocal. For the language selection page, you can use x-default.

Canonical usually points to the current language page if it is a standalone translation. Do not reduce all languages ​​to one canonical: this way the search engine can exclude localized addresses. hreflang links equivalents, and canonical resolves the issue of preferred address within a particular version.

Choose one convenient way to support hreflang: HTML, HTTP headers, or sitemap. Mixing several mechanisms does not provide an advantage and complicates the diagnosis. After publication, check the response codes, indexability, reciprocity of links and the presence of all versions in the site map.

6. Set the page language and check typography

Set the correct attribute on each HTML page lang. For example, <html lang="pl"> Tells the browser and assistive technologies the primary language. W3C recommends specify the language specifically on the element html, and for fragments in another language – on the surrounding element.

Language affects Narrator pronunciation, spell checking, hyphenation, and glyph selection. For Arabic, Hebrew and other directions from right to left, you additionally need dir and a full layout check.

Not all fonts contain the characters you need. Before launching, check the Cyrillic alphabet, Polish characters, diacritics, quotation marks, long words and hyphens. A button that fits in English may be twice as long in another language. Correct the component and the adaptive, rather than shortening the translation to an unnatural phrase.

7. Include forms, integrations and legal text

The form must retain the language of the page along with the enquiry. Then the manager understands in what language to respond, and the letter to the client is formed from the correct template. Translate signatures, prompts, validation errors, consents, thank you page and automatic notifications.

Check where enquiries from different regions go, what CRM funnel is used, what currency the amount is transferred in and what date format the integration expects. Do not store the price only in the translated text: the value and currency should be structured data.

Privacy policies, payment, return and delivery terms may require not a literal translation, but adaptation to the market. Assign a person responsible for due diligence. For complex chains, it is useful to describe in advance the path of the enquiry from the site to the manager and test it in each language.

8. Establish an update and review process

The main reason for outdated translations is the lack of an update rule. When the original page changes, the system must mark related versions as requiring review. The editor sees the differences, the translator updates the necessary blocks, and publication occurs after approval.

Before starting, go through each key chain manually:

  1. open the language home page and switch to another version;
  2. go to the service, article and form, saving the corresponding page;
  3. check the menu, breadcrumbs, search and errors;
  4. send a test request and check the CRM and letter;
  5. check title, description, canonical, hreflang, sitemap and lang;
  6. look at the page on your phone with long translations;
  7. check addresses without translation and behavior when deleting a version.

Launch one additional language first and debug the process before adding the rest. If you need to select architecture and scope of work, describe languages, regions and page types in the brief. I will prepare the content map, URL structure, integration rules and implementation steps. Before the start, a checklist of technical specifications for the site will also be useful.