Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
What language to use for URL's for Russian language?
-
Hi,
Our site is in English, Spanish, Danish and Russian - the URL's are individual to the language they are in, but of course, Russian contains some strange characters so I decided not to use them in the URL's
Any advice on how to create the URL's for russian language pages?
thanks
-
Hi,
Technically if your cms and server can handle incoming urls with utf8 characters in them then you should be ok. I have seen some instances where the setup does not like them and produces 404 errors when you try to include these characters in the url, but most times it is fine. Google will display utf8 urls in the search results without problem (check out the wikipedia result here)
There is a further consideration though which is one I face a lot with Greek (similar to russian in some ways) which is how these urls are shared in mails, social media etc. A lot of the times these urls end up getting automatically url encoded and the url shown in the mail or facebook etc is a long, long string of url encoded characters which is impossible to read, gives no indication of what the page is about and generally looks bad (try putting that link above into facebook....nasty). For this reason I usually choose to do 'greeklish' urls which is a latin character representation of the greek characters. There are usually some common practices in regards how the local language is 'recreated' in latin characters, there are for Greek, I would assume there are for Russian also. So with that in mind, if you have a russian speaker who is familiar with that kind of thing I would be inclined to make the urls themselves 'russianlish'.
My two cents!
-
Listen to Matt Cutts awesome answer here LOL!!!: http://www.youtube.com/watch?v=suTDT6-Q8NE
I think your special characters may depend on the search engine. Go to Russia's search engine and find out if your URLs display better there: http://www.yandex.com/
I believe Yandex is more popular there than Google is.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Schema for languages Subfolders
I'm using static Schema for each language subfolder in my website, Should i use the same "URL, description" for every language? or i have to use the URL and description according to the language? I'm using that schema for english should i change URL and description in the other languages? for example
International SEO | | MTBE0 -
Redirect to 'default' or English (/en) version of site?
Hi Moz Community! I'm trying to work through a thorny internationalization issue with the 'default' and English versions of our site. We have an international set-up of: www.domain.com (in english) www.domain.com/en www.domain.com/en-gb www.domain.com/fr-fr www.domain.com/de-de and so on... All the canonicals and HREFLANGs are set up, except the English language version is giving me pause. If you visit www.domain.com, all of the internal links on that page (due to the current way our cms works) point to www.domain.com/en/ versions of the pages. Content is identical between the two versions. The canonical on, say, www.domain.com/en/products points to www.domain.com/products. Feels like we're pulling in two different directions with our internationalization signals. Links go one way, canonical goes another. Three options I can see: Remove the /en/ version of the site. 301 all the /en versions of pages to /. Update the hreflangs to point the EN language users to the / version. **Redirect the / version of the site to /en. **The reverse of the above. **Keep both the /en and the / versions, update the links on / version. **Make it so that visitors to the / version of the site follow links that don't take them to the /en site. It feels like the /en version of the site is redundant and potentially sending confusing signals to search engines (it's currently a bit of a toss-up as to which version of a page ranks). I'm leaning toward removing the /en version and redirecting to the / version. It would be a big step as currently - due to the internal linking - about 40% of our traffic goes through the /en path. Anything to be aware of? Any recommendations or advice would be much appreciated.
International SEO | | MaxSydenham0 -
Has any one seen negative SEO effects from using Google Translate API
We have a site currently in development that is using the Google Translate API and I am having a massive issue getting screaming frog to crawl and all of our non-native English speaking employees have read through the translated copy in their native language and the general consensus is it reads at a 5th grade level at best. My questions to the community is, has anyone implemented this API on a site and has it a) helped with gaining traffic from other languages/countires and b) has it hurt there site from an SEO standpoint.
International SEO | | VERBInteractive0 -
Using a top level domain name and directing it to a subfolder
Hi, we have a large international network. Our main website sits on .com domain and is used by the UK market. We have an international site in a subdirectory .com/dk/ for Denmark for example. We have also purchased the domain name www.ourcompany.dk/. Should we be forwarding the domain name (www.ourcompany.dk/) to point to the subdirectory www.ourcomany.com.dk/ so in the browser it shows up as www.ourcompany.dk or should we be displaying it as www.ourcompany.com/dk/? Are there any pros and cons to this method? Which one is best and are there any benefits in SEO. Ideally we want the .com domain name to have the best domain authority so would this impact it in any way? Any tips would be great.
International SEO | | Easigrass0 -
How to interlink 16 different language versions of site?
I remember that Matt Cutts recommended against interlinking many language versions of a site.
International SEO | | lcourse
Considering that google now also crawls javascript links, what is best way to implement interlinking? I still see otherwhise extremely well optimized large sites interlinking to more than 10 different language versions e.g. zalando.de, but also booking.com (even though here on same domain). Currently we have an expandable css dropdown in the footer interlinking 16 different language versions with different TLD. Would you be concerned? What would you suggest how to interlink domains (for user link would be useful)?0 -
Two versions of a website with different languages - Best way to do it?
I'm working on a website for a Swedish artist and her page is in Swedish, everything is in Swedish on the site, even though it's not a lot of text on the site. We would like to have the site in English too, or another version of the site in English on a separate domain, what's the best way to proceed from here? The domain name is a .se (swedish domain), would it be better to create a another domain and host the english version of the site on a .com domain? Or will we bump into problems with duplicate content if we create a replica of the swedish site in english. We're using wordpress and I know that there's translation plugins out there, is that a good option? I'm a bit clueless on how to proceed and would love some help or guidance here.
International SEO | | Fisken0 -
Best URL structure for Multinational/Multilingual websites
Hi I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.) As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product? To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format: hotelsite.com/en/hotel-name (for english) and hotelsite.com/se/hotel-name (for swedish content of that same product) and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc. Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name? Any thoughts on best practice would be greatly appreciated.
International SEO | | pikka0 -
Should product-pages with different currencies have different URLs?
Here is a question that should be of interest for small online merchants selling internationally in multiple currencies. When, based on geolocation, a product-page is served with different currencies, should a product-page have a different URL for each currency? Thanks.
International SEO | | AdrienOLeary0