Launching a multilingual website: URLs, language switching and final checks
Plan and review a multilingual site with mapped pages, language switching, complete content and a tested contact journey.
Article language: English

In this article
Four languages in a menu do not necessarily mean four working versions of a website. An offer may be in English while a form error appears in Polish, or a button may point to a translation that does not exist yet. Review the whole customer journey: URLs, matching pages, the language switcher, content and contact. Otherwise, a multilingual site can feel like a conversation in which every department answers in a different language, sometimes even a programming language.
This guide covers implementation: URLs, a map of corresponding pages, switcher behaviour and completeness checks. Decisions about the market and how to adapt the offer should come first. A finished text in another language is an input to the work, not automatic proof that the entire language version is ready.
What does launching another language involve?
Write down the scope for each part of the site. The home page, services, forms, error messages, documents and articles may be at different stages of preparation. Distinguish a translated interface from translated content. Replacing a Polish menu with an English one does not change the language of a long guide or an attached file.
Make a simple list of materials, with an owner and status for each. Mark what is ready, what needs editing and what you have deliberately chosen not to publish in that language. Do not hide gaps by silently substituting text from the base language. The customer should know what kind of material a link will open.
Connect the language scope to the localisation brief (in Polish). That material helps prepare input for writers and translators. At the technical stage, you also need decisions about which versions correspond, who approves them and who will answer enquiries in each language.
How should you choose URLs and map corresponding pages?
Every published version needs a clearly defined location. For a site with separate URLs, map the base page to its equivalent in the second language and any further variants. The relationship should reflect the content, not just a similar URL ending. Service names may be translated in different ways.
Google recommends separate URLs for language versions rather than relying solely on dynamic content changes based on browser settings. The choice of directories, subdomains or domains should take the company's structure and ability to maintain them into account. The URL format alone does not replace accurate content or links between versions.
Record missing equivalents in the project too. If an article exists only in Polish, the switcher should not pretend to open its English translation. You can link to the content collection in the selected language or clearly explain the limitation, according to the rule used across the site.
How should the language switcher work?
Name languages in a way readers can understand. Abbreviations can help where space is tight, but full names remove some ambiguity. A flag on its own can confuse a language with a country. For languages used in several countries, make clear whether the choice concerns language alone or a regional offer as well.
Try to preserve context when someone changes language. A person on a service page expects the corresponding page, if it exists. Sending every language choice to the home page forces them to search again. If no equivalent is available, explain this before the visitor loses their bearings.
Test the switch on a phone, with a keyboard and after opening a link directly. People must be able to correct the choice, even if the site suggests a language based on the browser. Google advises against automatic redirects based on an assumed language; a voluntary choice leaves the reader in control.
How should you mark the language of a document and its passages?
Content needs an accurate language declaration in HTML. W3C points to the lang attribute on the html element, with a suitable declaration on the surrounding element for a passage in another language. This helps tools process text appropriately, including choosing a screen reader's pronunciation.
Check the declaration in the finished document, not just in the management panel. If the interface is English but an article remains Polish, mark the actual content correctly. Do not assign a language to the whole publication solely from the active navigation button.
A demonstration version may behave differently from a published URL opened directly. Check both paths: changing language within the site and opening a link in a new session. A visitor should not first see an unexplained, unintended language and only later the intended content.
When and how should you use hreflang?
Hreflang describes the relationship between URLs for language or regional variants. If the implementation uses corresponding versions, prepare a consistent set of annotations. Google's documentation calls for each page to include itself and for variants to refer back to one another. Codes should reflect the actual language and, where relevant, the region.
Do not enter a URL that has yet to be created. Check that every target is available and matches the content map. Canonical and hreflang serve different purposes; the configuration should not accidentally name one Polish page as the sole correct document for every separate translation. The final settings need to be checked against the actual structure.
Check representative groups of equivalents: a service, an article and the contact page. A correct header on one page does not confirm the whole site. Keep a report of the target URLs so the team can check the same relationships when another language is added.

How should you review text, layout and characters in each language?
Do not compare paragraph counts alone. Check the meaning of the promise, service limitations, button labels and information needed to make contact. Differences between versions can be justified, but they should follow a decision. An old delivery time left in by accident can change a customer's expectations.
Look at the longest headings, lists and buttons. Languages change text length, line breaks and how typefaces are used. Test the typography of a premium website (in Polish) with real content, including Korean and Japanese characters where they are in scope. If a right-to-left language is added, also review mixed text directions in names, codes and addresses (in Polish), rather than judging label length alone.
Pay attention to easy-to-miss elements: photo captions, alternative text, empty-result messages and text shown after a form is sent. Use a shared checklist for repeated components. When a translation arrives after the design, review the layout again rather than assuming the earlier proportions still fit.
How should you test the form and actual contact handling?
Go through a submission in every language covered by the offer. Check fields, instructions, errors, consent and confirmation. The message sent to the team should retain the language context if it is needed for handling the enquiry. Saving a form alone does not prove that it reached the right person. When editing, apply the brand voice to interface messages (in Polish), making the current status and next step clear in both error and confirmation messages.
Test the B2B contact form (in Polish) from the browser through to the inbox. Use test data and check characters used in the language. Also observe what happens with an invalid address or a connection problem. The page should not switch to an incomprehensible technical message in those cases.
Decide who answers enquiries and which languages they actually support. Poland and Asia localisation (in Polish) includes this part of the experience. If a reply needs a translator or extra time, the company should agree on a process before it starts encouraging a new audience to get in touch.
What might a two-language site review look like?
In this hypothetical example, a company launches its offer in Polish and English but leaves its guides in Polish for now. The team maps service pages to their equivalents and tells readers which language the guides use. It does not create empty English URLs merely to give the switcher identical entries.
During testing, a customer opens an English page directly. They then check the sharing preview for a link to that page and see a Polish title. Elsewhere, the form sends the message correctly, but the subject of the enquiry loses the name of the selected service. Both issues are logged for the acceptance review even though the page being reviewed looked right visually.
After the fixes, the company repeats the tests for opening the link, changing language, submitting the form and receiving the message. Readiness means that the chosen user journey works and that the available content is described accurately. The team does not claim that article translations exist when they have not yet been prepared.
How should you update versions and detect discrepancies?
Every significant change to the offer should trigger a check of the dependent versions. Assign an owner to the base content and someone responsible for the other languages. The update record should show which materials need alignment and when their consistency was last confirmed.
Not every change requires identical wording. Consistent promises, scope and conditions matter more. If a local variant deliberately offers something different, record why. Otherwise, a later editor may mistakenly make the texts match and remove a necessary distinction. Add the review rule to the publishing process.
Technical checks should detect missing interface keys, empty URLs and incorrect relationships. A person remains responsible for meaning. An automated report showing the same number of headings does not establish translation quality. Also decide how to withdraw a version the company cannot maintain and where visitors will go next.
How should you document the final review and its limitations?
The report should identify the languages, URLs and scenarios checked. Separate confirmed results from materials awaiting approval. If a form works in English but the offer file is still Polish, record both facts. A general statement that multilingual support is ready makes later maintenance harder.
Include examples of problems found and the result of each retest. For a mapping error, give the source, expected equivalent and actual target. For a content discrepancy, identify the passage and the person responsible for the decision. This helps the team address the cause instead of fixing only the page where someone happened to notice it.
Include the report in the technical SEO review (in Polish) and the functional website review (in Polish). The checked set becomes a basis for updates after launch. A new language requires these tests again, even when it uses an existing template.
If readers save an offer for later, include a print version of the page (in Polish). Check each language in use, the names and the page breaks. A printout should not inherit a Polish footer merely because the English offer fitted on the paper.
What should the final implementation checklist cover?
Confirm the full scope:
- The map shows real equivalents and clearly identifies missing translations.
- The switcher preserves context and leaves the choice to the user.
- The language of the document and its passages matches the actual content.
- Version annotations point to available URLs and the correct reciprocal relationships.
- Headings, buttons and messages work with real text and on a phone.
- The form was tested in the browser and reached the team handling it.
- The company has assigned owners for updates to every published variant.
If you are preparing a multilingual site, explore Aeneia Design.







