Locale code in route versus in query string for i18n
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
2
down vote
favorite
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?
seo internationalization
asked 2 hours ago
Fernando Tiberti
1111
New contributor
Fernando Tiberti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
favorite
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?
seo internationalization
asked 2 hours ago
Fernando Tiberti
1111
New contributor
Fernando Tiberti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
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?
seo internationalization
asked 2 hours ago
Fernando Tiberti
1111
New contributor
Fernando Tiberti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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?
seo internationalization
seo internationalization
asked 2 hours ago
Fernando Tiberti
1111
New contributor
Fernando Tiberti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
Fernando Tiberti
1111
New contributor
Fernando Tiberti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
Fernando Tiberti
1111
New contributor
Fernando Tiberti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
Fernando Tiberti
1111
asked 2 hours ago
Fernando Tiberti
1111
1111
New contributor
Fernando Tiberti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Fernando Tiberti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Fernando Tiberti is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
They should be identical as far as SEO is concerned, because Google doesn't look in the URL to determine language - to determine language they actually use machine learning on the text content itself.
The important part for SEO is to just make Google aware of the different language versions of each page by using meta tags like so:
<head>
<title>Your Website</title>
<link rel="alternate" hreflang="en-us"
href="http://website.com/en-US/about/" />
<link rel="alternate" hreflang="de"
href="http://website.com/de/about/" />
</head>
More info at Google's guidelines for specifying web page languages.
answered 46 mins ago
Maximillian Laumeister
831318
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
They should be identical as far as SEO is concerned, because Google doesn't look in the URL to determine language - to determine language they actually use machine learning on the text content itself.
The important part for SEO is to just make Google aware of the different language versions of each page by using meta tags like so:
<head>
<title>Your Website</title>
<link rel="alternate" hreflang="en-us"
href="http://website.com/en-US/about/" />
<link rel="alternate" hreflang="de"
href="http://website.com/de/about/" />
</head>
More info at Google's guidelines for specifying web page languages.
answered 46 mins ago
Maximillian Laumeister
831318
add a comment |Â
up vote
2
down vote
They should be identical as far as SEO is concerned, because Google doesn't look in the URL to determine language - to determine language they actually use machine learning on the text content itself.
The important part for SEO is to just make Google aware of the different language versions of each page by using meta tags like so:
<head>
<title>Your Website</title>
<link rel="alternate" hreflang="en-us"
href="http://website.com/en-US/about/" />
<link rel="alternate" hreflang="de"
href="http://website.com/de/about/" />
</head>
More info at Google's guidelines for specifying web page languages.
answered 46 mins ago
Maximillian Laumeister
831318
add a comment |Â
up vote
2
down vote
up vote
2
down vote
They should be identical as far as SEO is concerned, because Google doesn't look in the URL to determine language - to determine language they actually use machine learning on the text content itself.
The important part for SEO is to just make Google aware of the different language versions of each page by using meta tags like so:
<head>
<title>Your Website</title>
<link rel="alternate" hreflang="en-us"
href="http://website.com/en-US/about/" />
<link rel="alternate" hreflang="de"
href="http://website.com/de/about/" />
</head>
More info at Google's guidelines for specifying web page languages.
answered 46 mins ago
Maximillian Laumeister
831318
They should be identical as far as SEO is concerned, because Google doesn't look in the URL to determine language - to determine language they actually use machine learning on the text content itself.
The important part for SEO is to just make Google aware of the different language versions of each page by using meta tags like so:
<head>
<title>Your Website</title>
<link rel="alternate" hreflang="en-us"
href="http://website.com/en-US/about/" />
<link rel="alternate" hreflang="de"
href="http://website.com/de/about/" />
</head>
More info at Google's guidelines for specifying web page languages.
answered 46 mins ago
Maximillian Laumeister
831318
edited 21 mins ago
answered 46 mins ago
Maximillian Laumeister
831318
answered 46 mins ago
Maximillian Laumeister
831318
answered 46 mins ago
Maximillian Laumeister
831318
831318
add a comment |Â
add a comment |Â
Fernando Tiberti is a new contributor. Be nice, and check out our Code of Conduct.
Fernando Tiberti is a new contributor. Be nice, and check out our Code of Conduct.
Fernando Tiberti is a new contributor. Be nice, and check out our Code of Conduct.
Fernando Tiberti is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f118511%2flocale-code-in-route-versus-in-query-string-for-i18n%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password