: Recommended approach for slug generation with multiple languages I am building a website that will be available in multiple countries. Each country's content will be unique to that country, but

@Heady270

You'll have better user metrics, if you create slugs in language according to the language version:


users will easier remind about page addresses to visit them twice,
users will faster understand the page's topics reading them in their mother tongue,
in general, you get all benefits of using mother tongue instead of foreign language.


But note!


such setup is very error-prone / fragile,
it is not a kind of trivial task, to get Google correctly index and rank all of your content in all of countries you target.
beside of this, it is a Heidenarbeit, die sich kaum lohnt german description for plenty of work not worth to do.


For the sake of clarity and best possible indexing and ranking i would always prefer an approach:


one ccTLD → one site → one language.


I recommend this from the personal point of view and experience - i've seen sites, i.e. with content for Germany, Austria and Swiss, whose setup was theoretically correct, but Google wasn't able to rank them correctly. German pages was ranking for Austria, austrian pages was ranking for Swiss and so on.

In your case the content on such pages will be the same:

English


mydomain.com/gb-en
mydomain.com/de-en


German


mydomain.com/gb-de
mydomain.com/de-de


And the only reliable method to route users to correct version is based on their Geo-IP-ing and recognizing of their browser language settings. You will be forced to recognize Geo-IP and browser language by first user's visit, let him correct your recognition and save the country and language selection in a cookie. By next visit you check the cookie and are able to redirect the visitor to the site's version saved in a cookie.

Google recommends this method too, but by itself doesn't read cookies and very seldom uses IP another than american one. Google means the only way to crawl multilanguage sites is correct hreflang implementation. In my experience it is never the case where all language versions of a multilanguage site were ranking equally good. But the management affort for such sites is way higher as if you would run a separate site for each country.

Vote Up Vote Down