: When the root URL of a domain doesn't have a specific site, how should visitors be directed to language folders? My question is not technical (how to do it using X technology), it's about

@Shanna517

I think the most SEO friendly way would be to define a default language. This content would be served from /. All other languages homepages would come from /lang/. And the pattern @unor proposes can still be applied: prefix all content with /lang/, for example /lang/about-xy/ - for the default language as well, as it is common best practice.

Why could it be better to serve a real / page? I have had cases where there once was a / page, but then the system changed to 302 redirects for all languages. And then the original / was kept indexed and showed up in search results (with outdated title tag, etc) for ages. So, this is the point: Your most important URL, the /, is redirecting, with a 302! Or it's showing a list of language links (I would definitly not "noindex" the /), useless in terms of SEO, thus wasting your potential. If you use ccTLDs, you can avoid this problem completely. Also, I heard people say it should be better to have the / page serving a 200 response. But cant find this post anymore.

Vote Up Vote Down

@Shanna517

Many multi-lingual sites don’t have the language tag for the default/primary language in the URL¹, but I think it’s better to include it. So yes, in my opinion, it’s not only good design, it’s the best.

Its suggesting itself to use the root page as a site/language chooser. I think there are three ways how this page can work:


Redirect (based on certain conditions²)
Show a list of links
Show a list of links and pre-select/highlight the most likely choice (based on certain conditions²)


This page is likely not relevant for SEO at all, because search engines typically would have no interest to present a language chooser page to their users. Such a page doesn’t (shouldn’t) have any relevant content, and if it’s redirecting, it would be useless to lead users to this redirecting page instead of the redirect target page (search engines know, or assume to know, their user’s language).

The most important thing (and as you mentioned, you already do it) is that it’s not the only way to choose the language. Users (and search engines) should be able to switch to the translations of the current page with a language switcher/alternate+hreflang links.

Apart from that, as far as search engines are concerned:


For Google Search, you could link it with rel="alternate" hreflang="x-default":


[…] the reserved value "x-default" is used for indicating language selectors/redirectors which are not specific to one language or region, e.g. your homepage showing a clickable map of the world


(I don’t understand why this could be useful, and I think it’s bad design (as the selector page is not a translation of a language-specific homepage) but they mention it in their documentation, so I think it’s better to note it here, too.)
If you redirect, don’t use 301. As the redirect is based on changing/user-specific conditions, it’s not permanent. And you probably don’t want it to get cached for a user (who might change e.g. the accepted languages in their browser and come back to the root page).

302 (or maybe 307?) seems to be the right status code.
Maybe: You could consider to noindex this root page, if it’s really just a list of links.




¹ By the way, for sites that use subdomains (en.example.org, da.example.org) instead of path segments for the language tags, the same question comes up: what to do with example.org/www.example.org? I think the solution is the same in this case.

² The conditions could be the Accept-Language header, the IP address, or whatever makes sense in your context.

Vote Up Vote Down