I’ve spent 20+ years helping companies grow traffic across borders, and one mistake stands out above all others: teams translate their site and call it an international strategy.
Translation is not a strategy. It’s a task.
The real decision comes first: do you organize your site by language, or by country? Get that wrong and you’ll fight your own architecture for years. Rankings suffer, local teams get frustrated, and the CMS becomes a mess nobody wants to touch.
Here’s how I walk clients through the choice.
Two Approaches, Two Different Problems
A multilingual site organizes content by language. English speakers see English pages, French speakers see French ones. The offer stays consistent worldwide. Think /en/, /fr/, /es/ folders on one domain.
A multiregional site targets countries. Germany gets its own experience, with local pricing, legal disclaimers, promotions, and cultural adjustments. Sometimes that means domain.de or /de-de/ folders, and often multiple languages within a single market.
They look similar from the outside. Under the hood, they solve different problems. Language targeting answers “can my audience read this?” Country targeting answers “does this fit how people in this market buy, and what local law requires?”
When Multilingual Is the Right Call
Choose a language-first structure when:
- Your product and pricing stay the same everywhere
- You’re reaching audiences who share a language across borders (Spanish speakers in 20+ countries, for example)
- One central team manages all content
- You want lower CMS overhead and a single site to maintain
The upside is reach with modest complexity. About 70% of the world doesn’t speak English. A well-built multilingual site opens those markets without multiplying your operations.
Ahrefs took this path, expanding into 12 languages after recognizing that only around 20% of internet users worldwide read English. One platform, many tongues.
When Multiregional Wins
Go country-first when the market itself changes your offer. Signals include:
- Products, pricing, or availability differ by country
- Local laws force different disclaimers, cookie policies, or compliance messaging
- Regional teams need to run their own promotions and edit their own content
- You want ccTLDs like example.de to build local trust
Amazon runs country-specific domains for a reason. Their German catalog, pricing, and regulations differ from France. A language switcher can’t handle that.
The catch: Most companies don’t have the capacity, and that gap is where ccTLD strategies fall apart. Fragmented authority, higher tool costs, more governance headaches.
My take: if you can’t fund unique content and dedicated management per country, stay away from ccTLDs. Subdirectories with proper hreflang get you most of the benefit at a fraction of the cost.
The Question That Decides It
Strip away the technical debate and ask one thing: does your offer change by country?
If no, build multilingual. If yes, build multiregional. If partly, use a hybrid, with language folders as the base and country versions only where law or product differences demand them. That last option is what I recommend for most mid-sized companies going global.
Then answer three follow-ups honestly:
- Can local teams actually maintain regional content, or will pages go stale?
- Do you have the SEO resources to manage hreflang across every version?
- Will your CMS support the structure without duct tape?
Weak answers here should push you toward the simpler setup. An honest multilingual site beats a neglected multiregional one every time.
Hreflang: Where Both Strategies Live or Die
Whichever path you take, hreflang tags tell Google which version to show each user. Misconfigure them and you get duplicate content flags, wrong-country rankings, and pages cannibalizing each other.
The errors I see most often:
- Translating keywords instead of researching how locals actually search
- Serving region content through cookies or JavaScript on a single URL, which crawlers can’t see
- Relying on machine translation for pages that carry your brand voice
- Missing return tags, so hreflang pairs never validate
None of these are exotic. They’re basic hygiene that most teams skip because nobody owns international SEO.
What I’d Do Monday Morning
Audit your current structure against your actual business model. List every market you serve, note whether the offer differs there, and map that against your URL setup. Mismatches between the two are where you’re leaking traffic and trust.
I broke this down in full, with case studies from Netflix, Airbnb, Amazon, and Booking.com, on the International Web Mastery blog. Bill Hunt and I also cover domain structures, geolocation signals, and hreflang implementation on the International Web Effectiveness Podcast.
Full guide: Multilingual vs Multiregional SEO