International SEO has a reputation for being fiddly, and it's earned, hreflang alone is famously easy to break. But the fiddly parts aren't where projects fail. Projects fail on three structural decisions made before a single tag is written: where the market versions live, whether the content is localized or merely translated, and whether each market gets enough depth to earn authority on its own.
Get those right and hreflang becomes bookkeeping. Get them wrong and you end up with the classic international graveyard: six half-translated site versions cannibalizing each other, none with enough content to rank, and a hreflang implementation nobody can debug.
This guide covers all four layers in order: site structure, hreflang implementation (with working code), translation vs localization, and building per-market topical authority.
ccTLD vs subfolder vs subdomain
Your first decision is where international versions live. There are three options, and the trade-off is always the same: geo-targeting strength vs authority consolidation.
| Structure | Example | Strengths | Weaknesses |
|---|---|---|---|
| ccTLD | example.de | Strongest country signal; local trust and CTR; legal separation | Each domain builds authority from zero; highest cost and maintenance |
| Subfolder | example.com/de/ | Inherits root domain authority; one site to maintain; easy analytics | Weaker inherent geo signal (fix with hreflang + local signals) |
| Subdomain | de.example.com | Team/infrastructure separation when required | Authority consolidation weaker than subfolders with none of a ccTLD's trust benefits |
For most businesses the answer is subfolders. Authority is the scarcest resource in SEO, and splitting it across multiple domains means fighting every competitive battle with a fraction of your strength. The exceptions are real but narrow: you're a household name in a market that strongly prefers local domains (common in Germany and Japan), regulations force separation, or you're acquiring an established local ccTLD with its own equity.
Target languages or countries, decide which
A /de/ folder can mean “German speakers everywhere” or “the German market”. If you sell identical things at identical prices across DACH, target the language once (de). If pricing, shipping, or product lines differ by country, target countries (de-DE, de-AT, de-CH) and accept the near-duplicate content between them, that's exactly the situation hreflang exists to handle.
hreflang: implementation that actually validates
hreflang annotations tell Google which URL is the right version of a page for a given language or language-country pair. Two things people get wrong conceptually: it's a page-level, pairwise annotation (not a sitewide setting), and it's a swap signal, not a ranking signal, it decides which of your equivalent pages appears, not whether you rank at all.
The three implementation routes are HTML link tags in the head, HTTP headers (for PDFs and non-HTML), or XML sitemap annotations. Sitemap implementation scales best for large sites; head tags are easiest to audit. A correct head-tag cluster for a page with US English, UK English, German, and a default fallback looks like this:
<link rel="alternate" hreflang="en-us"
href="https://example.com/products/desk/" />
<link rel="alternate" hreflang="en-gb"
href="https://example.com/uk/products/desk/" />
<link rel="alternate" hreflang="de"
href="https://example.com/de/products/schreibtisch/" />
<link rel="alternate" hreflang="x-default"
href="https://example.com/products/desk/" />Every one of these rules is load-bearing, each is a real-world failure mode we find in audits:
- Reciprocity is mandatory. Every URL in the cluster must list every other URL and itself. If the German page doesn't annotate back to the English page, Google ignores the pair entirely.
- Use valid codes. Language is ISO 639-1, country is ISO 3166-1 Alpha-2, in that order.
en-ukis invalid (it'sen-gb);de-eudoesn't exist, there are no regional codes. - Annotate canonical, indexable URLs only. hreflang pointing at redirected, noindexed, or canonicalized-away URLs is discarded. hreflang and canonical tags must agree.
- Always include x-default, the version for users matching no annotation, usually your global English page or a language selector.
- Absolute URLs, always. Relative hrefs are a silent failure.
hreflang errors are one of the most common findings in our technical SEO checklist for a reason: implementations decay every time a URL changes, a market launches, or a CMS migration drops a template. Re-validate quarterly.
Translation vs localization
Translation converts your words into another language. Localization converts your search strategy into another market. The difference decides whether your international pages get impressions at all, because query demand doesn't translate literally: the head term in one market is a minor synonym in another, and whole query categories exist in some markets that don't exist in yours.
- Redo keyword research natively per market. Volumes, phrasing, and intent all shift. This is the same discipline as our semantic keyword research process, run per market, ideally by a native speaker.
- Re-check search intent per market. The same query can surface category pages in one country and editorial comparisons in another. Read each market's SERP before assigning page types, exactly as our search intent guide prescribes.
- Localize the commercial layer: currency, units, payment methods, shipping, legal terms, phone formats, and social proof from that market. These drive conversion and are relevance signals in their own right.
- Adapt examples and references. Case studies, statistics, and cultural references from your home market read as foreign content, because they are.
“If your international pages are word-for-word translations, you haven't entered a new market. You've published your old market in a new alphabet.”
Machine translation plus native-speaker editing is a workable pipeline for scaling, pure machine translation at scale is thin-content risk and, more practically, produces pages that target no real queries and convert nobody.
Topical authority is earned per market
Here's the uncomfortable truth of international expansion: your dominance in one market doesn't transfer. With a subfolder structure your German section inherits the domain's authority, but relevance for German queries has to be built with German coverage, Google evaluates whether you're a comprehensive source for those queries in that language. A ten-page German section attached to a thousand-page English site is still a ten-page competitor in Germany.
- Build a topical map per market. Start from your home-market topical map, but re-derive it from native keyword research, clusters gain, lose, and reshape across markets.
- Launch a full core cluster, not a sampler. Enter each market with its money pages plus the complete supporting cluster around your primary topic, following the same compounding logic as the topical authority playbook.
- Interlink within the market first. German pages should primarily link to German pages, forming a self-sufficient cluster. Cross-language links belong in the language switcher and hreflang, not scattered through body copy.
- Earn in-market links. Links from German-language sites and .de domains validate you as a participant in that market's web, home-market links don't carry the same local weight.
- Sequence markets. Fully build market one, measure, systematize, then replicate. Five markets launched thin all stall together; one market built deep becomes the template that funds the rest.
Measure each market as its own P&L: separate Search Console filters per subfolder, native-market rank tracking, and per-market content velocity. When a market's cluster is complete and it still underperforms, the diagnosis is usually links or localization quality, not more pages. If you want the structure, hreflang, and market playbooks handled end to end, that's our international SEO service.
Key takeaways
- Subfolders (example.com/de/) are the right structure for most businesses, they consolidate authority into one domain while still allowing per-market targeting.
- hreflang is an annotation, not a ranking boost: it tells Google which version to show which users, and it only works when every version links back reciprocally, including to itself.
- Translation ports your words; localization ports your search demand. Keyword research must be redone natively per market, literal translations routinely target queries nobody types.
- Topical authority is earned per market. A dominant English cluster gives your German subfolder a head start in authority, but not in relevance, each market needs its own coverage.
- Launch markets sequentially, not simultaneously: one fully-built market outperforms five thin ones and teaches you the playbook cheaply.
Frequently asked questions
Should I use a ccTLD, subfolder, or subdomain for international SEO?
Subfolders win for most businesses because all markets share one domain's authority. Choose ccTLDs only when local-domain trust is commercially decisive in a target market or legal separation demands it, and accept that each ccTLD builds authority from zero.
Does hreflang improve rankings?
No, it's a swap signal, not a ranking signal. hreflang decides which of your equivalent pages Google shows to which users, preventing the wrong-country version from appearing. The pages still have to earn their rankings through content, relevance, and links.
Do I need hreflang between en-US and en-GB pages?
Yes, same-language, different-country pages are the canonical hreflang use case. Without annotations, Google often picks one version for both markets, showing US pricing to UK users or letting the two pages compete. hreflang plus consistent canonicals resolves it cleanly.
Can I just machine-translate my site for new markets?
As a raw pipeline, no. Unedited machine translation produces pages that target literal translations of your keywords rather than what natives actually search, and at scale it reads as low-quality content. Machine translation with native-speaker editing and market-specific keyword research is the workable middle ground.
How many pages do I need to launch a new market?
Enough to cover one complete core cluster: your money pages plus the full set of supporting content around your primary topic, typically 20–50 pages depending on the niche, not five translated landing pages. Depth in one cluster beats breadth across many.
Why is my correct hreflang being ignored?
The usual culprits: missing return links (every page must annotate every other page and itself), hreflang pointing at non-canonical or noindexed URLs, invalid codes like en-uk, or canonical tags that contradict the annotations. Audit the full cluster with a crawler rather than checking pages individually.
Founder & Semantic SEO Lead · Permanent SEO
Writes about entity SEO, topical authority, and how modern and AI-powered search actually rank content.
View full profile