Multilingual SEO: hreflang, Structure and the Mistakes That Cost Rankings
Multilingual sites usually fail for structural reasons, not translation quality. Here is the setup that works.
Adding a second language looks like a content project and behaves like an architecture project. Get the structure wrong and you produce two versions competing with each other, neither ranking properly, with search engines unsure which to show to whom.
Pick a URL structure and commit
- Subdirectories (site.com/fr/) — the default recommendation. Authority accrues to one domain, and setup is simple.
- Subdomains (fr.site.com) — acceptable, but authority is more separated and it is more infrastructure for little gain.
- Country domains (site.fr) — strongest local signal, highest cost, and each domain builds authority from zero.
- Parameters (?lang=fr) — avoid. Weak signals, caching problems and a structure search engines handle badly.
hreflang, done correctly
Every language version must reference every other version, including itself, and the references must be reciprocal — if the English page points to French, the French page must point back. One-directional hreflang is ignored entirely, which is why so many implementations produce no effect at all.
- Use language codes alone (en, fr) unless you genuinely serve different content per country (en-US vs en-GB).
- Always include an x-default for visitors whose language you do not serve.
- Point to the canonical URL of each version, not a redirect chain.
Translation is not localisation
People search differently in different markets, not merely in different words. The direct translation of your best keyword is frequently not what the target market types. Research keywords natively per language, and expect page structures to differ — a market with different objections needs different sections, not the same page rendered in another language. It is the kind of work our technical SEO service does, in that order, with the indexing checked before anything is tuned.
- 1 URL structure, chosen once
- reciprocal hreflang or no effect at all
- 0 automatic language redirects
Frequently asked questions
Is translated content duplicate content?
No. Genuine translation into another language is not duplication. The real risk is near-identical pages within the same language — for example separate US and UK pages with barely any difference — where a canonical or consolidation is the answer.
Should we use machine translation?
As a first draft reviewed by a native speaker, yes — it is now good enough that the review is editing rather than retranslation. Published unreviewed, it produces content that reads slightly wrong to every native visitor, which costs trust more quietly than it costs rankings.
More on this topic: SEO & Visibility.
Keep reading
Want this built for your business? See what we do.