November 11, 2026
International SEO is the work of making one organization's content rank in multiple countries or languages without the versions fighting each other in search. The short answer: pick a URL structure you can live with, tell search engines which version serves which audience, and resist the urge to auto-translate your way into a market.
Most sites that struggle here did not fail at translation. They failed at signals. Google indexed four near-identical pages, guessed wrong about which one to show in Germany, and split the authority across all of them. This article covers the decisions that avoid that: domain structure, targeting signals, hreflang, and the content calls that decide whether a market is worth the effort.
Decide what you are targeting: language, country, or both
Start by naming the axis. Targeting a language (Spanish speakers anywhere) is a different job from targeting a country (users in Mexico). Most real sites do both, and conflating them is the first mistake.
- Language targeting serves the same content to everyone who reads that language, regardless of location. Good for software docs, global brands with one product.
- Country targeting serves different content, currency, shipping, or legal terms by location. Required for ecommerce and anything with regional pricing or compliance.
The distinction drives everything downstream. A site targeting es (Spanish, no region) needs one Spanish version. A site targeting es-MX, es-AR, and es-ES needs three, each justified by content that actually differs. If the only difference is a currency symbol, you probably want one Spanish page and a market selector, not three thin duplicates.
Write down, per market, what is genuinely different: language, currency, product availability, legal copy. If nothing is different, do not build a separate version.
Choose a URL structure before you build anything
Your URL structure for international targeting is close to permanent. Changing it later is a full migration, so decide with that cost in mind.
| Structure | Example | Geotargeting | Effort | Authority |
|---|---|---|---|---|
| Country-code domain (ccTLD) | example.de | Strong, automatic signal | High: separate domains to run | Split across domains |
| Subdomain | de.example.com | Set manually in Search Console | Medium | Partly separate from root |
| Subdirectory | example.com/de/ | Set manually in Search Console | Low | Consolidated on one domain |
| URL parameter | example.com?lang=de | Not recommended | Low | Weak, hard to target |
Subdirectories on a single domain are the default choice for most teams because new markets inherit the root domain's authority and you run one site. ccTLDs send the strongest country signal and can help trust in markets that distrust foreign domains, but each one starts its authority close to zero and multiplies your technical and link-building work.
Avoid language parameters. They are hard to geotarget and easy to index badly. If you have inherited a parameter-based setup, moving to subdirectories is the kind of restructure an SEO Migration plan exists for, and it needs a redirect map before anything ships.
Signal targeting with hreflang
Hreflang tags tell Google which version of a page serves which language and region. They do not change rankings directly. They change which of your existing versions appears for a given user, which stops the wrong-country page from showing and reduces duplicate-content confusion.
An hreflang set is a cluster. Every page in the set lists every other page, including itself, and the tags must be reciprocal. If the English page points to the German page, the German page has to point back. One-directional tags are ignored.
<link rel="alternate" hreflang="en-us" href="https://example.com/us/page" />
<link rel="alternate" hreflang="de-de" href="https://example.com/de/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page" />
The x-default entry is the fallback for users who match no listed version. Point it at your market selector or your primary-language page.
Where hreflang goes wrong
Hreflang breaks in predictable ways. These are the failure modes to check first:
- Missing return tags.The most common error. Use Search Console to find it, and expect to fix it in batches rather than once.
- Wrong region codes.Use ISO 639-1 for language and ISO 3166-1 Alpha 2 for country. It is
en-gb, noten-uk. UK is not a valid region code. - Pointing at non-canonical or redirecting URLs.Every hreflang URL must be the canonical, live, 200-status version. A tag pointing at a redirect is dropped.
- Hreflang contradicting canonical.If a page's canonical points to a different-language version, you have told Google to ignore the page entirely. Each language version should self-canonicalize.
For large catalogs, hand-maintaining hreflang in the head does not scale. Submit it in an XML sitemap instead. Either way, treat hreflang as part of your Technical SEO workload, not a one-time setup.
Translate for intent, not for words
Machine-translated pages rank poorly and convert worse because they miss how people actually search in each market. Keyword research has to be redone per language. The literal translation of your best English term is often not what native speakers type.
Do the research in-market. Pull the real query set from Search Console's Performance report filtered by country, and validate terms with someone who speaks the language natively. A term that is high-volume in one Spanish-speaking country can be niche or even wrong in another.
This is where cheap internationalization dies. Auto-translation produces grammatically passable pages that target no real search intent, so they earn no clicks, and thin duplicate versions can drag on the rest of the site. Budget for human review of the pages that matter, and let the long tail wait. If you are scaling many near-identical templated pages across markets, that is a Programmatic SEO problem with its own quality controls, not a reason to skip the human pass on your core pages.
Build authority per market
Links and trust do not transfer cleanly across borders. A .com with strong US backlinks does not automatically rank in France just because you added /fr/. Each market needs its own local signals over time.
That means local links, local press, local business presence, and for query-by-location searches, the local-pack mechanics that overlap with Local SEO. Set the right language and region, host content that matches what that market searches for, and earn references from sites in that country. There is no shortcut. New-market rankings build slowly, and anyone promising a timeline is guessing.
Frequently asked questions
What to do next
Pick one market where you already see impressions in Search Console but no dedicated content, and treat it as a pilot: one URL structure decision, one correctly reciprocal hreflang set, and real in-market keyword research for a handful of core pages. Prove the mechanism on a small surface before you roll it across every language.
If you want the structure and targeting mapped against your own site before you build, that is where an SEO Audit earns its keep.

