Translating URLs worth it?
-
My company has content in 23 different languages in 30+ countries. We translate page content but we don't translate URLs. I am trying to figure out whether it would be worth the considerable extra overhead to translate the URLs as well. I'd really appreciate hearing the thoughts of the Moz community. Thanks in advance!
-
Thanks to all for your input! I am thinking we will try translating URLs in one language to test the impact. Thanks again
-
Definitely agree translating the URLs is a must. Having keywords in your URL can aid your SEO efforts so it makes sense for the keywords to be in the language of the country you are targeting with the translated content.Certainly if I looked at SERPs for an English language search but found the URLs written in a foreign lanaguage I would not click on that search result as it instantly looks rather strange or even spammy.
-
I agree with Toshi one hundred percent. It's strongly recommended to change it. I'd say it's crucial you do it. There's absolutely no reason to not do it.
-
If you're already translating the content, it makes sense to translate the URLs as well as part of the process. Think about it, for a non-English speaker the English URLs are effectively gibberish. It would be like if you were given a URL that was in Chinese or Korean. Aside from being a poor user experience, it's not optimal from an SEO perspective as well, as keywords are going to change from language to language, so keeping the English words doesn't make sense.
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
-
Switch to Separate URL Configurations for International SEO?
We run an ecommerce website and sell to customers in the US and Canada. We recently realized that the way we serve content to our users isn't Google's recommended way. We use locale-adaptive pages in that some content changes slightly depending on where we think the user is located based on their IP address. But the URL doesn't change. Google's stance on locale-adaptive - https://support.google.com/webmasters/answer/6144055?hl=en&ref_topic=2370587 That being said, the changes are quite minor. It is usually only pricing and currency that changes depending on if we determine the user to be based in Canada or the US. However, I understand that there can be problems related to this configuration because of GoogleBot primarily using a US-based IP. We decided that the best course of action for us is to serve US content as our default content on all of our existing URLs. And Canadian content would be served using new url paths such as: example.com**/en-ca/**product1. All of this would also be configured to use hreflang tags. The problem we have run into is that it is a pretty huge development challenge to reconfigure how the site serves content when we have been using locale-adaptive for over a year. So developer resources would be taken away from other tasks and put toward this one for a relatively long time. Based on this information and the fact that we would like to both rank better in Canada and to follow Google's recommendations, how important would you say this change would be? I realize this isn't a black and white question and it depends a lot on business goals and preferences. However, I need to be able to gauge as best as I can how necessary it is to do this in order to make the decision of whether to do it or not. Any input is greatly appreciated!
International SEO | | westcoastcraig1 -
Country and Language Specific URL Paths
Wanted to ask everyone a questions: So our company is going to be doing a website that is going to be full of videos. The url path will be country.domain.com/language/slug/content-id. We redirect the user when they go to the different country. So if you're in spain on a train to france your URL will change from es.domain.com/es/slug/content-id to fr.domain.com/es/slug/content-id. Each country can listen to each video in all languages. My question is with hreflang tags and canonicals. Aside from targeting users in a certain country via Google Search Console, how do I eliminate duplication and tell Google which I'd like to show up via which country. In spain I would like es.domain.com/es/slug/content-id to show in Google and would have hreflang tags on each of the es.domain pages but what about fr.domain.com/es/slug/content-id since it would show the same content? I can't canonical to one of them since I need them to show in their respective country. How do I show the difference in language and country without showing duplication?
International SEO | | mattdinbrooklyn0 -
Human Translation versus Google Translate for Ecommerce Products
Hi all, We want to put our products on our ecommerce site into another language. I have always been under the impression that running text through Google Translate is a no no, not only for the user experience, but also it is a Google tool and I am assuming that Google would notice that it is not translated by a human. I don't know if it would incur a penalty as such but it most likely would not be favoured as a human translation Can anyone confirm their experience or impression on this? Thanks!
International SEO | | bjs20100 -
External URLs in hreflang sitemap questions
I'm currently putting together an international sitemap for a website that has an set up like the following: example.com/us
International SEO | | Guyboz
example.com/au
example.com/ca
example.co.uk
example.se I'm planning on including the hreflang tags within sitemaps for each domain, to make sure google serves up the right version. However, I'm a bit sceptical about including the non .com domains within the .com sitemap - and the other way round for .co.uk and .se sitemaps. The way I've been doing it follows the following example: <url><loc>http://www.example.com/us/</loc></url> Putting in the .co.uk and .se domains within the .com sitemap just doesn't feel right - is this actually the right way to do it? Thanks in advance 🙂0 -
What is the current thinking about translated versions of pages? Is it necessary
My company is about to do a big push in China. We can get our homepage translated in Chinese at a very reasonable price. My questions are: Is it worth it? Do browsers to an adequately job of translating pages? If it is worth it: Can someone suggest a good post explaining what to do with the translation? What are the SEO implications? Thank you
International SEO | | appbackr
Sarah0 -
Homepage URL for multi-language site
Hi, We are setting up a new site, and currently considering the URL and folder structure of the site. We will have 2-3 different language versions, and we have decided to use sub folders for this. My question is regarding the homepage URL. We want the English language site (en) to be the default one, from where you can then change the language. Should I have a folder for each of the language versions (as described below)? www.mydomain.com/en
International SEO | | Awaraman
(this would be the default page where everyone would always come if they type www.mydomain.com to webrowser) www,mydomain.com/ru www.mydomain.com/es Or, would it be better for SEO to have www.mydomain.com as the default URL where we would have the English version of the site, and then have two other folders (as below) where we would have the 2 other language versions: www,mydomain.com/ru www.mydomain.com/es Thank you in advance, BR Sam0 -
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 -
International (foreign language) URL's best practices
I'm curious if there is a benefit or best practice with regards to using the localized language on international sites (with specific ccTLDs). For example, should my french site (site.fr) use the french language as keywords within the URLs or should they be in english? e.g. www.site.fr/nourriture vs. www.site.fr/food Is that considered best practice for SEO (or just for brand perception those markets?). Is there a tangible loss in SEO if we do not use the correct language for those URLs and just stick with English around the world? I recall seeing a Matt Cutts video on the topic and he said that google does support i18n URL's but other SE's might not support them as gracefully but he didn't come down with a hard recommendation to go with i18n URL's or just English. Would love a strong ruling in favor one direction based on best practices.
International SEO | | mongillo0