multi-language SEO

Multi-language SEO: Targeting Multiple Countries

Featured image: Multi-language SEO: Targeting Multiple Countries
Table of contents

ost multi-language SEO projects fail quietly. Ahrefs studied 374,756 domains and found broken hreflang tags on roughly two thirds of them. Most owners never noticed. Their translated pages simply sat there, unseen.

You pay for translation, wait months, then watch the English page keep ranking. Meanwhile a local competitor takes the market you paid to enter. The translation is rarely the problem. A missing tag, a wrong canonical, or one redirect usually is.

This guide covers how to rank a website in more than one language. You will learn how to choose your first market, pick a URL structure, research keywords in a language you do not speak, and set up hreflang correctly. It also shows you how to fix the most common problem: the wrong language version ranking.

Key Points:

  • Translated pages are not duplicate content, and hreflang does not improve rankings. It only decides which version Google shows.
  • Subfolders like example.com/no/ suit most small sites. They share the authority you have already built, unlike country domains.
  • Start with the market already sending you traffic. Launch one language, prove it, then add the next.
  • Research keywords in each language from scratch. Translated keyword lists miss the words people actually type.
  • Never redirect visitors by IP address. Googlebot crawls from US addresses, so redirects hide your other language folders.
  • Two thirds of sites have broken hreflang tags. Missing return tags and wrong canonicals cause most wrong-version rankings.

What Multi-Language SEO Means

Multi-language SEO: Targeting Multiple Countries
Multi-language SEO: Targeting Multiple Countries

Multi-language SEO is the work of optimising your site so Google shows the right language version to the right person. You are not just translating pages. You are telling search engines which version belongs to which audience.

Most site owners start here because they already see foreign traffic. People land on the English page, read it, then leave without buying. Speaking their language fixes that gap.

Targeting a Language vs Targeting a Country

Language targeting aims at everyone who speaks a language. Country targeting aims at people inside one country. Tag a page es and it serves Spanish speakers everywhere, from Madrid to Mexico City. Tag it es-MX and you have narrowed it to Mexico alone.

Pick language targeting when your offer stays the same across borders. Pick country targeting when prices, shipping, or local rules change.

Four Myths That Cost Small Sites Time and Money

Four myths waste the most budget: Google penalizes translated pages, hreflang boosts rankings, country domains always win, and auto redirects help users.Each one sounds sensible. Each one costs money.

Small businesses feel these hardest. You get one budget and one shot at a second market.

Myth 1: Translated pages count as duplicate content. They don’t. Google has said this repeatedly. The real duplicate risk sits inside the same language, not across languages.

Myth 2: Hreflang improves rankings. It doesn’t. Hreflang picks which version shows after Google decides you rank. Build the page first, then tag it.

Myth 3: A country domain ranks better automatically. A .de or .no sends a strong signal. But Google treats it as a separate site, so you start from zero.

Myth 4: Auto-redirecting by IP helps users. It blocks your indexing. Googlebot crawls from US addresses, so redirects hide your other folders. Show a banner instead.

One more thing worth knowing. Google removed the International Targeting report from Search Console in 2022. Any guide pointing you there is out of date.

Deciding Which Markets to Target First

Start with the market already sending you traffic you never asked for. Open Google Search Console, filter by country, and check the last 12 months. Those visitors found you without any help.

That beats guesswork. If 300 people a month land on your English page from Norway, the demand is already there.

Check four things before you commit:

  • Existing traffic. Search Console country data and GA4 location reports.
  • Search volume. Ahrefs, Semrush, or Google Keyword Planner with the country filter on.
  • Competition. Smaller markets like Norway or Denmark often have weaker competitors than Germany or Spain.
  • Can you serve them? Payment, shipping, and support must work before traffic means anything.

That last point kills more projects than any technical issue. Ranking in Sweden helps nobody if you cannot ship there.

Launch with one language, prove it, then add the second. Most sites wait 4 to 6 months before a new language brings steady traffic.

Choosing Your URL Structure

Multi-language SEO: Targeting Multiple Countries
Multi-language SEO: Targeting Multiple Countries

You have three real options: a country domain, a subdomain, or a subfolder. Subfolders like example.com/no/ suit most small sites. Choose carefully, because switching later means a full migration.

Every language version needs its own URL. Google cannot rank a page it cannot tell apart from the rest.

StructureExampleUpsideDownside
Country domainexample.noStrongest country signal, high local trustStarts at zero authority, costly to run
Subfolderexample.com/no/Shares your existing authority, cheapest to manageWeaker country signal on its own
Subdomainno.example.comAllows separate hosting or a separate CMSGoogle treats it as a semi separate site

Google treats it almost like a separate site.

Skip the fourth option. Google does not recommend URL parameters like example.com?lang=no because they can create duplicate URLs.

Which Structure Is Right for Your Site

Use subfolders unless you have a specific reason not to. They keep every language on one domain, so new pages inherit the authority you already built. Country domains suit bigger brands with local teams, and subdomains suit sites needing separate servers.

One thing most guides skip. Companies often recommend the structure their own product uses, so check what the writer’s site runs on before trusting the advice.

When Two Countries Share the Same Language

Only build separate versions when the pages will actually differ. Two near identical English pages for the US and UK give Google no reason to pick one. It will usually show one and ignore the rest.

If you cannot make real changes, skip the split. One strong page beats two weak copies.

  • Money. Show £, $, or kr, plus the right tax label like VAT or GST.
  • Spelling. Optimise and optimize. Colour and color.
  • Everyday words. Lorry and truck. Holiday and vacation.
  • Contact details. Local address, local phone number, local hours.
  • Local links. Links from .co.uk or .at domains show Google which market you serve.

Doing Keyword Research in a Language You Don’t Speak

Expect smaller numbers. Never translate your keyword list. Research each language from scratch instead. A dictionary gives you the correct word, not the word people actually type. In Spain shoppers search “chaquetas” for jackets. In Mexico they search “chamarras.”

too. A Norwegian keyword might show 90 searches against 20,000 in English. That is proportional, and competition is usually lower.

Translating Your Site the Right Way

Match the effort to the page. Not every page needs the same treatment. A legal disclaimer needs a plain translation. Your homepage needs rewriting for the local reader.

Three levels cover most sites. Straight translation for manuals and terms. Localisation for blog posts and product pages. A full rewrite for homepages and landing pages.

What to Translate Beyond the Visible Page

Most projects translate the body text and forget the rest. Google reads the parts users never see, and those parts often carry your keywords. Check meta titles, URL slugs, alt text, navigation, forms, and structured data before launch.

Where AI Translation Fits

Use AI for the first draft, then have a native speaker review it. Publishing raw output is where sites get into trouble. Machine translation reads fluently, but it misses local search terms, and the cost shows up in bounce rates.

Setting Up Hreflang Tags Correctly

Hreflang tells Google which language version to show each visitor. Every page in the group must list every other version, plus itself. Miss one link and Google ignores the whole set.

Here is a Norwegian and English pair. Both pages carry the same three lines:

html

<link rel=”alternate” hreflang=”en” href=”https://example.com/” />

<link rel=”alternate” hreflang=”no” href=”https://example.com/no/” />

<link rel=”alternate” hreflang=”x-default” href=”https://example.com/” />

You can place these in three spots. The page head suits small sites. The XML sitemap suits large ones. HTTP headers handle files like PDFs. Pick one method and stick to it.

Common Hreflang Mistakes

Broken hreflang is the norm, not the exception. Ahrefs studied 374,756 domains and found errors on roughly two thirds of them. Most owners never notice, because nothing visibly breaks.

Five mistakes cause almost all of it:

  • No return tag. Page A links to B, but B never links back.
  • No self reference. Each page must also list itself.
  • Wrong codes. It is en-GB, not en-UK. Language first, country second.
  • Wrong canonical. A Norwegian page pointing its canonical at the English version deletes itself from search.
  • Missing x-default. Nothing catches visitors who match no version.

Let people choose their language. Never redirect them automatically by IP address. Googlebot crawls mostly from US addresses. Force a redirect and it never reaches your Norwegian or German folders, so those pages stay unindexed.

Show a banner instead, then keep your internal links inside the right folder. A Norwegian page should link to Norwegian pages, never back to the English version.

  • Use real links in your switcher. Plain <a href> tags, not JavaScript dropdowns.
  • Keep it visible. Header or footer, on every page.
  • Skip flag icons. Flags mean countries, not languages. Write “Norsk” and “Deutsch.”

Your Norwegian pages need Norwegian links. Your German pages need German links. A strong .com gives you a base, but local search leans on local sources. One link from a Norwegian trade site beats five generic ones.

Treat each language folder as its own small site. Point the outreach there, skip paid links, and start with local directories, trade bodies, suppliers, and regional blogs.

Measuring Results by Language

Split your data by language folder, or you will not see what is working. A global traffic number hides a failing market behind a healthy one. In Search Console, filter by country, then add a page filter for the folder like /no/.

Watch four things per language: indexed pages, impressions, clicks, and conversions. Also run URL Inspection on a few translated pages. If Google selects the English URL as canonical, your setup has a problem.

When the Wrong Language Version Ranks

Four things cause it: a broken hreflang link, a wrong canonical, no local links, or a page that looks too English. Check them in that order. The first two fix most cases.

A Spanish visitor seeing your English page is the classic symptom. The Spanish page exists, but Google shows the stronger one instead.

Keeping a Multi-Language Site Healthy

Multi-language setups break quietly over time, so crawl your site every month. Someone deletes an English page and the Norwegian hreflang tags still point to it. Nothing looks wrong on screen, but the whole language group stops working.

Run a crawl in Screaming Frog, Ahrefs, or Semrush. Look for broken links, missing return tags, and canonical conflicts inside each language folder. When you remove a page in one language, update the others the same day.

Your Pre-Launch Checklist

Run through these ten checks before your new language goes live. Each one takes minutes now and saves weeks of troubleshooting later.

  • URL structure is consistent. Every page sits in the same folder pattern, like /no/.
  • Hreflang codes are valid. Language first, country second. en-GB, not en-UK.
  • Return tags are in place. Every page links to all versions, including itself.
  • Set the x-default version. One fallback for visitors who match no version.
  • Canonicals point to themselves. No translated page canonicalising back to English.
  • No IP redirects. Test with a VPN from two countries.
  • You translate the metadata. Titles, descriptions, slugs, alt text, and schema.
  • Internal links stay in the folder. Menus, breadcrumbs, and body links.
  • Sitemap includes the new pages. Then submit it in Search Console.
  • Language differences split the tracking data. Search Console and GA4 filtered by folder.

FAQs

What is the difference between multi-language SEO and international SEO?

Multi-language SEO targets languages, while international SEO targets countries. A Spanish page tagged es reaches Spanish speakers anywhere, but a page tagged es-MX targets Mexico specifically.

Do I Need Hreflang for a Two-Language Website?

Yes, hreflang is worth adding even for two languages. Without it, Google may show your English page to Norwegian searchers who would convert better on the Norwegian version.

Which URL structure should a small business choose?

Subfolders like example.com/no/ suit most small businesses. They keep every language on one domain, so new pages inherit the authority you already built instead of starting from zero.

Why is my English page ranking in Germany instead of my German page?

The usual causes are a missing hreflang return tag or a canonical pointing back to the English URL. Check both before assuming the German page needs more content.

Is it worth adding a second language if the market is small?

Yes, when search volume is proportional and competition is low. A Norwegian keyword might show 90 searches against 20,000 in English, but far fewer sites compete for it.

Conclusion

Multi-language SEO works when you get three things right: a clear URL structure, correct hreflang tags, and content written for the local reader rather than translated at them. Start with the market already sending you traffic, launch one language, and prove it before adding another.

Most problems trace back to the same few causes. Broken return tags, a canonical pointing home, or an IP redirect blocking Googlebot. Check those first, crawl your site monthly, and split your reporting by language folder so a weak market never hides behind a strong one.

Run the pre-launch checklist above before your next language goes live.

Need a hand with this?

I do this work for a small number of clients each quarter. A 30-minute call is free and you'll get three specific fixes whether or not we work together.

Book a Free Strategy Call

Usama Habib

Usama Habib

AI SEO Specialist & SEO Consultant. I help businesses win visibility in Google and in AI search, and I publish everything I learn as complete topical maps.

Free 30-min strategy call 3 fixes, whether you hire me or not
Book