Which will rank higher: Non-mobile friendly site in native language vs. mobile friendly global site in English?
-
Hi, we are currently implementing a mobile site, e.g. m.company.com. The global mobile site will only be available in English.
We have local subsites of the desktop site, e.g. company.com/fr. The local subsites are not mobile friendly.
If a user does a search for a brand term in France, **which site will rank higher in SERPs? **If it will be the global site, is there anything we can do (other than making them mobile friendly) to make the local sites rank higher?
Would it be the mobile-friendly site, even though it is only in English, because the local site would be penalized for not being mobile friendly? Or would it be the local site, because Google will give priority to the fact that it's in French, which matches the language of the person searching?
-
No, it doesn't change my answer, but it's a good distinction to make. It sounds like the international expansion is in process. If the client needs geo-targeted content (sounds like they might), the countries need to be treated differently. Each subfolder as it's own site really. But it sounds like the translation is a good place to start for the time being.
For the mobile, my answer remains the same. There isn't anything other than making the translated content mobile or responsive that will help the traffic.
-
Thanks Kate. The content is very similar between countries, to the degree where I thought it was translated verbatim at first. Looking deeper, I see that there is some slight variation between offerings.
The client is only using language codes: en, it, fr - except in China, where they have two versions of the site (zh-hans and zh-en. The second code, zh-en, is incorrect).
All the content is set up under subdirectories, e.g. site.com/en rather than microsites en.site.com.
Does this change your judgment?
-
Lots going on here. First, let me clarify, your client's desktop content is only translated? They don't change the content and the offerings don't change by country? There is a very important distinction here. Language and country are two different things.
Regardless, if the mobile site is only in English, because of mobilegeddon, if they think they are penalized, it's because they lost mobile traffic or are seeing declines. This is only because there is not good mobile content in the users language. Once that is available, I expect the traffic will rise. It's not a penalty like duplicate content isn't a penalty, it is just not optimal.
For anyone doing brand searches, I think the answer is it depends. If Google thinks the user is okay with the English mobile site, they will show that. If the user has only ever searched in their particular language, and that's not available on mobile, they might show the desktop local site (better but not perfect) or they might test showing the English mobile site. I think you'll see both over time until the mobile issue is fixed.
-
In the Abercrombie case, the site that comes up in the search results is the EU mobile site, with German language. When I click on it, it seems that they are automatically redirecting me to abercrombie.com; not the English version of m.eu.abercrombie.com. I find automatic redirects annoying - in this case, I'm intentionally trying to hit the German site and I can't.
We are in development of the new global mobile site. The existing desktop site is being "punished" for not being mobile-friendly. Hence why we are creating a mobile site in the age of responsive design
-
Hi Jennifer,
How can you still be in development and in the same time be "punished" for not having a mobile version?
To answer your question - Abercrombie is doing something similar as your client is doing. On the desktop version they have 5 languages - the mobile version is only English. If you search on Google.de (desktop) - you get the German version. If you search Google.de on mobile - the titles in the search results are German - however the site which is displayed when you click on the links is the one that is optimised for mobile (= English version)
I guess this will be similar in your case - desktop searches will go to the translated version - the mobile searches will go to the mobile version (even if it's not in the language of the searcher).
Dirk
-
According to the client, the site is being penalized for not being mobile friendly; but there could be other reasons. The desktop site has 10-12 versions, set up as subdirectories.
If the native language site will come up first, the client is fine with doing nothing. If not, they want us to redirect the users as you described. But since we're still in development, we're not sure what the answer is.
Do you think it's most likely that the native language site would come up first?
The long-term plan is to create responsive sites, for better SEO and UX, so this is just a temporary interim solution.
-
Your site will in no way become penalized for not being mobile friendly. "mobilgeddon" was an effort to get more people to switch to mobile friendly designs and is still only a factor within Google's algorithm. You should be thinking about switching to mobile (responsive ideally) for a better user experience - not because of Google.
You mentioned that the global mobile version will only be available in English. Does this mean you have other languages on the desktop site? If so I would rely exclusively on the non-mobile pages utilizing the hreflang tag (https://support.google.com/webmasters/answer/189077?hl=en) and then when you eventually make the other language pages mobile friendly switch the hreflang to point to those page.
Pointing your users in a different company expecting their native language to the mobile english only version I suspect would create extremely high bounce rates. You would be best off (IMO) just sending them to the non-mobile but correct language desktop page regardless of search being desktop vs mobile.
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
-
Managing multi-regional and multilingual sites
Hello, It's been a year since we launched our website and at first, we did it with a domain name called misitio.co. We have just bought the domain name mysite.com and my doubts are what should I do with the domains I have in other countries, for example .mx .br, should I redirect them to mysite.com or manage them independently? Thank you very much
International SEO | | Isabelcabreromunoz1 -
Google Search Console "International Targeting" is reporting errors that are not present on my site
We are currently handling search for a global brand www.example.com/ which has presence in many countries worldwide. To help Google understand that there is an alternate version of the website available in another language, we have used hreflang tags. These hreflang tags are implemented only via the XML sitemap across all geo-locations. Under the “Search Analytics -> International Targeting” section, in Google Search Console, for the Malaysian website (www.example.com/my/), there are a number of “no-return tags (sitemaps)” errors arising. For example, for India as a geo-location, there is one ‘en-IN’ – no return tags (sitemaps) errors listed. The error is listed below: Originating URL - www.example.com/my/xyz/ Alternate URL - www.example.com/in/xyz/ When the XML sitemap for the URL – www.example.com/in/ was checked for the hreflang tags, it was noticed that the implementation of hreflang tags for the URL – www.example.com/in/xyz/ was perfectly fine and it was providing a return tag to the URL – www.example.com/my/xyz/. After the code level verification, it was identified that the implementation of hreflang tags was perfectly fine via the XML sitemap. Even though at the code level it was verified that the implementation is fine, the error still persists in Google Search Console. Kindly suggest a solution to this situation, and also advise the effects of these errors on search engine performance
International SEO | | Starcom_Search0 -
.fr Site Not Indexed in Search Console
Hey everyone, I am just now learning international SEO, and so appreciate any and all help! 1. I added supershuttle.fr to Search Console about a week ago and it still has 0 indexed pages. It is showing that pages were indexed in the sitemap, and when I check, there are 75 results in Google. Is this something I should be concerned with? Is there a setting that I'm not aware of in Search Console that I need to change? 2. Also, I read the below regarding the automatically translated pages. Would https://en.supershuttle.fr/ be considered an "automatically translated" page? Use robots.txt to block search engines from crawling automatically translated pages on your site. Automated translations don’t always make sense and could be viewed as spam. More importantly, a poor or artificial-sounding translation can harm your site’s perception
International SEO | | SuperShuttle0 -
What's the best homepage experince for an international site?
Greeting Mozzers. I have a question for the community, which I would appreciate your input on. If you have a single gTLD that services multiple countires, what do you think is the best homepage UX for the root homepage and why? So the example would be you own website www.company.org and target content to Germany, Japan and Australia with content through the folder structure eg. www.company.org/de-de If someone comes to the www.company.org from a region, would you: Redirect them based on location IP – so if from Germany they land on www.company.org/de-de Let them land on the homepage which offers location selection Let them land on a page with content and offer location selection eg. pop-up or obvious selection box Something I’ve not thought of… I'd appreciate your input. Thanks
International SEO | | RobertChapman0 -
SEO When Teaching English To Russians
My girlfriend is from Saint Petersburg, Russia and now lives in Toronto, Canada. She's been teaching English to Russians for 3 years in person and on Skype, and now wants to start a website to get more 1-on-1 clients and sell online courses, which I have a lot of experience in. If you don't feel like reading my notes below, I'll summarize my main questions here: Would you lean to creating the site more in English or Russian language or both equally... with a .com or .ru or both (2 sites)... hosted in the U.S. or Russia? I've been reading a number of excellent threads about strategies and tactics for online marketing in multiple language (including some here on Moz), but am still confused about how best to approach this. Here are some notes: -Some prospects will search for her services in English and some in Russian (probably more in Russian). -If I build her a site primarily in English, she can take advantage of my experience in English keyword research, SEO, competitor research, and so on. If I build her a site primarily in Russian, I can still do those things, but not as efficiently or effectively. -If I were thinking first and foremost of our users, which is obviously a good place to start, the site would be in both English and Russian, but I've read that if a site has both English and Russian text, and is a .com instead of a .ru, that can really hurt its chances of ranking in Russia's Yandex search engine, which is used more in Russia than Google. Along the same lines, although most SEO sites are saying that it doesn't matter where you host a website these days, an exception seems to be that Yandex does reward sites that are hosted locally. Are these assertions true? -At first I assumed that organic search competition is lower in the Russian language, but I don't really know. I've also read that Yandex really rewards older domains and that it can be hard to beat them, which means competition may be quite high. So my questions again are: Would you lean to creating the site more in English or Russian or both... with a .com or .ru or both (2 sites)... hosted in the U.S. or Russia? Thanks in advance!
International SEO | | smilinggardener
Phil1 -
What’s the best way to convert ccTLD to global TLD?
We started out as a Canadian site targeting Canadian users. Now our site http://iCraft.ca has a lot of international buyers and sellers and .ca TLD doesn’t make sense anymore, as we are not performing well on Google.com We are doing a complete site redesign right now, which will address a lot of coding and content specific issues, but we suspect .ca domain will always hold us back in achieving good positions on Google.com. Since Google doesn’t allow ccTLDs to set geo-targeting, what are our options? a) Migrating to a brand new .com site and setting up 301 redirects for all links from iCraft.ca. Would we lose all rankings in this example and pretty much start building them from scratch? Or would PR be transferred page by page from one domain to another through 301 redirects? b) Setup a separate .com site with mirrored content to target global audience and keep .ca site to target Canada. Not sure if splitting PR for the same pages between 2 sites is a good idea. Also, how would you address duplicate content properly in our situation?
International SEO | | MarinaUX
In this video that I found here on forum http://www.youtube.com/watch?v=Ets7nHOV1Yo Matt Cutts says that it’s ok to have duplicate content on different ccTLDs, but he says - make sure you localize your content on those domains. What if you can’t? Most of the content on our site is meant for anyone, not just Canadian users. So, for the most part, we’d have exactly same content on .com site, as we have on .ca site. We could display prices in different currencies on product pages, but the rest of the content – blogs, forum etc. are not country-specific and can’t be localized easily. Also, it’s not clear from the video if all mirrored sites should sit on the same domain name for each country, like example.com and example.ca or is it ok to have example.com and icraft.ca? c) Is there a better option? Thanks for your help!0 -
Ranking well in Google US but not showing up in UK
Hi, We are trying to position a specific site for a big sport event that will be played at the end of May. We only care about Google UK. It had no relevant content until last week. The site is a almost a year old but we just started to get links for it (all from the UK). They worked so fast: we were in page 2 of SERPs in the UK within a few days. But suddenly the site has disappeared and we're not even in top 100 anymore. However, we are ranking extremely well in the US (first page for the keywords we wanted to rank for). The site is a .com and it's hosted in Wordpress.com (with a custom URL). I understand that that can be a problem, but we have already told Google that our business is in the UK through Webmaster Tools. I guess that with time and more UK links, Google would ultimately understand that our focus is the UK audience, but unfortunately we have no time and we can't wait due to the date of the sport event. What do you think that we can do to rank well in the UK and not in the US as fast as possible? Thanks!
International SEO | | jorgediaz0 -
Do non-english(localized) URLs help Local SEO and user experience?
Hi Everyone, This question is about URL best practice for multilingual websites. We have www.example.com in English and we are building the exact replica of English site in German www.example.de. On the Geman site, we are considering to translate some portions of the URLs for example last folder and file name as seen below: example.de/folder1-in-english/folder2-in-english/folder3-in-german/filename-in-german.html Is this a good idea? Will this help SEO and user experience both? or the mixed languagues in URL will confuse the users? Google guidelines say that this should be ok. Would love to get feedback from SEOMOZ community! Thanks, Supriya.
International SEO | | Amjath0