Multilingual SEO is the set of technical choices that decide whether your translated pages actually get found: a URL structure Google can crawl, hreflang tags that point each version at the right audience, translated sitemaps and metadata, and duplicate-content handling done right. Translating your content is the easy half. This guide covers the four things that get those translations found โ and the handful of mistakes that quietly keep them out of search entirely.
You can translate every page on your site perfectly and still get zero traffic from other markets. It happens constantly. The translations are fine; the SEO plumbing underneath them isn't โ so Google either never indexes the translated pages, or serves the wrong language version to the wrong person, or treats your versions as duplicates and picks one to ignore.
Multilingual SEO is that plumbing. Get it right once and your translated pages compete in local search results the way your original does at home. Get it wrong and you've done the work of going multilingual without the payoff. Here's what actually matters, in order.
(If you're earlier than this โ still deciding what to translate and adapt for each market โ start with what website localization involves; this guide is the SEO layer that sits underneath it.)
What Is Multilingual SEO?
Multilingual SEO is optimizing a website that exists in more than one language so search engines index each version, rank it in the right market, and never confuse the versions with each other. It covers four technical areas: URL structure (where each language lives), hreflang (which version is for whom), sitemaps and metadata (how you tell Google what exists), and duplicate-content handling (how you keep versions from competing with each other).
It is not the same as translation. Translation changes the words on the page; multilingual SEO makes sure those translated pages are crawlable, indexable, and correctly targeted. A site can have flawless translations and broken multilingual SEO โ that's the most common failure mode, and it's invisible until you check your search traffic and find the translated pages get none.
One requirement sits above all four areas: translations must be served server-side. If your pages are translated by client-side JavaScript that swaps text after the page loads, search engines often index only the original language. Real, server-rendered HTML per language is the baseline everything else depends on.
1. URL Structure: Where Each Language Lives
Google supports three URL structures for multilingual sites, and does not support language parameters like ?lang=de for this purpose.
| Structure | Example | Best for |
|---|---|---|
| ccTLD | example.de | Strong single-country targeting, larger budgets |
| Subdomain | de.example.com | Separation, different server locations |
| Subdirectory | example.com/de/ | Most sites โ simplest, consolidates authority |
For most businesses, subdirectories are the pragmatic default: they're the least work and they keep all your ranking authority on one domain instead of splitting it across separate properties. ccTLDs send the strongest geographic signal but mean maintaining separate domains; subdomains sit in between. The full trade-off โ including when a ccTLD is actually worth it โ is in our dedicated guide to subdomains vs. subdirectories.
Whichever you choose, keep it consistent across every page and language. Mixing structures is a signal-diluting mess.
2. hreflang: Telling Google Which Version Is for Whom
The hreflang attribute is how you tell Google which language and region each page targets, so it serves the right version in search results and consolidates ranking signals instead of treating your versions as duplicates. It's the highest-impact part of multilingual SEO, and the most error-prone.
The rules that cause the most problems, per Google Search Central:
- Every version must reference itself and every other version. Missing "return tags" (page A links to B, but B doesn't link back to A) is the most common hreflang error, and it invalidates the whole cluster.
- Use the right codes. ISO 639-1 for language, ISO 3166-1 Alpha 2 for region โ and don't invent combinations.
en-UKis wrong; the code isen-GB. - Add an
x-defaultfor users who don't match any of your specific versions.
Because these tags have to stay reciprocal across every page in every language, maintaining them by hand is where sites break as they grow. The step-by-step implementation โ including the annotated code โ is in our guide to adding hreflang tags. Tools that generate hreflang automatically (Verbi does this as part of its SEO handling) exist mainly to remove this class of error entirely.
3. Sitemaps and Translated Metadata
Two smaller pieces that get skipped and shouldn't:
Translated XML sitemaps. Your sitemap should list every language version so Google can discover them, and it can carry the hreflang annotations too. A sitemap that only lists your original-language URLs leaves the crawler to find the translated pages on its own โ slower, and less reliable on a newer site.
Translated metadata. Title tags and meta descriptions need translating along with the body. They're what shows up in each market's search results, and they're easy to leave in the source language by accident โ a page that reads perfectly in German with an English title tag looks half-finished in the SERP and costs you the click.
4. Duplicate Content Across Languages
A question that worries people more than it should: do translated pages count as duplicate content? Generally, no. Google does not treat genuine translations of a page as duplicate content โ different languages are different content. The problem only appears when versions aren't clearly distinguished (missing hreflang, no distinct URLs), which is exactly what the first two sections prevent.
Where it does get real is within a language โ near-identical pages for en-US and en-GB, or es-ES and es-MX, that differ by a few words. There, hreflang plus meaningful regional differences are what keep them from competing. The full explanation is in our guide to multilingual duplicate content.
The Mistakes That Quietly Kill Localized SEO
Most multilingual SEO failures aren't exotic. They're the same handful of mistakes, and every one is avoidable:
- Don't auto-redirect by IP. Google explicitly warns against automatically redirecting users between language versions based on location. Googlebot mostly crawls from the US, so IP redirects can hide every non-English version from the crawler. Offer a clear, crawlable language switcher instead โ and remember location isn't language (a traveler in Spain may not want the Spanish site).
- Don't rely on client-side translation. JavaScript widgets that overlay translations after load are frequently not indexed. Serve translated HTML.
- Don't use flags for languages. Flags are countries, not languages โ label each option in its own language ("Deutsch," not a German flag).
- Don't ship half-translated pages. Mixed-language pages are poor UX and Google notices. Translate the whole page, metadata included.
- Don't forget to maintain it. Multilingual SEO isn't a one-time setup. Every time you add a page, all its language versions and their hreflang references need to exist too.
How to Implement Multilingual SEO
There are three broad ways to get all of the above in place:
- By hand / in your framework. Full control, and a real maintenance burden โ every new page multiplies the hreflang and sitemap work. Fine for a small, static site; painful as you scale.
- A CMS plugin (on WordPress and similar). Handles much of it inside one platform, tied to that platform.
- A translation proxy. Serves translated pages and generates the SEO structure โ hreflang, sitemaps, subdirectory URLs โ automatically, independent of your stack.
Verbi (verbi.io) is the third kind: it translates your existing site at the DNS level and handles the entire multilingual-SEO layer โ reciprocal hreflang, x-default, self-referencing canonicals, translated sitemaps, and /fr /de subdirectory URLs โ so the error-prone parts above are generated correctly rather than maintained by hand. That's what our SEO features do, and it works the same on Framer, WordPress, Next.js, or a custom site. It's one approach among the three; the right one depends on your stack and how much of this you want to own yourself.
Whatever you use, the test is the same: view-source a translated page and confirm the translated HTML, the reciprocal hreflang, and the translated title tag are all actually there. If they are, your multilingual SEO is working. If they're not, no amount of translation quality will get those pages found.
Frequently Asked Questions
What is multilingual SEO?
Multilingual SEO is optimizing a website that exists in multiple languages so search engines crawl and index each version, rank it in the right market, and don't confuse the versions. It covers URL structure, hreflang tags, translated sitemaps and metadata, and duplicate-content handling. It's distinct from translation: translation changes the words, multilingual SEO makes the translated pages findable.
Does hreflang help SEO?
Yes โ hreflang is what tells Google which language and region version to show each user, and it consolidates ranking signals across versions instead of letting them compete. Missing or non-reciprocal hreflang is the most common reason translated pages rank for the wrong audience or not at all.
Do translated pages count as duplicate content?
Generally no. Google treats genuine translations as distinct content, not duplicates. Problems arise only when versions aren't clearly separated (missing hreflang, no distinct URLs) or when near-identical same-language regional versions compete. Correct hreflang and distinct URLs prevent both.
Should I use subdirectories or subdomains for a multilingual site?
For most sites, subdirectories (example.com/de/) are the pragmatic choice โ they're simplest to run and keep all your ranking authority on one domain. Subdomains and country-code domains (ccTLDs) suit stronger single-country targeting but split your authority and mean more to maintain. See our subdomain vs. subdirectory guide for the full comparison.
Why aren't my translated pages ranking?
The usual causes, in order: translations served by client-side JavaScript that Google doesn't index; missing or non-reciprocal hreflang; IP-based auto-redirects hiding versions from the US-based crawler; or the pages simply being new on a low-authority domain (which time and internal links fix). Check that a translated page's view-source shows real translated HTML and reciprocal hreflang first.
What's the difference between multilingual SEO and international SEO?
They overlap heavily and are often used interchangeably. "Multilingual SEO" emphasizes serving multiple languages; "international SEO" emphasizes targeting multiple countries or regions (which may share a language). The technical toolkit โ URL structure, hreflang, sitemaps โ is the same for both.