How to Make a Multilingual Website: URLs, Hreflang, Translation
How to make a multilingual website: subdirectories vs subdomains, hreflang and x-default, machine vs human translation, CMS options and SEO mistakes to avoid.

To build a multilingual website that ranks and converts, give every language its own crawlable URL (usually a subdirectory such as /de/ or /fr/), connect the versions with reciprocal hreflang tags plus an x-default fallback, and translate everything on the page, including titles, meta descriptions, slugs and image alt text. Let visitors choose their language with a visible switcher instead of forcing a redirect by IP. Machine translation is fine for a first draft, but pages that sell or carry legal weight need a human editor who knows the market.
Pick a URL structure before anything else
The URL structure decides how search engines see your language versions, how much hosting you manage and how authority flows between them. There are three serious options and one to avoid.
- Subdirectories (example.com/de/): one domain, one host, one codebase. Every backlink to any language strengthens the whole domain. Google lists low maintenance as the main advantage. This is the default we recommend for most companies.
- Subdomains (de.example.com): easy to host on separate infrastructure, which helps when a regional team runs its own stack. The downside is that users may not recognize the target market from the URL alone, and in practice each subdomain has to earn trust more on its own.
- Country-code domains (example.de): the strongest local signal and often the best fit when a market expects a local domain. They cost more to register, renew and maintain, some are restricted to local entities, each targets a single country, and each domain starts with zero authority.
- URL parameters (?lang=de): Google explicitly does not recommend them. Segmentation is hard and parameters are easy to lose in links and caches.
One rule applies to all of them: one language per URL. Google advises against showing different content on the same URL based on cookies or browser settings, because its crawler usually comes from US IP addresses and does not send an Accept-Language header. A page that adapts on the fly may simply never get its other versions crawled.
Subdirectories vs subdomains vs ccTLDs at a glance
| Criterion | Subdirectories | Subdomains | ccTLDs |
|---|---|---|---|
| Example | example.com/de/ | de.example.com | example.de |
| Shared domain authority | Yes | Partial | No |
| Local market signal | Medium (via hreflang) | Medium (via hreflang) | Strong |
| Setup and upkeep | Lowest | Medium | Highest |
| Separate hosting per market | Harder | Easy | Easy |
| Best for | Most businesses | Independent regional teams | Large country operations |
Hreflang and x-default done right
Hreflang tells search engines which URL to show to which language or region. It does not detect the language of a page (Google uses its own algorithms for that) and it is not a ranking boost. Its job is to stop the wrong version from appearing in the wrong country and to keep near-duplicate regional pages from competing with each other.
The rules that matter in practice:
- Reciprocal links. If the English page points to the German one, the German page must point back. If two pages do not reference each other, Google ignores the tags.
- Self-reference. Every version lists itself as well as all its alternates.
- Absolute URLs. Include the protocol and domain: https://example.com/de/pricing, not /de/pricing.
- Valid codes. Language in ISO 639-1 (de, fr, es), optionally plus a region in ISO 3166-1 Alpha-2 (en-US, en-GB, pt-BR). A region alone is invalid, and "en-UK" is wrong: the code for the United Kingdom is GB.
- One delivery method. Use HTML link tags in the head, HTTP headers (handy for PDFs) or an XML sitemap. They are equivalent, and using all three adds nothing but more places for errors.
- Canonicals agree with hreflang. Each language version should be canonical to itself. A German page canonicalized to the English one tells Google to drop it, and hreflang will not rescue it.
The x-default value marks the fallback page for visitors whose language you do not serve, such as a language picker or your main international version. It takes no language code. Add it to every cluster, especially if your home page chooses a language for the visitor.
A common mistake we see is hreflang pointing to URLs that redirect, return 404 or are blocked by robots.txt. Every URL in the cluster should return 200, be indexable and contain content in the declared language.
Machine vs human translation
Machine translation has become good enough that the question is no longer "whether" but "where". Engines such as DeepL and Google Translate, and the AI translation built into most localization tools, produce fluent drafts in seconds. The risks are in what they cannot know: your terminology, legal wording, local units and formats, and the way buyers in a given market actually search.
A practical split that works on most projects:
- Machine only: support articles, long product catalogs, internal pages, anything you would otherwise leave untranslated.
- Machine plus human edit: service pages, landing pages, blog posts you want to rank. The editor fixes terms, rewrites headings around local search queries and checks calls to action.
- Human from scratch (transcreation): brand slogans, ad copy, pricing pages, contracts, privacy policies and terms.
Translation is not localization. Website localization also covers currencies, date and number formats, phone formats, addresses, legal notices, payment methods and examples that make sense locally. Keyword research has to be redone per language: a literal translation of your English keyword is often not what people type in Germany or Brazil.
CMS options for multilingual content
Most platforms can handle several languages. What differs is how translations are stored, who edits them and what the add-ons cost.
- WordPress with WPML. The most widely used commercial option. At the time of writing, WPML sells a Multilingual Blog plan at €39, Multilingual CMS at €99 and Multilingual Agency at €199, each including one year of updates and support. The CMS and Agency plans include a quota of AI translation words. It handles WooCommerce, custom fields and string translation, at the cost of extra database load on large sites.
- WordPress with Polylang. A free core plugin on wordpress.org, with Polylang Pro from €99 per year and a Business Pack with WooCommerce support from €139 per year at the time of writing. Pro connects to DeepL using your own API key. Lighter than WPML and a good fit for content sites.
- Headless CMS. Field-level localization is built into platforms such as Contentful, Sanity, Strapi and Storyblok, and headless WordPress can store every language in the same backend. The frontend renders hreflang, localized slugs and the switcher, so you control every detail. This is how we build sites that need several languages from one editorial workflow, often on headless WordPress with a custom language module instead of a plugin.
- Webflow Localize. A paid add-on on top of a site plan. At the time of writing, Essential starts at $9 per month (up to 3 locales, 10,000 AI translation words per month) and Advanced at $29 per month (up to 10 locales, 50,000 words per month), with the price depending on the number of locales. Webflow publishes locales in subdirectories and can generate hreflang tags and sitemap entries automatically. Localized URLs, asset localization and automatic visitor routing are listed for Advanced, not Essential, so check the plan before you promise translated slugs.
Translation proxies (services that serve translated copies of your site from their own layer) are the fastest way to launch, but your content then lives outside your CMS and the bill usually grows with word count and traffic. Choosing the platform itself is a separate decision; the point here is that every option above can produce clean multilingual SEO when configured properly.
Language switcher UX
The switcher is a small component that decides whether visitors trust the rest of the site.
- Put it where people look for it: the header, usually top right, and repeat it in the footer.
- Write each language name in that language: Deutsch, Français, Español. A German speaker stuck on a Japanese page cannot read "German" written in Japanese.
- Avoid flags for languages. A flag is a country, not a language: Spanish is spoken in more than twenty countries and Switzerland has four national languages.
- Link to the same page in the other language, not to the other home page. If a page has no translation, say so and offer the closest page.
- Use real links (anchor tags with href), not JavaScript-only buttons, so crawlers can follow them, and set the lang attribute on the html element of every version.
- Remember the choice. If a visitor picks French, do not switch them back on the next click.
Suggesting a language is fine: a dismissible banner that says "This page is available in Deutsch" respects the visitor and keeps every URL reachable.
Common SEO mistakes on multilingual sites
- Auto-redirect by IP or browser language. Google advises against it: IP location is unreliable, travelers and expats get the wrong version, and redirects can stop users and crawlers from reaching your other versions. Suggest, do not force.
- Untranslated metadata. The body is in Spanish but the title tag, meta description, Open Graph tags and image alt text are still English. Search results then show English snippets for a Spanish page, and fewer people click.
- Mixed languages on one page. Translated navigation around an untranslated article, or English buttons and form errors inside a German checkout. Google specifically warns against translating only the boilerplate while keeping the main content in one language.
- Untranslated slugs and structured data. /fr/our-services works, but /fr/nos-services reads better and can match local queries. FAQ and product schema should be in the page language too.
- Thin regional duplicates. en-US, en-GB and en-AU pages that differ only in spelling. Use hreflang so they do not compete, and add real differences: prices, contacts, delivery terms.
How to choose: what we recommend
Our decision rule for most companies entering a new market:
- Use subdirectories on your main domain unless a market demands a local domain or a regional team needs its own infrastructure.
- Generate hreflang, canonicals and the sitemap from the CMS or the code, never by hand, and validate them after every release.
- Machine-translate for coverage, then pay for human editing on the pages that bring revenue: home, services, pricing, top landing pages.
- If you have two or three languages and a small team, a plugin or Webflow Localize is enough. If you have many languages, several editors or a product catalog, plan a structured CMS where every field is localizable.
When a site already exists, start with an audit of the URL structure and hreflang before translating anything new. If you would rather hand it over, our team builds multilingual websites with localized SEO from the first release, and we plan language versions into corporate websites from the start, so a new market becomes a content task rather than a rebuild.
Translation converts the text into another language. Localization adapts the whole experience to a market: currency, date and number formats, legal notices, payment methods, contact details and the keywords local buyers use. A translated site can still feel foreign; a localized one reads as if it was made for that country.
Yes, if both versions are indexable. Hreflang helps Google show the right version in each country and is cheap to implement on a small site. Add an x-default as well, pointing to the version you want visitors of other languages to see.
Not by itself. Google judges content by quality and usefulness, not by how it was produced. The problem is unedited output that is awkward, inaccurate or targets the wrong keywords. Review at least the pages that drive leads and sales.
No. Automatic redirects by IP or browser settings send travelers and expats to the wrong version and can hide pages from crawlers. Show a dismissible suggestion banner instead and keep every language reachable through the switcher.
Start with the markets that already send you traffic or leads, usually one or two languages beyond your main one. Every language adds ongoing work: new pages, updates, support and SEO. Two well-localized versions beat five half-translated ones.
How we can help
- Multilingual websitesWebsites in several languages: one structure, translated URLs and proper search markup
- Corporate websitesA website that represents your company, brings in leads and is easy to update
- Headless WordPress websitesNew websites with WordPress as the CMS and a fast Nuxt front-end: easy for editors, fast for visitors



