Building a multilingual website: method and pitfalls to avoid

A multilingual website displays the same content in several languages with a distinct URL per language (subfolder, subdomain, or separate domain) and hreflang tags that tell Google which version to show based on the visitor's language and country. For a showcase site of 5 to 10 pages in two languages, professional translation generally costs between 300 and 1,500 euros depending on the volume of text, and technical integration takes one to three weeks.

The real problem: most multilingual sites are poorly structured

Translating a website isn't just about duplicating pages and swapping words. The problem most professionals run into when tackling a multilingual site isn't the translation itself, but the structure: which URL for which language, how to stop Google from indexing two identical pages as duplicate content, how to handle updates without editing each language by hand, and what to do when a page only exists in one language.

A poorly built multilingual site can be worse than a well-made single-language site: penalized duplicate content, the wrong version shown in search results depending on the country, language switching with no coherent redirects. All details invisible to a satisfied visitor, but that cost you in SEO and user experience.

Choosing the right URL structure

Three options exist, with different trade-offs.

For the vast majority of showcase sites and small businesses, the subfolder is the right choice. Reserve the dedicated domain for cases where you have a separate legal entity, team, and marketing budget per country.

Translating: machine, human, or hybrid

Three approaches, not to be confused:

1. Raw machine translation (built-in Google Translate, on-the-fly translation plugins): fast and free, but inconsistent quality. Reserve it for low-stakes sites or as a temporary fix.
2. Machine translation with review: an automatic first draft, corrected by a native speaker or professional translator. A good cost/quality compromise for a blog or informational pages.
3. Professional human translation: mandatory for sales pages, legal notices, terms and conditions, and any content that carries liability or affects your brand image. Expect generally 0.08 to 0.15 euros per word for a freelance professional translator, a bit more through an agency.

For a 3,000-word site (around ten pages), full human translation represents a budget of 250 to 500 euros per additional language, excluding ongoing updates.

Multilingual SEO: hreflang and adapted content

The hreflang tag tells Google which language version to serve based on the visitor's language and sometimes country. Without it, Google sometimes shows the French version to an English-speaking visitor, or vice versa, which hurts click-through rate and experience.

Two common mistakes:

• Translating word for word without adapting local search vocabulary: the queries typed into Google aren't the same in French, English, or Spanish, even for the same topic. A real multilingual SEO strategy uses keywords specific to each language, not a literal translation of the French keywords.
• Forgetting to translate metadata (title, description, image alt attributes): these are what show up in search results, not just the visible text.

Who translates, and who keeps it up to date?

This is often the underestimated part. A translation frozen at launch quickly becomes outdated: a new offer, a price change, a new blog post. On a site with a standard CMS (WordPress with a multilingual plugin like WPML or Polylang), every content update has to be manually repeated in each language, which doubles or triples the editorial workload over time.

On a subscription site where edits are handled by the provider, this synchronization work can be delegated: you send the translated text (or have it translated), and the update is applied across all languages without you having to touch the site yourself.

Solutions depending on your situation

• Existing WordPress site, 2 languages, tight budget: translation plugin (Polylang, free in its basic version) + human translation on key pages. A decent solution, but manual maintenance with every update.
• Full redesign, 2 to 4 languages, need for reliability: site designed multilingual from the start, subfolder structure, native hreflang, professional translation. This is the cleanest approach long-term.
• SaaS or application with frequently changing content: favor a translation system built into the workflow (versioned translation files, or a third-party service like Crowdin/Lokalise) rather than page-by-page translation.

Key takeaways

• The subfolder (site.com/language/) is the simplest and most effective structure for most professional websites.
• Human translation remains essential for any content that carries commitment (sales, legal notices, terms and conditions); reviewed machine translation is enough for secondary informational content.
• Hreflang prevents Google from showing the wrong language to a visitor, and content adapted to local search vocabulary beats a literal translation.
• Expect 250 to 500 euros of human translation per additional language for a ten-page site, and 1 to 3 weeks of technical integration.
• Ongoing maintenance (syncing updates across languages) often costs more over time than the initial setup: plan ahead for who handles it.

Frequently asked questions

Should I use a subdomain, a subfolder, or a different domain per language? A subfolder (site.com/en/) is the easiest to manage and concentrates SEO authority on a single domain. A subdomain (en.site.com) works if one language has a separate team or hosting. A dedicated domain (site.com) is only justified for a strong local presence, with a team and marketing budget on the ground.

Is machine translation enough for a professional website? For simple informational pages, machine translation reviewed by a native speaker can get you by. For sales pages, legal notices, or any content that carries liability, human translation remains necessary: translation engines still produce tone and meaning errors on industry-specific vocabulary.

Is hreflang mandatory for good rankings in each language? It's not a strict requirement, but its absence often leads to the wrong language version being indexed in a given country's results. On a site with more than two languages, misconfigured hreflang is the most common cause of pages cannibalizing each other in Google.

How long does setting up a multilingual website take? For a showcase site of 5 to 10 pages in 2 languages, expect generally 1 to 3 weeks between translation and technical integration, excluding proofreading. A larger site with a regular blog needs an ongoing translation process rather than a one-off project.

In summary

A well-built multilingual website rests on three pillars: a clear URL structure, translation suited to the stakes of each page, and correctly configured hreflang so Google serves the right version to the right visitor. If you're starting from a full redesign and want to avoid these pitfalls from the design stage, VeryAppi's website subscription plan includes multilingual structure within the unlimited edits, with no plugin overhead for you to manage.