Choose a predictable URL structure
A main language at / and English under /en/ is a clear starting point. A language switch should lead to the corresponding translation when available. Avoid forcing location-based redirects; a visitor in the Netherlands may still prefer English.
Translate meaning and actions
Translate prices, form fields, errors and renewal terms too. Keep canonical and language references consistent with actual pages. A translated page normally needs its own appropriate canonical. Test search, cart and payment stages, not only the homepage.
Your practical checklist
- Choose stable language URLs.
- Link corresponding translations.
- Translate form and price information.
- Test the complete route in each language.
A useful question
Do I need .com for English?
Not necessarily. One domain can serve multiple languages with a clear structure.
Ready to check your name? Start with the exact domain, then compare alternatives. Find a domain →
Sources & further reading
Original guide by chname.ch editorial. Archive dates organise this library; this guide was created and reviewed on . Provider and registry instructions take precedence when requirements change.