Locale code in route versus in query string for i18n

.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?

asked 2 hours ago

Fernando Tiberti

1111

New contributor

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?

asked 2 hours ago

Fernando Tiberti

1111

New contributor

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?

asked 2 hours ago

Fernando Tiberti

1111

New contributor

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

asked 2 hours ago

Fernando Tiberti

1111

New contributor

asked 2 hours ago

Fernando Tiberti

1111

New contributor

asked 2 hours ago

Fernando Tiberti

1111

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Â |Â

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.

edited 19 mins ago

answered 45 mins ago

Maximillian Laumeister

831318

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "45"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

Fernando Tiberti is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

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

Name

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
2
down vote

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.

edited 19 mins ago

answered 45 mins ago

Maximillian Laumeister

831318

add a commentÂ |Â

up vote
2
down vote

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.

edited 19 mins ago

answered 45 mins ago

Maximillian Laumeister

831318

add a commentÂ |Â

up vote
2
down vote

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.

edited 19 mins ago

answered 45 mins ago

Maximillian Laumeister

831318

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.

edited 19 mins ago

answered 45 mins ago

Maximillian Laumeister

831318

edited 19 mins ago

answered 45 mins ago

Maximillian Laumeister

831318

answered 45 mins ago

Maximillian Laumeister

831318

answered 45 mins ago

Maximillian Laumeister

831318

add a commentÂ |Â

Fernando Tiberti is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Fernando Tiberti is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Post as a guest

Name

Search This Blog

Iyfjky