A
A
algorama2012-01-28 23:27:01
Domain name market
algorama, 2012-01-28 23:27:01

Domain localization

What is the best way to implement many localizations in a domain name? I choose between two options:

  • en.domainname.com
  • domainname.com/en/
The second one is intuitively closer (if only because when typing in the address bar it makes me want to immediately write the domain name, and not some localization letters, Wikipedia constantly puts me in a stupor), but I still doubt it. Are there any implementation quirks or issues associated with each option? Are there any other good localization options?

Answer the question

In order to leave comments, you need to log in

5 answer(s)
E
Evengard, 2012-01-29
@algorama

I would choose the first one. Why? Because often (albeit not always) the language of the site is clear precisely from the domain name (by tld). And if you need to show that there is a different language here than the one in tld, then you need to show it again in the domain name.

D
Dmitry, 2012-01-29
@EvilsInterrupt

I would choose the second. It is often used, which will not cause a lot of questions “Why is that?”. Examples:
www.freebsd.org/ru/
www.lenovo.com/ru/ru/index.html
www.ibm.com/ru/ru/

V
Vladislav, 2012-01-29
@click0

If the content is drastically different, then different domains are better, not even subdomains.
If the usual localization, then I agree with the previous speaker.

A
Alexey Sundukov, 2012-01-29
@alekciy

If the sites are on different servers, then the first. Otherwise, the second.

G
gorets, 2012-01-30
@gorets

And automatically select the language depending on where they come from with further confirmation of the region?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question