Multilingual SEO: How to optimize a website for multiple languages

Translating your website does not automatically make it visible in international search results.

Search engines still need to understand which pages belong to each language or region, how the versions relate to one another, and which page to show to each searcher. Your localized content also needs to reflect the words people actually use in every market, not merely direct translations of your original keywords.

That is the purpose of multilingual SEO.

In this guide, you will learn how to build a multilingual website that search engines can crawl, index, and serve to the right audience. We will cover localized keyword research, URL structures, hreflang, canonical tags, internal links, sitemaps, and performance measurement.

What is multilingual SEO?

Multilingual SEO is the process of optimizing website content for searches in more than one language.

It combines traditional SEO, such as keyword research, on-page optimization, internal linking, and technical accessibility, with signals that help search engines understand language and regional variations.

For example, a software company may have:

• an English page for international visitors;

• a German page for German-speaking visitors;

• an English page with different prices and terminology for the United Kingdom;

• a French page specifically for customers in Canada.

These pages may discuss the same product, but they do not necessarily target the same audience or use the same search terms. Multilingual SEO helps each version compete in the appropriate search results.

Multilingual, multiregional, and international SEO

These terms are related, but they describe different situations.

A website can be both multilingual and multiregional. A Canadian website, for instance, may have English and French content while also serving different pages to customers in Canada and France.

Define this distinction before choosing URLs or hreflang values. A language code such as de targets German speakers generally. A language-region combination such as de-AT targets German-speaking users in Austria.

1. Research keywords separately for every market

Do not build your multilingual SEO strategy by translating a list of English keywords word for word.

People in different markets may describe the same product differently. Search demand, terminology, competitors, and buying intent can also change by country. Even markets that share a language may use different words. A British shopper might search for “trainers,” while a US shopper is more likely to search for “sneakers.”

For every target market:

• Start with the problems your audience wants to solve.

• Ask a native speaker or local subject-matter expert to identify natural terminology.

• Validate those terms with local search data.

• Review the pages currently ranking in that market.

• Map one primary search intent to each localized page.

Localize the entire search experience, including the title tag, meta description, headings, body copy, image alt text, URL slug, and calls to action.

The goal is not to make every language version structurally identical. The goal is to make every page useful and relevant to its intended audience.

2. Give every language version its own URL

Google recommends using a separate URL for each language version rather than changing the page language via cookies or browser settings.

A stable URL allows search engines to crawl, index, link to, and evaluate each version independently. It also gives users a page they can bookmark and share.

Avoid serving several languages from the same URL. Also avoid forcing users onto another version based only on their IP address or browser language. Search engines may not discover every variation, and users may be sent to a language they do not want.

3. Choose a multilingual URL structure

Three structures are commonly used for multilingual or multiregional websites.

Country-code top-level domains

A country-code top-level domain, or ccTLD, is suitable when each country operates as a largely independent market.

Examples:

• example.de for Germany

• example.fr for France

• example.at for Austria

This structure sends a clear country signal, but it requires separate domains, more maintenance, and a separate authority-building strategy for each site. A ccTLD also targets a country, not a language. A .de domain does not automatically target every German-speaking user.

Subdomains

Subdomains can separate languages or markets while keeping the same root domain.

Examples:

• de.example.com

• fr.example.com

• en-gb.example.com

They allow different technical configurations or hosting locations, but they usually require more maintenance than subdirectories.

Subdirectories

Subdirectories place all language versions on one domain.

Examples:

• example.com/de/

• example.com/fr/

• example.com/en-gb/

For many organizations, subdirectories offer the most practical balance. They are easy to manage and allow localized pages to benefit from the authority and links of one domain.

Whichever structure you choose, use it consistently. Do not mix /de/, de.example.com, and URL parameters without a clear technical reason.

4. Use hreflang to connect language and regional versions

The hreflang attribute tells Google that several URLs are language or regional alternatives of the same page. Follow Google’s guidelines for localized page versions when implementing hreflang through HTML tags, HTTP headers, or XML sitemaps.

It does not translate a page, make it indexable, or guarantee higher rankings. Its purpose is to help Google show the most appropriate version in search results.

Add a reference to every available version, including a self-reference:

<link rel="alternate" hreflang="en" href="https://example.com/product/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/produkt/" />
<link rel="alternate" hreflang="de-AT" href="https://example.com/at/produkt/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/product/" />

In this example:

• en serves English speakers without a specific region;

• de serves German speakers generally;

• de-AT serves German-speaking users in Austria;

• x-default provides a fallback when no listed language or region matches.

Hreflang rules to follow

• Use ISO 639-1 language codes, such as en, de, or fr.

• Add an optional ISO 3166-1 Alpha-2 region code, such as en-GB or fr-CA.

• List all alternatives on every member of the set.

• Include the page itself in the set.

• Use fully qualified, indexable URLs.

• Keep the references reciprocal. If page A points to page B, page B must point back to page A.

• Use x-default for a global fallback or language selector where appropriate.

• Do not use a country code without a language code.

You can implement hreflang in the HTML <head>, an HTTP header, or an XML sitemap. Choose one method and maintain it reliably. Adding the same correct set through several methods does not create an additional benefit and can make errors harder to diagnose.

5. Use canonical tags correctly

Hreflang and canonical tags solve different problems.

• hreflang connects valid language or regional alternatives.

• rel="canonical" identifies the preferred URL among duplicate or near-duplicate pages.

Localized pages with distinct languages should normally use self-referencing canonical tags:

<!-- On the German page -->
<link rel="canonical" href="https://example.com/de/produkt/" />

Do not point every translated page to the English version. That tells Google that the English URL is the preferred page and may prevent localized URLs from appearing as intended.

If two regional pages contain substantially the same content in the same language, for example, German pages for Germany and Austria, choose the canonical strategy carefully. Google recommends using canonical and hreflang together when genuinely duplicate regional pages require a single preferred version.

Translated content in different languages is not automatically a duplicate-content violation. The bigger risk is conflicting signals, incomplete localization, or several same-language URLs competing for the same intent.

6. Localize the complete page (not only the body copy)

A page can be translated and still perform poorly in search if its supporting elements remain generic or untranslated.

Localize the following elements:

• title tags and meta descriptions;

• headings and body copy;

• URL slugs where practical;

• navigation and breadcrumbs;

• image alt text;

• structured data content;

• product names, units, currencies, and examples;

• calls to action, forms, and confirmation messages.

Websites targeting Arabic, Hebrew, or other scripts must also handle right-to-left and left-to-right layouts correctly.

Keep one primary language on each page. Side-by-side translations or mixed-language navigation can make the experience less clear for users. Google primarily uses visible content to determine a page’s language.

Although Google does not use the attribute to identify a page’s language, the W3C recommends declaring the default language with the HTML lang attribute for accessibility, browsers, and other user agents.

7. Build internal links within and across language versions

Internal links help search engines discover localized pages and understand their importance.

Each language version should have a complete internal navigation structure. German content should link to other relevant German pages instead of repeatedly sending visitors back to English pages.

Also provide a visible language or region selector that links to equivalent pages. If a visitor is reading the German pricing page and switches to English, send them to the English pricing page (rather than the homepage).

Good language selectors:

• use standard links search engines can crawl;

• show language or region names clearly;

• remain available on every localized page;

• remember the user’s preference without blocking manual changes;

• avoid flag-only navigation, because a language is not the same as a country.

8. Include localized pages in your sitemap

Your XML sitemap should contain only canonical, indexable URLs that you want to appear in search.

Remove redirected, blocked, duplicate, and noindex URLs. Update the sitemap when pages are published, moved, or removed.

You can also specify language alternatives in the sitemap:

<url>
  <loc>https://example.com/product/</loc>
  <xhtml:link rel="alternate" hreflang="en"
    href="https://example.com/product/" />
  <xhtml:link rel="alternate" hreflang="de"
    href="https://example.com/de/produkt/" />
</url>

Every localized URL still needs to be crawlable. A sitemap helps discovery, but it does not override a noindex tag, blocked resources, an incorrect canonical, or a redirect.

9. Make JavaScript-based localization crawlable

Some websites load translated content after the initial page response or change languages entirely in the browser. This can create problems if search engines cannot render the final content or access a stable URL for each version.

Check that:

• every language version has a unique URL;

• localized content is present in the rendered HTML;

• navigation works without requiring cookies or a user action;

• internal links use crawlable <a href> elements;

• canonical and hreflang tags appear correctly after rendering;

• language versions do not redirect Googlebot based on location or headers.

Use Google Search Console’s URL Inspector to compare the rendered page with what users see.

10. Measure performance by language and market

Do not evaluate an international website only through one global traffic number. A gain in one large market can hide a serious decline in another.

In Google Search Console, review:

• clicks and impressions by country;

• queries by language and market;

• performance by localized directory or hostname;

• indexed versus submitted pages;

• pages excluded because of canonicals, redirects, or noindex directives;

• changes after migrations, redesigns, and translation updates.

Compare equivalent periods year over year to control for seasonality. Around a migration or relaunch, also review daily data so you can identify the exact date when visibility changed.

Useful multilingual SEO metrics include:

• non-brand clicks per market;

• rankings for local priority keywords;

• click-through rate by page and query;

• number of valid indexed localized pages;

• conversions from organic traffic by language;

• hreflang and canonical errors;

• backlinks from relevant local websites.

Common multilingual SEO mistakes

Avoid these frequent problems:

• Translating keywords without local research.

• Serving several languages from one URL.

• Redirecting visitors automatically without allowing a choice.

• Pointing every localized page’s canonical tag to the English page.

• Using incomplete or non-reciprocal hreflang sets.

• Confusing language targeting with country targeting.

• Translating the article but leaving metadata or navigation in English.

• Linking localized pages mainly to a different language version.

• Publishing machine-translated content without editorial review.

• Leaving redirected or non-indexable URLs in the sitemap.

• Using flags as the only way to select a language.

• Measuring all markets as one audience.

Multilingual SEO checklist

Before publishing a localized page, confirm that:

• [ ] Local keyword research supports the page topic.

• [ ] The page targets one clear search intent.

• [ ] The language version has a unique, stable URL.

• [ ] The title, description, headings, content, and CTA are localized.

• [ ] The page returns HTTP status 200 and is not blocked from indexing.

• [ ] The canonical tag points to the intended canonical URL.

• [ ] Hreflang values are valid, complete, and reciprocal.

• [ ] The page links to its equivalents through a visible language selector.

• [ ] Internal links lead to relevant pages in the same language.

• [ ] The URL appears in the correct XML sitemap.

• [ ] Structured data matches the visible localized content.

• [ ] A native speaker or qualified editor has reviewed the page.

• [ ] Search Console tracking can isolate the relevant language or market.

Build a localization workflow that protects organic visibility

Multilingual SEO is not a one-time technical setup. New product pages, changed source content, updated metadata, and removed URLs can create inconsistencies across every language version.

A defined localization workflow helps marketing, development, and translation teams keep content aligned. Glossaries and style guides protect local terminology. Translation memories reduce repeated work. Quality checks help teams catch missing or inconsistent content before publication.

LingoHub brings these parts of the localization process together so teams can manage multilingual content with clearer ownership and fewer manual handoffs.

Explore website localization with LingoHub

Frequently asked questions

Does translating a website improve SEO?

Translation can create access to new search demand, but translation alone does not guarantee visibility. Each market needs local keyword research, indexable URLs, localized metadata, relevant content, internal links, and correct technical signals.

What is the best URL structure for a multilingual website?

There is no universal answer. Subdirectories are often the easiest structure to maintain on one established domain. ccTLDs provide a strong country signal but require more infrastructure. Subdomains offer greater separation but also add management overhead.

Do multilingual websites need hreflang?

Hreflang is strongly recommended when equivalent pages target different languages or regions. It helps Google understand the relationship and show the appropriate version. It is not a substitute for crawlability, localization, or canonical tags.

Are translated pages duplicate content?

Pages translated into different languages are not automatically considered duplicate-content violations. Problems are more likely when same-language regional pages are nearly identical or when canonical and hreflang signals conflict.

Should a website redirect users based on browser language?

Avoid forced redirects. Offer a visible suggestion or language selector and let users choose. Every language version should remain accessible to users and search engines through a stable URL.