Multilingual SEO: How to Set Up a Multilingual Website for Google in 2026

Multilingual SEO means making each language version of a website findable in its own market. Google recommends a separate URL for every language version, hreflang annotations that link the versions to each other, one language per page, and no automatic redirects based on the visitor’s language or location. A translated page is not treated as duplicate content as long as its main content is actually translated.

By , Editor-in-Chief, Web First Rank
21 years of experience in digital communication · 90 training sessions · Web First Rank, founded in 2009, has delivered more than 1,000 projects
Updated October 26, 2026. The 2022 version of this article covered only translation and the choice of a CMS, repeated one section twice, and did not mention URLs or hreflang; it was rewritten from Google’s current documentation.

Is a translated page duplicate content?

No. Google states that localized versions of a page are considered duplicates only if the main content remains untranslated (Google Search Central, updated September 21, 2026). A French page and its English translation are two different pages for Google. Our guide to canonical URLs explains what duplicates are and how to handle them.

Which URL structure should you choose?

Google recommends using different URLs for each language version of a page, rather than cookies or browser settings to change the language. It lists the following options for geotargeting and language versions (Google Search Central, updated December 10, 2025):

Four URL structures for a multilingual site

Country-specific domain
Example
example.de
Main trade-offs, according to Google
Clear targeting and separation, but costly, with strict rules in some countries and only one country per domain
Subdomain on a generic domain
Example
de.example.com
Main trade-offs, according to Google
Easy to set up and flexible server locations, but visitors may not tell whether “de” means a language or a country
Subdirectory on a generic domain
Example
example.com/de/
Main trade-offs, according to Google
Easy and low-maintenance on one host, but harder to separate sites and one server location
URL parameters
Example
site.com?loc=de
Main trade-offs, according to Google
Not recommended: hard to segment and unclear to visitors
Source: Google Search Central, Managing multi-regional and multilingual sites, updated December 10, 2025. Summary by Web First Rank.

In short: Google does not recommend URL parameters; subdirectories are the easiest to maintain on one host, and country domains give the clearest targeting at a higher cost.

For most small and mid-sized businesses, subdirectories on one domain are the simplest to maintain. This site works that way, with French at the root, English under /en/ and Arabic under /ar/.

How hreflang works

The hreflang annotation tells Google which versions of a page exist in which languages. The rules, according to Google’s documentation:

  • Three equivalent methods: HTML link tags, HTTP headers or an XML sitemap. Google says they are equivalent and advises against using all three together.
  • Every version lists itself and all the others. If two pages do not point to each other, the tags are ignored.
  • Valid codes only: an ISO 639-1 language code, optionally followed by an ISO 3166-1 Alpha 2 region code, such as fr, en-GB or ar. A country code cannot be used alone.
  • x-default is the fallback used when no other language or region matches the visitor’s settings; Google recommends it for language selector pages.
  • Google says it does not use hreflang or the HTML lang attribute to detect the language of a page: it relies on its own systems.

An example for a page available in three languages, placed in the <head> of each version:

<link rel="alternate" hreflang="fr" href="https://www.example.com/page/" />
<link rel="alternate" hreflang="en" href="https://www.example.com/en/page/" />
<link rel="alternate" hreflang="ar" href="https://www.example.com/ar/page/" />
<link rel="alternate" hreflang="x-default" href="https://www.example.com/page/" />

One language per page, no automatic redirects

  • Keep a single language for content and navigation on each page and avoid side-by-side translations.
  • Do not redirect visitors automatically by language or location. Google advises against it, because it can keep users and crawlers from seeing every version. Googlebot usually crawls from the United States and does not send an Accept-Language header, so it may miss variations served from language settings.
  • Do not use IP analysis to adapt your content. Offer visible links to the other language versions, so visitors can choose.

Translation quality and CMS

Google’s multilingual page does not discuss machine translation, so what follows is our own advice. For an online store or any commercial content, have a native speaker translate or review product pages, calls to action and legal text: an awkward translation weakens your credibility and your conversions, whatever the technical setup. On WordPress, a multilingual plugin such as Polylang, which this site uses, lets you manage each language with its own URL; large catalogs may need a platform built for that scale.

Our experience on our own site

Our own site is multilingual: French at the root, English under /en/ and Arabic under /ar/, with hreflang annotations for French, English, Arabic and x-default on its pages. It is the subdirectory option from the comparison above.

Checklist before launching a multilingual site

  1. Choose a URL structure and keep it for every language.
  2. Give every language version its own URL and its own translated navigation.
  3. Add reciprocal hreflang annotations, with valid codes, using one method only.
  4. Do not redirect visitors automatically by language or location; offer a visible language switcher.
  5. List all language versions in your sitemap and check them in Search Console.
  6. Have the commercial content reviewed by a native speaker.

FAQ

Do I need a separate domain for each language?

No. Google lists country domains, subdomains and subdirectories as possible structures, each with trade-offs. Subdirectories on a single domain are often the simplest to maintain.

Do I need hreflang on every page?

Every page that exists in several versions should carry annotations that list itself and all the other versions, and each of those versions must point back. Annotations without matching return links are ignored.

Does Google detect a page’s language from hreflang?

No. Google says it does not use hreflang or the lang attribute to detect the language of a page; it relies on its own systems. The annotation tells Google which versions belong together.

Can I redirect visitors automatically to their language?

Google advises against automatic redirects based on language or location, because crawlers and some visitors may never see the other versions. A visible language selector is the safer option.

Need to take your site international?

Our team sets up multilingual structures and checks that every version is indexed and correctly linked. Discover our SEO services or request a free quote.

Read also: Canonical URLs: how they work and what Google says · SEO audit checklist

Aymen Turki

Editor-in-Chief, Web First Rank

Aymen Turki has 21 years of experience in digital communication and has run 90 training sessions and 30 interventions. Web First Rank, founded in 2009, has delivered more than 1,000 projects.

Sources

Directeur Général, WFR