Multilingual websites: what you need beyond translation
Neaptide · September 7, 2026 · 5 min read
Plan language URLs, navigation, forms, SEO and ongoing updates. Includes a Neaptide URL example and a practical acceptance checklist.
On this page
A translated homepage does not make the whole website usable in another language. A visitor can open a service, encounter an untranslated form and leave after an unclear error. Plan the complete journey, including confirmation messages and the team’s reply.
Choose markets you can support
Choose languages and markets separately. An English version does not mean you offer the same terms in every country. Decide where you can provide the service, how customers can contact you and who will answer. List only offices that actually exist.
Assign a content owner for each language. Budget for updates to services, prices, instructions and form messages, not just the initial translation. Otherwise versions drift after the first change.
Follow the same journey in two languages
Neaptide publishes the same web development service at /ru/services/web and /en/services/web. Use these two pages to check whether changing language keeps visitors on the right service and whether the form is usable. The table is a checklist, not a record of tests on every device or submission.
| Step | Russian | English |
|---|---|---|
| Open the service | /ru/services/web | /en/services/web |
| Change language | Remain on this service | Remain on this service |
| Open the form | Russian labels and errors | English labels and errors |
| Follow an article link | Russian version if available | English version if available |
Give each version its own URL
Google recommends a separate URL for each language version. Hreflang identifies corresponding pages: each version should reference itself and the others, with links in both directions. This helps describe the site’s language structure but does not replace the translation.
A complete translation generally needs its own canonical URL, which identifies the preferred address for that page. Do not point all translated pages to the original language by default. Near-identical pages aimed at different regions need a separate assessment.
A visitor should be able to open their chosen language directly. Avoid forcing another version solely because of an IP address. When a translation is missing, say so and offer an available version.
Translate forms and messages along with the pages
Check service names, currencies, units, dates, captions and metadata. Research local search wording separately: a translated keyword does not establish demand.
Test empty required fields, errors and confirmation messages. Internal links should retain the language where that translation exists. A clearly identified foreign-language source can still be useful.
Plan for the next update
Keep a list of pages, their translations and the dates of substantive updates. When service terms change, assign updates to the other versions too. Include diagrams and downloadable files in the review.
Review enquiries and search performance for each language section. A traffic difference does not by itself indicate a poor translation: demand and competition may differ. To discuss a multilingual site with Neaptide, prepare a list of markets, pages and languages your team can maintain.