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.
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. 
- 
					
					
					
					
 All my sites are in multiple languages - including french - and I have seen much better results when I translated the file names into French instead of leaving them in English. So for example I have found that: www.mywebsite.com/bonjour.html performed better for relevant French language searches than www.mywebsite.com/goodmorning.html This has held true for me in all the languages. Even in Chinese and Russian, I write them out with latin characters and it seems to make a difference. I hope this helps. 
- 
					
					
					
					
 hi if you want your site indexed on google.fr then leave it with french, but if you want both, so with englisch translation and on google.com, then I'd suggest the following structure: www.site.fr/nourriture & www.site.fr/en/food it's up to you in which language you create your site... Google does not care, they can translate  cheers 
Browse Questions
Explore more categories
- 
		
		Moz ToolsChat with the community about the Moz tools. 
- 
		
		SEO TacticsDiscuss the SEO process with fellow marketers 
- 
		
		CommunityDiscuss industry events, jobs, and news! 
- 
		
		Digital MarketingChat about tactics outside of SEO 
- 
		
		Research & TrendsDive into research and trends in the search industry. 
- 
		
		SupportConnect on product support and feature requests. 
Related Questions
- 
		
		
		
		
		
		Why Doesn't Google Use My Title Tag and Meta Description?
 Hi fellow Moz SEOs, Need your URGENT help! We set an optimised title & meta description for our client websites. These titles are approved by our clients. Before somedays, they checked on Google, noticed the title & meta description were not the same. Next moment, they notified me about this issue. The title & meta description looks fine when I checked the source code. So, why Google use title & meta description differently? For example: Title approved by client: Top Specialist Divorce & Family Lawyer - Yeo & Associates LLC International SEO | | Verz
 Google set our title: Yeo & Associates LLC: Top Specialist Divorce & Family Lawyer Title approved by client: Filing For Divorce Online in Singapore | DivorceBureau®
 Google set our title: DivorceBureau®: Filing For Divorce Online in Singapore Title approved by client: Halal Buffet & Bento/Packet Meals Event Caterer Singapore | Foodtalks
 Google set our title: Foodtalks - Halal Buffet & Bento/Packet Meals Event Caterer Singapore Title approved by client: Child Care Centre in Singapore| Top Preschool | Carpe Diem
 Google set our title: Carpe Diem: Child care Centre in Singapore| Top Preschool Every day, they are requesting me to update Google's title with their approved title. Also, asking me these questions.
 Why did this happen?
 Why didn't set their recommended title? Is there any way to set our approved titles? Please, help me to find the solution. ASAP Thanks in advance!0
- 
		
		
		
		
		
		International SEO
 Okay, so I have read through the following link in respect to International SEO (https://a-moz.groupbuyseo.org/learn/seo/international-seo), and I believe that the way forward it a ccTLD. My thought was to have .com, .co.uk and .eu. Currently my site is .com, but receives most of its traffic from UK sources. I'm concerned that when I switch over to ccTLDs, the .co.uk in particular, that my UK traffic could dry up. Switching from .com to .co.uk and then using the .com to target the US market makes sense, but I would like to know others opinions on the potential dangers of doing this. Also, are ccTLDs kept on the same hosting or would they require individual hosting? The link doesn't cover this question. International SEO | | moon-boots1
- 
		
		
		
		
		
		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
- 
		
		
		
		
		
		In the U.S., how can I stop the European version of my site from outranking the U.S. version?
 I've got a site with two versions – a U.S. version and a European version. Users are directed to the appropriate version through a landing page that asks where they're located; both sites are on the same domain, except one is .com/us and the other is .com/eu. My issue is that for some keywords, the European version is outranking the U.S. version in Google's U.S. SERPs. Not only that, but when Google displays sitelinks in the U.S. SERPs, it's a combination of pages on the European site and the U.S. site. Does anyone know how I can stop the European site from outranking the U.S. site in the U.S.? Or how I can get Google to only display sitelinks for pages on the U.S. site in the U.S. SERPs? Thanks in advance for any light you can shed on this topic! International SEO | | matt-145670
- 
		
		
		
		
		
		If I redirect based on IP will Google still crawl my international sites if I implement Hreflang
 We are setting up several international sites. Ideally, we wouldn't set up any redirects, but if we have to (for merchandising reasons etc) I'd like to assess what the next best option would be. A secondary option could be that we implement the redirects based on IP. However, Google then wouldn't be able to access the content for all the international sites (we're setting up 6 in total) and would only index the .com site. I'm wondering whether the Hreflang annotations would still allow Google to find the International sites? If not, that's a lot of content we are not fully benefiting from. Another option could be that we treat the Googlebot user agent differently, but this would probably be considered as cloaking by the G-Man. If there are any other options, please let me know. International SEO | | Ben.JD0
- 
		
		
		
		
		
		URL Structure - Homepage, Country and State Pages
 Hello, I am creating a website (or websites if best format) that will have state-specific boating license courses for every state in the US, Canada and Australia. I would like the content to be available on the website in English, French and Spanish. I want to be the global leader in providing boat test courses. For the (1) homepage, (2) country pages, and (3) state pages, what is best SEO format I should use for: International SEO | | Monologix
 (a) URL structure
 (b) "href lang" code
 (c) rel canonical code
 (d) will meta content with non-English pages need to also be in the non-English language of that page? Also, what server company do you recommend I host my website with? I am a non-programmer and learning SEO, so any and all help will be greatly appreciated! Thank you very much in advance!!!0
- 
		
		
		
		
		
		International hreflang - will this handle duplicate content?
 The title says it all - if i have duplicate content on my US and UK website, will adding the hreflang tag help google figure out that they are duplicate for a reason and avoid any penalties? International SEO | | ALLee1
- 
		
		
		
		
		
		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! International SEO | | Logi0
 
			
		 
			
		 
			
		 
					
				 
					
				 
					
				 
					
				 
					
				 
					
				 
					
				