Technical SEO · guide 3 of 7
Multilingual websites: reach customers in every language without confusing Google
How to add languages or countries to your site the right way: which URL structure to pick, how hreflang really works, why raw machine translation is risky and the local details that win trust.
23 min readUpdated 9 Nov 2026
- 11 questions to test yourself
- 1 calculator
- 13-item checklist
On this page8 sections
You added a Spanish version. Why does Google still show Spaniards the English one?
You paid for a Spanish translation, switched on a language plugin and waited. Months later, customers in Madrid still land on your English page, or find nothing at all. No error, no warning. The translation was never the hard part; telling Google which version is for whom was.
By the end you will know whether you need language or country versions, which URL structure fits a small business, how to set up hreflang (the code that links your language versions together) so Google trusts it, and how to make a translated page read as if a local wrote it.
There is also one line of code, often written by a plugin rather than a person, that quietly tells Google to ignore the translations you paid for. Near the end you will hunt for it in a real-looking page source, and then in your own, in a couple of minutes.
First, a question most people get wrong. The answer shapes everything else.
Quick quiz
You publish a page in Spanish. What does Google use to decide that the page is in Spanish?
Pick one. Your first answer is the one that counts.
Language or country: decide what you are actually targeting
Before any code, answer one question: are you serving people who speak a language, or people who live in a country? They are different jobs.
A translation agency in Valencia that wants English-speaking clients anywhere is targeting a language: one English version is enough. An online shop that ships to the UK and Ireland, with different prices, delivery times and VAT, is targeting countries: it may need en-GB and en-IE versions even though both are in English.
Most small businesses only need language versions. Country versions earn their keep only when something real changes between countries. Two English pages that differ only in the flag at the top give Google two near-identical pages and give you twice the upkeep. Not sure which you are? Score your own business.
Score yourself
Language versions or country versions? Score your business
Think of the country you want to add and compare it with your main market.
Prices or currency are different there
Delivery times, shipping costs or returns are different
Tax, legal terms or the information you must show are different
You sell a different range of products or services there
You have a real address, staff or a partner in that country
0 of 5 answered. Answer them all to see your result.
Test yourself
hreflang codes: guess what each one means, then flip
Think of your answer, then flip the card.0 of 7 flipped
Pick a URL structure you will not regret in three years
Google’s documentation on multi-regional and multilingual sites asks for one thing above all: give each language version its own URL. Do not show different languages on the same address by reading a cookie or the visitor’s browser settings, because Google may only ever see one of them.
That leaves three sensible options. Each one works; they differ in cost, effort and how strongly they say “this is for one country”.
Side by side
| Question | Country domain | Subdomain | Subfolder |
|---|---|---|---|
| Looks like | example.de | de.example.com | example.com/de/ |
| Says “this is for one country” | Strongly. A country domain is a clear country signal | No more than a subfolder does | No more than a subdomain does; hreflang does that job |
| Setup and running cost | Highest: several domains, renewals, sometimes local registration rules | Medium: one domain, but each subdomain often needs its own setup | Lowest: one domain, one site, one hosting plan |
| Where links and reputation build up | Split across separate sites | Partly split, depending on how your platform runs it | All on one domain |
| Good for | Businesses with a real operation in each country | Versions that genuinely need separate systems | Most small businesses adding languages |
What would you do?
A guesthouse picks a structure
This is an illustrative example: the guesthouse is made up. It is in Bansko, Bulgaria, and its site is in Bulgarian. Most bookings come from Bulgaria, the UK, Romania and Greece.
The owner has a modest budget and runs the site herself on WordPress.
How should she add the new languages?
hreflang without the headache
hreflang is a small annotation that says: “this page also exists in these languages, at these addresses”. It helps Google show a searcher in Vienna your German page rather than your English one. It is a hint, not a command, and Google only trusts it when the whole set is complete and consistent.
You can add it in three places: as link elements in the head of each page, as HTTP headers (useful for PDFs) or in your XML sitemap. Pick one method and stick to it. Most WordPress, Shopify and Wix multilingual setups write it for you, which is fine, as long as you check what they write. If you have not picked a platform yet, the guide on WordPress, Shopify, Wix or custom shows how to test its multilingual support before you commit.
Step by step
Build an hreflang set, one step at a time
Step 1 of 6
List every version of one page
Illustrative example: a tile shop has the same product page in three languages: example.com/en/tiles/, example.com/es/azulejos/ and example.com/de/fliesen/. Notice the slugs are translated too; that is fine and reads better.
Make a guess
The tile shop’s page exists in English, Spanish and German, plus an x-default. Across all three pages, how many hreflang lines are there in total?
With that many lines, one going missing is easy. Which leads to the most common hreflang bug of all.
Quick quiz
The Spanish page lists en, es and x-default. The English page lists only en and x-default. What is the likely result?
Pick one. Your first answer is the one that counts.
Translation: why machine-translating and hoping is risky
Machine translation has become very good, and it is a fine first draft. The risk is publishing it unread. The tool does not know your prices, your opening hours, your tone or what a customer in another country needs to hear before they trust you.
Translate the main content, not just the menu. Google’s documentation warns that translating only the template, the buttons and navigation, while the body stays in one language, makes a confusing page. Also keep one language per page: side-by-side translations on the same page make it harder for Google and for people to tell what the page is.
Before and after
A Valencia dental clinic’s opening paragraph in English
Translated literally
Ask for your hour. We attend from Monday to Friday of 9 to 14 and of 17 to 20 h. Revision from 40 €. Call to 961 23 45 67.
Written for an English speaker
Book an appointment online or by phone. We are open Monday to Friday, 9am to 2pm and 5pm to 8pm, Spanish time. Check-ups from €40. Call +34 961 23 45 67; our reception team speaks English.
- “Revision” is a false friend: revisión means a check-up. Literal tools and non-native writers trip on these.
- Times, prices and phone numbers follow the reader’s conventions, and the number has the country code someone abroad needs.
- It answers the question every foreign customer has: will anyone understand me when I call?
- This is an illustrative example: the clinic is made up.
The other trap is keywords. People in different countries do not just speak differently; they search differently. A computer is an ordenador in Spain and usually a computadora in Mexico. A British client looks for a solicitor, an American for a lawyer or an attorney.
So do not translate your keyword list. Do the keyword research again in each language, with a native speaker, and let them choose the words customers there type. The keyword research guide for beginners walks through the method; run it once per language.
Try the numbers
How much translation would you need to check?
Words to translate and review
20,000 words
Review time
about 33 hours
Review time per language
about 17 hours
Your own numbers, not a quote. If the per-language time is more than your reviewer can give in a month, launch one language first or start with your most-visited pages, then add the rest.
Local signals that make a version feel native
Translated words get you understood. Local details get you trusted, and several of them are also clues Google uses to tell which country a version is for. Go through each version as if you were a customer from there.
- Prices in the local currency, with tax shown the way people there expect it.
- A phone number with the country code, and the hours in the visitor’s time zone or clearly labelled with yours.
- A real local address, if you have one, and a Google Business Profile for each real location.
- Dates, units and sizes in local formats: 9 November 2026 or 11/9/2026, centimetres or inches.
- Payment and delivery options people in that country actually use.
- Reviews, case studies or client names from that market, where you have them.
- Mentions and links from local sites: a chamber of commerce, a local directory, a partner in that country.
Myth or fact?
Myth or fact?
1.The English and Spanish versions of the same page count as duplicate content.
2.Automatically redirecting visitors by their IP address is the safest way to give them the right language.
3.A country domain such as .de tells Google a site is meant for Germany.
4.Even with perfect hreflang, Google may sometimes show your English page to a Spanish speaker.
5.You must host your site on a server in each target country.
6.Search Console has a setting where you choose your target country.
The mistakes that quietly break multilingual sites
None of these throw an error message. Pages just fail to appear in the right country, and nobody notices for months. Start with the one we promised at the beginning: can you find it in a page’s source?
What would you do?
Spot the bug in the page source
Illustrative example: this is part of the head of the tile shop’s Spanish page, https://example.com/es/azulejos/.
Line 1: hreflang="en" href="https://example.com/en/tiles/". Line 2: hreflang="es" href="https://example.com/es/azulejos/". Line 3: hreflang="de" href="https://example.com/de/fliesen/".
Line 4: hreflang="x-default" href="https://example.com/en/tiles/". Line 5: rel="canonical" href="https://example.com/en/tiles/".
Which line quietly stops the Spanish page from showing in Spanish searches?
The canonical is the quietest bug. These are the others that turn up again and again:
- Return links missing, often after one language version gets a new page that the others never link back to.
- Wrong codes: en-UK, gr, jp, or uk for British English.
- The language switcher links every language to the homepage instead of to the same page in that language.
- The switcher uses flags. A flag is a country, not a language: which flag means Spanish, or English? Write each language in its own words: Deutsch, Español, Ελληνικά.
- Half-translated pages: a translated menu over an English body, or an English checkout after a Spanish product page.
- Translations that are never updated, so the German page still shows last year’s prices.
To see this bug at shop scale, read the Wasm Camel Dairy case study on this site. It is illustrative, an invented camel-milk dairy near Riyadh with modelled figures, but the fault is the one you just found: Arabic product pages with no hreflang, which Google treated as duplicates of their English twins. The fix was the same two lines per page, a self-referencing canonical and a full hreflang set.
Your multilingual checklist
Tick off what is already true. What is left is your plan, in roughly the order it matters. Most owners find two or three gaps, usually the canonical, a missing return link or a translation nobody has reviewed.
Checklist
Before and after you add a language
Saved on this device only
Questions people ask
Do I need hreflang if I only have two languages?
Google can usually tell languages apart from the text alone, so two clearly different languages will often work without it. hreflang still helps Google show the right one, for example when someone searches your brand name, and it matters most for same-language versions such as en-GB and en-US.
Should my main language sit at the root or in its own folder, like /en/?
Either works. What matters is consistency and that the switch is not done later in a hurry, because changing URLs on a live site is a migration with its own risks. If you do have to move, the guide on moving or redesigning a site without losing your Google traffic covers the redirects.
Can I use AI or machine translation at all?
Yes, as a draft. Then have a fluent speaker, ideally from the market you are targeting, review and correct every page before it goes live. Publishing unreviewed machine output at scale is the part Google’s spam policies warn about.
Should I still set the lang attribute?
Yes. Google does not use it to detect language, but browsers, translation tools and screen readers do, so it helps real visitors.
Will adding languages bring me more traffic?
It can open your business to searches you were invisible for, but nobody can promise rankings or traffic in any language. A well-built version removes the technical reasons not to show you; the content and the local market decide the rest.
The canonical bug you hunted is one case of a wider question: when Google finds several addresses that look alike, which one does it keep? The next guide in this series, on duplicate content and canonicals, answers it for the rest of your site, from www and non-www addresses to filter URLs.
And if a translated page still is not on Google a few weeks after you fixed it, the guide on why a page isn't on Google lists the twelve usual causes and how to check each one.
You reached the end
Your summary
This guide has 11 quick questions
Try them to see how much you already know. Your first answer is the one that counts.
Technical SEO: 0 of 7 read
- 1. Why isn't my page on Google? 12 causes and fixes: not read yet
- 2. Schema markup: what it does and which types a small business needs: not read yet
- 3. Multilingual websites: reach customers in every language without confusing Google: this guide, not read yet
- 4. Duplicate content and canonicals: what Google really does with copies: not read yet
- 5. Image SEO: faster photos that Google can find and understand: not read yet
- 6. Moving or redesigning a site without losing your Google traffic: not read yet
- 7. Core Web Vitals explained without the jargon: not read yet
0 of 57 guides read · Saved on this device only
New guides by email when they are published.
Unsubscribe in one click.
What to do next
- Use your self-check result to decide between language versions and a country version, and write down what actually changes between the markets.
- Open one translated page, view the source and check that hreflang lists every version, including itself, and that the canonical points to the page itself.
- Ask a fluent speaker to read your three most important translated pages aloud and mark anything a local would not say.
- Run a free SEO check on one page in each language to catch missing tags and blocked pages.
Check your own site
Run our free site check: most of the technical points above, in under a minute.
Run the free checkNext in Technical SEO
Technical SEO
Duplicate content and canonicals: what Google really does with copies
One page on your site can answer to eight different addresses. That is not a penalty, but it does mean Google is choosing the main one for you.
26 min readStart reading
See it applied in an illustrative case study
Invented businesses and modelled figures, not client results: how the work in this guide fits into a whole engagement.
- Signal · 16 monthsIllustrative+130% visits from search, 91% of species pages indexedFlorhaven Glasshouse Trust
How a Victorian glasshouse got its 12,000-species database back into search
Botanical garden & plant database · Ghent · Europe
- Signal · 8 monthsIllustrativeIndexed location pages 18% → 91%Fryline Kitchens
How a delivery-kitchen operator fixed 1,100 broken location pages across 6 brands
Multi-brand delivery kitchen operator · Manchester · UK & Ireland