Multilingual SEO is the work of making each language version of a website rank for people searching in that language. It covers separate URLs per language, research in each language, translation quality and connecting the versions so Google shows the right one.
By Kristijan GjorgjioskiIndependent SEO consultantPublished 18 October 2026 · 6 min read
Translating your website is the easy part. Getting each language to rank is where most sites stall.
I see the same pattern again and again.
You launch a Spanish or German version, wait six months, and find the new pages barely get impressions.
The translation was fine. The multilingual SEO wasn't there.
In this guide, you'll learn what multilingual SEO is, how Google actually reads languages and the seven steps I follow to make each language version earn its own traffic.
Multilingual SEO is the practice of making each language version of a website discoverable and relevant to people searching in that language, through separate URLs, native-language research and quality translation.
Here's a simple example.
Say you run a Dutch software company with an English site that ranks well.
You add a Dutch version. Multilingual SEO is everything that makes your Dutch pages rank for Dutch searches, rather than sitting in the index unseen.
Google draws a clear line between the two.
In its guide to multi-regional and multilingual sites, a multilingual site is any website that offers content in more than one language. A multi-regional site explicitly targets users in different countries.
| Multilingual | Multi-regional | |
|---|---|---|
| Targets | Languages | Countries |
| Example | A Belgian site in Dutch and French | A UK and an Irish site in English |
| Main challenge | Translation, research and language signals | Currency, delivery and country signals |
| Hreflang codes | Language only, such as fr | Language plus region, such as en-ie |
Plenty of sites are both.
A brand selling in Germany, Austria and France is multilingual and multi-regional at once.
It isn't just translation.
A word-perfect translation of the wrong keywords still ranks for nothing.
It isn't just hreflang either.
Hreflang connects your versions; it doesn't make any of them relevant. My guide to what hreflang is covers the tag itself in detail.
And it isn't a structure decision.
Whether your languages live in folders, subdomains or separate domains is a separate question, answered in my ccTLD vs subfolder vs subdomain comparison.
Because each language competes in its own search results, against its own local competitors.
Google says it uses the visible content of a page to determine its language.
It doesn't rely on your lang attribute or your URL.
So a page with German body copy, an English menu and English image alt text sends mixed signals. You think you've published a German page.
Google sees a blend.
People don't search in dictionary language.
A literal translation of your English head term often isn't the phrase locals use.
Sometimes they use an English loanword. Sometimes a regional term. Sometimes a completely different framing of your problem.
That's why I treat each language as its own keyword research project, never a translation job.
Google's spam policies list scaled content abuse as a violation.
One example is generating many pages through automated transformations, including translating, where little value is provided to users.
Machine translation as a first draft is fine.
Hundreds of unedited pages nobody on your team has read are a different matter.
Google's documentation sets out a handful of rules that shape every multilingual build:
That last point matters.
Translating only the menu and footer while the main content stays in English doesn't create a new language version in any useful sense.
This is the order I work in on multilingual projects.
Start with your own data, not a wish list.
In Search Console, look at queries that aren't in your main language, and at countries sending impressions you never targeted.
Check your enquiries and orders too.
If people already find you in a language you don't support, that's your strongest first candidate.
Each language version needs a crawlable address of its own, such as /fr/ or /es/.
No cookie switches. No JavaScript toggles that swap text on one URL. No redirects based on browser language.
Then confirm every new version is actually indexable.
On one translation and interpreting site I worked on, a batch of new language pages had been told to stay out of search entirely. The full story is in this language services case study.
Work with a native speaker and check the live results in each language yourself.
Look at which terms competitors use in their titles, which questions appear in the results and whether people use English terms for your product.
The output should be a keyword-to-page map for each language. My guide to keyword research for a service business shows the method, which works the same in any language.
Use whatever drafting method suits your budget, including machine translation.
Then put a native speaker between your draft and the publish button.
Brief them on:
A translator who knows the keyword map writes titles and headings that match real searches.
Go through every element of a translated page, not just the body copy:
Mixed-language pages are the most common fault I find, usually in templates nobody thought to translate.
Add hreflang so Google knows which of your pages are equivalents.
My free hreflang generator builds the full reciprocal set from a list of URLs.
Then add a visible language selector that links to the same page in each language, not to each homepage.
Google itself suggests linking to the other language versions of a page.
I label each option in its own language, such as Deutsch and Français, so people can find theirs.
A strong English section can hide a failing Spanish one in blended totals.
Filter Search Console by page folder for each language.
In analytics, segment by language version, which a clean GA4 setup makes simple.
Check three things monthly: impressions per language, whether the right language version is the one ranking, and enquiries from each.
Not every multilingual site is international.
Canada, Switzerland, Belgium and Wales all have businesses serving one country in two or more languages.
The rules above still apply to you, with one difference: your hreflang can use language-only codes, because the country doesn't change.
One business I worked with, a pet relocation company in Central America, publishes every page in both Spanish and English for pets moving into or out of one country. You can read how that played out in the bilingual pet transport case study.
The work is the same: separate URLs, native research and one language per page.
Pick your most valuable page and check its translated version today.
Is every element in one language? Does it have its own URL, its own researched keyword and a hreflang set pointing both ways?
Fix that one page, then roll the same standard across your site.
Before you add another language, run through my international SEO checklist. And if you'd like the research, structure and hreflang handled together, here's how my international SEO consulting works, including multilingual site reviews for sites that already have languages live.
Multilingual SEO is about languages: making a German page rank for German searches, wherever the searcher is. International SEO is the wider job of targeting countries, which adds currency, delivery, legal differences and country-level structure such as ccTLDs. A Swiss site in German and French is multilingual but single-country. A UK and US site is multi-regional in one language.
Not in itself. Google's spam policies target scaled pages that add little value, including content generated through automated translation. A machine draft that a native speaker edits, with keywords researched in that language, is a normal workflow. Publishing hundreds of raw machine translations nobody has read is the risk, both for rankings and for the visitors who land on them.
It is strongly recommended whenever you have equivalent pages in different languages. Hreflang tells Google which pages are translations of each other, so it can show a Spanish searcher the Spanish version. It removes the guesswork, but it does not replace good translation or separate URLs.
Where your platform allows it, I translate slugs into the page's language, because the URL appears in results and native speakers read it. Google says it does not use the URL to detect language, so this is mainly for users. Keep the language folder, such as /de/, consistent, and use ASCII-friendly versions of accented words if your system handles them badly.
About the author
Kristijan Gjorgjioski
Independent SEO consultant · 6+ years in SEO · 60+ client websites worked on
I'm an independent SEO consultant with 6+ years in SEO. I run audits, migrations and content programmes for businesses in Europe, the UK and the USA, and I build the automation behind my own research.
Book a free 30-minute call. I look at your site first and tell you plainly what I would fix, and in what order.