Is it advisable to show additionally also English ciity names of American cities in website versions of non-western languages such as Chinese, Japanese etc?
-
To my understanding in many Asian languages city names are transcribed as they sound and this can cause confusion especially in the case of lesser known American city names.
So I was planning to put in our international website versions (Chinese, Japanese, Korean etc. ) the English name in brackets after the translated city name in meta title and H1.
However when I checked Tripadvisor and Booking.com I noticed that they do not show the English city name anywhere on their Asian language versions.Any thoughts?
Would you recommend to put the English city name in brackets after the translated city name or may it rather hurt our ranking and traffic? -
It would be useful to see an example of what you mean, but the answer is probably not. What to do first is:
- Ensure you set up hreflang correctly, so that Google understands your Chinese-language page on New York and your English-language page on New York are functionally equivalent.
- Use a good rank tracker, and configure it to check your keywords on each of the country-level Google sites you're interested in (Google.co.kr for Korea, and so on). See whether the correct page is showing up when you track ranks for the foreign-language name, and for the phonetically-translated name.
- Check Search Console for the appropriate pages, using the country filter to look only at the kinds of queries and clicks you're getting from each of the countries you're interested in. See whether people are actually searching with the Asian-language name for the city, or with a phonetic translation. See whether people are searching for the English name (they might be).
- If, after looking at your rank tracking and search console results, you think there are many people in Asia putting English-language city names into their queries, at that point you could consider going ahead with this idea. Even then, try it on just a few of your city pages at first—not all of them—and continue to refer back to your rank tracker. What you don't want to see is any direct competition between different language versions of the same page, in the same SERP.
-
Hey there,
I wouldn't put the English versions in the brackets.
It'd make the H1 much longer and there'd be many titles with the same KW's in them.
I don't think it'd hurt SEO as much but it'd be quite confusing regarding UX.
Hope it helps. Cheers, Martin
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
-
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 -
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 -
Can a Global Website Rely on Browser Settings for Translation?
Our website serves a global market and over a year ago, we launched 8 language variations of the site and implemented hreflang tags. These language variation pages are proving difficult to maintain, and in Search Console they're triggering thousands of errors. I have double checked our implementation and it's not perfect, so I understand the errors. Here's the question though... the 8 language variations of the site are receiving less than 1% of our web traffic despite 40% of our web traffic coming from countries outside of North America every month. I want to know if we can eliminate the headache of these 8 language variations altogether, remove our attempt at hreflang, and simply rely on the browser settings of the user to dictate what language the website appears in for them? If not, is there a simpler solution than hreflang and attempting to maintain a very large website in 8 languages? Thank for your input! Niki
International SEO | | NikelleClark0 -
Is it OK to change language by user IP?
Hello, I just read https://support.google.com/webmasters/answer/182192?hl=en#1 about multilingual website. Google says "Avoid automatic redirection based on the user’s perceived language". so Is it ok to redirect url by user IP instead of user language?
International SEO | | visaasancard0 -
Website Migration
Are there any SEO issues with fdmgroup.com that I should address? We recently migrated to a new website redesign. Thanks.
International SEO | | fdmgroup0 -
Geotarget subfolders with the same language or get rid of duplicates but lose option to geotarget?
Hi, we have a domain that is aimed to cover LatAm region. Currently, the homepage contains country selector for ~20 countries. 95% of them hold content in Spanish. We have only homepages for each regions as separate subfolders, i.e.
International SEO | | eset
www.maindomain.com/co
www.maindomain.com/cl
www.maindomain.com/br
etc. but once the user clicks on menu item he is taken back to main domain subpages, i.e. www.maindomain.com/comprar My struggle is to decide whether it is better to: A) copy all content for each subfolder, which will create huge amount of duplicates (there are no resources to create unique content and it is even impossible taking into account nature of the product - mostly tech.specs, etc.) and implement hreflang sitemaps and configure GWT to target each country with its own Spanish content (the same for each country) OR B) remove all local subfolders and keep only main domain in Spanish that will serve all countries within the region. With this option, we will get rid of duplicates but also lose option to geotarget. So, my questions is which option will do less harm, or if there is any other approach that comes to your minds. I consulted with two agencies but still haven't got clear answer. Thanks a lot for your help!0 -
SEO for Subdomains for different languages .com/fr, .com/es
Hi All, I was wondering how best to to approach optimisation of a site that exists on a single .com domain, but has different subfolders for different languages. The site is a .com and it has subfolders for French, Spanish, Russian and English. The business is situated in France and the vast majority of clients are French and English speakers. I've read that it's possible to geo target these subfolders using webmaster tools however I believe this is an inferior method of optimisation than having tld's. Just wondered if anyone had experience of htis and could provide any advice ? As they won't be rebuilding the site for another year or so I wondered if there were any quick wins? My second question is to do with how best to set these campaigns up within SEO Moz. would it be better to track at a subdomain or subfolder leverl (for different languages)? If someone could advise I would greatly appreciate it! Thanks, vantresca
International SEO | | vanvallejo0 -
Website Translation
Hi All, I know its not an SEO question, but....................... Can anyone suggest a few good website translation "widgets" I would like to give those who are not fluent in English and option to choose another language in which to view the page text. Thank You!!!
International SEO | | APICDA0