大网数据广告活动
网站运营与故障问答

Locale code in route versus in query string for i18n

· 52CE 我爱测

So I came across a library that helps with adding locale code to the route of your website. eg website.com/en-US/about/ The library claims that one should do it this way because "Google needs different URLs to crawl and render yo…

问题原文

原帖链接 · Fernando Tiberti · CC BY-SA 4.0

So I came across a library that helps with adding locale code to the route of your website. eg website.com/en-US/about/

The library claims that one should do it this way because "Google needs different URLs to crawl and render your pages for each language.". Is this correct?

Also, would simply putting the locale code in the query string accomplish the same thing? eg website.com/about/?locale=en-US

More generally: what are the advantages and disadvantages of route-based vs query-based?

已采纳解答

原帖链接 · phyrfox · CC BY-SA 4.0

From an SEO perspective, it doesn't matter. However, in the general case, using query-based language configuration complicates server code all over the place. It makes handling forms slightly more complicated, can complicate template processing, removes the possibility of static language-based files (e.g. imagine a banner image in each language, you can't just dump them to the file system, you need a image handler to determine which file to serve...).

Overall, unless you have some sort of platform that specifically takes advantage of a query-based i18n setup, you should avoid doing so, simply because it will complicate the server code in a myriad of not-so-fun ways. It's also incredibly non-standard, as almost all major packages (e.g. WordPress) does use route-based language configuration. It's simply easier to use.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2018-10-19)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。