International SEO
International SEO is the practice of optimizing a website so search engines can serve the right language or country version to users in different markets.
Start here
- Start with one market you understand well, not five at once.
- Use hreflang tags and a clear URL structure (ccTLD, subdomain, or subdirectory).
- Do local keyword research — don't just translate your home market keywords.
- Create or adapt content for each market; avoid verbatim copies.
- Build local links and signals to reinforce targeting.
I've made the mistake of jumping into five markets at once. Don't.
What I'd do first
- Pick one market you know something about — language, culture, search behavior. Don't launch in five countries because your boss saw a map.
- Set up a clear URL structure. I prefer subdirectories (example.com/de/) for most sites because they're easier to manage and keep link equity. ccTLDs (.de) are stronger but a pain for maintenance.
- Install hreflang tags on every page variant. Use the correct ISO language and country codes (de-de, es-mx). Test them in Search Console.
- Do local keyword research. Open Google Trends for that country, search in the local language, look at autocomplete. Don't translate your US keywords — you'll miss intent.
- Create or adapt content for that market. If you're copying the English page and swapping words, you're not doing international SEO. You're doing lazy translation.
Plain-English take
International SEO is about telling Google: "This page is for people in France who speak French, this one is for Canada-French, and this one is for Canada-English." You do that with hreflang tags in your HTML or sitemap, plus a URL structure that makes it obvious. The hard part isn't the tags — it's the content. You can't just run everything through Google Translate and call it a day. Each market has its own search habits, slang, and expectations. A keyword that works in the UK might be useless in Australia, even though both speak English.
How it shows up
When it works: you search for a product in German on google.de, and your German page ranks. When it doesn't: Google shows the English page to a French user, or worse, treats all your language versions as duplicates and ranks none. I've seen sites where the US version outranks the UK version in Google UK because they didn't use hreflang. The fix was adding the tags and building a few UK-specific links. Within weeks, the UK page started appearing.
Tradeoffs
The big one: ccTLDs vs subdirectories. ccTLDs (.fr,.de) give a strong country signal but split your domain authority across multiple domains. Subdirectories keep everything on one domain but rely more on hreflang. I lean toward subdirectories for most projects because they're simpler to maintain and you don't lose link equity. But if you're in a market where users trust local domains (like.jp in Japan), ccTLDs might be worth the hassle.
Another tradeoff: how much to localize. Full localization (new content, local writers, local links) performs best but costs time and money. Minimal localization (translated content, same structure) gets you in the door but rarely ranks as well. I've done both. The sweet spot is usually adapting 30-50% of the content — product pages can be similar, but blog posts and guides need local flavor.
What I got wrong
Early on, I thought hreflang was a set-it-and-forget-it thing. It's not. You need to maintain it as you add or change pages. I also assumed that if two countries share a language (Spain vs Mexico), I could use one Spanish version. Wrong. Search behavior differs — "coche" vs "auto" in Spain vs Mexico. Now I create separate pages with separate hreflang tags for each country-language pair. Also, I used to launch in too many markets at once. Spreading thin means none of them get enough content or links. Better to nail one market, then expand.
Next step
Quick answers
Do I need a separate domain for each country?
Not necessarily. You can use subdirectories (example.com/fr/) or subdomains (fr.example.com). ccTLDs (.fr) are strongest but more work. Pick what fits your resources.
Is hreflang required?
If you have similar content in multiple languages or countries, yes — it prevents duplicate content issues and helps Google show the right version. Without it, you risk confusion.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central — Primary guidance on international targeting, hreflang, and language/country versions.
- Moz International SEO Guide — Clear practical definition and implementation overview for country and language targeting.
- Search Engine Journal — Useful for market-selection and implementation considerations, including Google Search Console and hreflang.
Notes from Callum Bennett.