2

So I have let's say 20 languages the marketing pages of the website are localized into. I am thinking of doing this...

mywebsite.com/en/page-1
mywebsite.com/en/page-2
mywebsite.com/zh/page-1
mywebsite.com/zh/page-2
...

Actually, instead of putting the latin script in there, I would really do this:

mywebsite.com/english/page-1
mywebsite.com/english/page-2
mywebsite.com/中文/页一
mywebsite.com/中文/...

The reason for that is it gives an SEO benefit I would think, for the native language pages.

But now we move onto the admin panel. The admin panel might also have these 20 languages, but should it be structured the same way? Or should it instead be like this:

mywebsite.com/admin/users/1/edit?lang=zh
mywebsite.com/admin/users/1/edit?lang=en
....

Or better yet, just store the language in localStorage and clean up the URL completely.

The reason we do it this way is because these pages are all hidden anyways from search engines, so there's no SEO benefit to be had. Is this the correct way to handle both situations? Or what is best?

2

There is no feasible SEO benefit (unless anyone can prove it?)

There is a pain for sharing non Latin links as the link will end up containing %20%32%36 for non valid URL characters and therefore can not be read by human.

https://stackoverflow.com/questions/1547899/which-characters-make-a-url-invalid

My native language is Russian, I study Japanese, my keyboard does not have Japanese characters, how do I alter link to see japan page?

ISO notation is great in every way, everyone use it and there is really no reason for you not to follow it:

I have never ever seen someone to make links localized: https://site.com/русский/latest-article Looks very odd to me

storing locale in localStorage is also not good as you can not send a link to a localized page:

  • I send localized link to my foreign colleague on his language
  • if particular page does not contain say French translation, it is clear how to get alternatives for other languages, and they are linkable. You will have a problem otherwise.

For most of webserves it is no longer a problem to have ../en-us/... instead of ?locale=en-us They can even transform one into another in background, so there is no need to choose less beautiful option to pass locale as query string (?locale=en)

enter image description here

| improve this answer | |
  • 1
    I agree. Our company sells products all across the world and all links are simply held in English. Except for the German page, which has German localized links, as that is the birthplace of the company and users expect it to be German and not international. But that is not an issue as nearly all German characters are present in English as well. OP's case would include a lot more invalid characters, which I think would only lead to confusion across different users as well. – Big_Chair Jan 22 at 14:53
  • I don't understand this argument about "invalid" URL characters. Wikipedia uses the native scripts EVERYWHERE, and it looks nice to me. IE th.wikipedia.org/wiki/… – Lance Pollard Jan 22 at 16:21
  • Looks like a top Chinese website doesn't use localized URLs... – Lance Pollard Jan 22 at 16:22
  • Baidu puts them in the URL: http://www.baidu.com/s?rsv_idx=1&wd=%E9%98%BF%E5%9D%9D%E5%B7%9E4.5%E7%BA%A7%E5%9C%B0%E9%9C%87&usm=1&ie=utf-8&rsv_cq=food%E6%98%AF%E4%BB%80%E4%B9%88%E6%84%8F%E6%80%9D%E4%B8%AD%E6%96%87&rsv_dl=0_right_fyb_pchot_20811_01&rsf=390f0462fd5ad42382be9e734b8d6541_1_15_1&rqid=b86dc60d000ce7bc baidu.com/… – Lance Pollard Jan 22 at 16:23
  • 1
    Got it, well my Google Chrome on mac shows the nice native script, are you on windows? Here is a korean site namu.wiki/w/… and m.sleepmania.net/product/… – Lance Pollard Jan 22 at 16:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.