多语言网站的URL结构 [英] URL structure for multi-language site

查看:150
本文介绍了多语言网站的URL结构的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想制作一个多语言站点,但是我不确定从SEO角度来看处理URL结构的最佳方法是什么.一些例子:

I want to make a multi-language site, but I'm not sure what the best way is to deal with the URL structure from a SEO point of view. Some examples:

产品

example.com/product/123/en/product-name

example.com/product/123/product-name/en

还是其他?

类别

example.com/Category/en/furniture/chair/

example.com/Category/en/120/chair/

example.com/Category/en/chair/

还是其他?

推荐答案

(忽略SEO方面,因为它在Stack Overflow上是不合主题的.)

(Ignoring the SEO aspect, as it’s off-topic on Stack Overflow.)

将语言标签作为 first 路径段是最常见的约定.而且这很有意义,尤其是如果您转换路径(您应该这样做),因为该路径表示层次结构:

Having the language tag as the first path segment is the most common convention. And it makes sense, especially if you translate the path (which you should!), because the path represents a hierarchy:

首页是首页:

  • example.org/en
  • example.org/de
  • example.org/en
  • example.org/de

从那里选择一个产品:

  • example.org/en/product/123/chair
  • example.org/de/produkt/123/stuhl
  • example.org/en/product/123/chair
  • example.org/de/produkt/123/stuhl

或类别:

  • example.org/en/category/furniture
  • example.org/de/kategorie/möbel
  • example.org/en/category/furniture
  • example.org/de/kategorie/möbel

如果语言标记位于路径的中间或结尾,则不允许使用可浏览的URL (至少不是明智的方式,带有已翻译的路径).

If having the language tag somewhere in the middle or at the end of the path, it wouldn’t allow for browsable URLs (at least not in a sensible way, with translated paths).

这篇关于多语言网站的URL结构的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆