International websites
How should a multilingual website support search?
Search engines and people need consistent signals about which language a page serves, how versions relate, and whether the visible content truly answers the same intent.
Published · Updated
URLs
Give every language a stable address
Use separate crawlable URLs for each language and keep navigation links available without requiring scripts or a browser-language redirect.
- ExampleUse one consistent pattern such as /fr/service/ and /de/service/.
Signals
Connect versions with reciprocal hreflang
Every equivalent page should reference all language variants, including itself, and the referenced pages should return the same complete set.
- CanonicalEach translated page normally points its canonical to itself when it is a real localized version.
Content
Translate what visitors can see
Localize titles, descriptions, headings, navigation, body content, calls to action, and structured data. Avoid pages that only translate hidden metadata.
- ReviewHave customer-facing final copy supplied or approved by a fluent reviewer.
Measurement
Observe each market separately
Track indexing, queries, landing pages, conversions, and content quality by country and language, then improve pages based on evidence.
- No guaranteeCorrect setup improves clarity for crawlers but does not guarantee a ranking.
FAQ
Questions
Can all languages use one URL?
Separate URLs give visitors and search engines a stable version to discover, share, and index.
Does hreflang replace translation?
No. Hreflang connects genuine language versions; the visible content still needs localization.
Should translated pages canonicalize to English?
Usually no when each localized page is intended to be indexed. Each genuine version normally uses a self-referencing canonical.
Related guides
Related service
Put the decision into practice
Explore a focused service or ask SmrtAnt to review your current website and priorities.