A multilingual website is often scoped as “the same site, translated”, and that assumption is where budgets and deadlines go wrong. Each language adds decisions about structure, search visibility, design, legal content and, above all, who keeps it current after launch. None of this is difficult when planned from the start, and all of it is expensive when discovered late. This guide walks through what the work really involves, so that you can brief it properly and choose how many languages to launch with.
What does a multilingual website involve beyond translation?
Translation of the visible page text is the largest single task, but it sits alongside several others:
- A URL structure and technical setup that search engines can interpret.
- Keyword research in each language, since people search differently in each market.
- Design that copes with longer and shorter text.
- Translated forms, emails, legal pages and system messages.
- A process for keeping all versions in step when content changes.
- Someone able to answer enquiries in each language you publish.
The last point is worth settling first. A page that invites contact in German creates an expectation of a reply in German. If you cannot support a language commercially, it may be better not to publish it yet.
How should you structure URLs for each language?
There are three common options. Subdirectories (yoursite.com/fr/) keep everything on one domain, are the simplest to manage and suit most businesses. Subdomains (fr.yoursite.com) behave more like separate sites. Country domains (yoursite.fr) send the strongest local signal but mean separate domains to register, maintain and build authority for.
Whichever you choose, a few rules apply:
- Every language version of a page needs its own URL. Content that changes language on the same address cannot be indexed properly.
- Add hreflang annotations so that search engines know which pages are equivalents and show the right one to each user. Each version must reference all the others and itself.
- Decide whether you are targeting languages or countries. French for France and French for Canada are different audiences with different vocabulary, currency and law.
- Translate the URL slugs where practical.
- Provide a visible language switcher that leads to the equivalent page, not back to the home page.
Who translates, and how do you control quality?
You have three realistic routes: professional human translation, machine translation reviewed by a native speaker, or raw machine translation. The right mix depends on the page. Home, service and sales pages carry your reputation and deserve a native writer who adapts the message rather than converting it word for word. Large volumes of supporting content can reasonably start from machine output and be reviewed.
Quality comes from preparation as much as from the translator:
- A glossary of product names, technical terms and words that must stay untranslated.
- A note on tone, including formal or informal address, which matters in French, German and Spanish.
- Keyword research per language. Translating your English keywords rarely gives the phrases local customers type.
- A final review of the text in place on the page, where truncated buttons and awkward line breaks become visible.
What needs translating that teams usually forget?
The body text gets attention. The surrounding material is where untranslated fragments appear after launch:
- Page titles and meta descriptions.
- Image alternative text, and any images that contain words.
- Forms: labels, placeholders, validation errors and confirmation messages.
- Automatic emails, such as enquiry confirmations and order notifications.
- Cookie banner, privacy policy, terms and other legal texts, which may also need legal review for each market.
- Navigation, footer, search results and 404 pages.
- Downloadable documents, video subtitles and structured data.
- For shops: currencies, tax display, delivery information, checkout and return policies.
Prepare this list as an inventory before requesting a translation quote. It prevents both surprise costs and an embarrassing mixed-language checkout.
How does design cope with different languages?
Text length changes with language. German and French commonly run longer than English, and a button label that fits neatly in one language can wrap or overflow in another. Layouts should be designed and tested with the longest language, not the master one.
Check that your chosen fonts include every accented character and special letter you need, otherwise the browser will substitute a different font for individual characters. Format dates, numbers, addresses and phone fields for each locale. Review imagery and examples for local relevance. If you plan to add a right-to-left language such as Arabic later, say so early, because it affects how the whole layout is built.
How do you keep every language up to date?
Launch is the easy part. The real cost of a multilingual website is that every future change happens several times. A new service page, an edited price list or a blog post needs translating, reviewing and publishing in each language, or the versions drift apart.
Agree a workflow before launch. Choose one master language in which content is always written first. Decide who is notified when the master changes and who approves each translation. On WordPress, plugins such as TranslatePress, WPML or Polylang manage linked language versions and show what is missing or outdated, but the tool only supports the process and does not replace it.
Be selective too. Not everything must exist in every language. Many companies translate core pages fully and publish the blog only in the languages where they can sustain it.
What drives the cost and timeline?
The main factors are the number of languages, the volume of text, the translation method, and how much is bespoke per market rather than translated. E-commerce, legal review and separate keyword research add effort. A site built for multiple languages from the outset costs considerably less to extend than one where languages are retrofitted on a layout that never anticipated them.
Frequently asked
Is automatic translation good enough?
For understanding, often yes. For persuading a customer, usually not without review. Machine output can misjudge tone, terminology and context. Use it as a starting point and have a native speaker revise the pages that matter commercially.
Should the site switch language automatically based on location?
Avoid forced redirects. Location and browser settings do not reliably indicate preferred language, and automatic redirection can stop search engines reaching all versions. Suggest a language if you wish, and always let the visitor choose and keep their choice.
Do we need a separate domain for each country?
Rarely. Subdirectories on a single domain work well for most organisations and concentrate your search authority in one place. Country domains make sense when each market operates as a distinct business with its own team.
How many languages should we launch with?
As many as you can maintain and support with replies, not as many as you can afford to translate once. Starting with two done properly and adding more later is a sound approach.
If you are planning a site in more than one language, our website development team can help you define the structure, workflow and scope before translation begins.
