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
-
Multilang site: Auto redirect 301 or 302?
We need to establish if 301 or 302 response code is to be used for our auto redirects based on Accept-Language header. https://domain.com
International SEO | | fJ66doneOIdDpj
30x > https://domain.com/en
30x > https://domain.com/ru
30x > https://domain.com/de The site architecture is set up with proper inline HREFLANG.
We have read different opinions about this, Ahrefs says 302 is the correct one:
https://ahrefs.com/blog/301-vs-302-redirects/
302 redirect:
"You want to redirect users to the right version of the site for them (based on location/language)." You could argue that the root redirect is never permanent as it varies based on user language settings (302)
On the other hand, the lang specific redirects are permanent per language: IF Accept-Language header = en
https://domain.com > 301 > https://domain.com/en
IF Accept-Language header = ru
https://domain.com > 301 > https://domain.com/ru So each of these is 'permanent'. So which is the correct?0 -
.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 -
Need help with search results for US site for a compnay that has many international sites
I am tasked with optimizing a US site for a company that has many international sites. Currently, if you search for just the main company name and don't include "USA" in your search, it won't even give you the US site on the SERP. It displays the Italian, French, etc etc sites - even though I'm searching on Google in the US with a preferred language of Engilsh. Unfortunately I don't have any control over the other sites, only the US one. Is there anything I can add to the US site (aside from setting the country code in GSC) so that when someone searches from within the USA, they get the US site and not all of the other ones? thanks!
International SEO | | SEOIntouch0 -
Prevent us.domainname ranking for UK searches
Hi Moz Community, I'd appreciate any advice you can offer on this. We have a client with international offices, and we manage the website and SEO for some of these offices, including UK. Others, such as their US office, are managed by another agency. All websites have the same domain name, but differ in their sub domains depending on their targeted country, e.g. uk.domainname for UK, us.domainname for US. All are .com. The US office's agency re-desgined their us.domainname website earlier this year. We noticed a couple of months ago that the US website started to outrank the uk.domainname website for branded searches on Google from the UK. After some investigation, we found that their agency had incorrectly implemented hreflang tags and set the us sub-domain as the hreflang="x-default" instead of www.domainname. They corrected this and uk.domainname is now the first organic result on Google. However, us.domainname has remained in 2nd place for organic brand searches (from Google UK) for the past two months, when we were hoping that this would have dropped out of the rankings by now. We have asked the US office to ensure that their International Targeting is set to United States in Google Search Console, but have no way of knowing if this has actually been done. Does anyone have experience of this? Is there anything else we could try to stop the US site ranking for Google UK, or is it just a matter of waiting? Many thanks, James
International SEO | | mcmnetjames0 -
Wants to Rank Well in Multiple Countries
We have been using moz subscription from last few months & are quite happy so far. We just wanted to explore more out of it & wanted to understand how to approach the optimization for having us rank well in US. At the same time we don't wanted to lose upon what we have achieved till now. I have read through some blog posts & found that changing the international targeting in GWT can also hurt. My vision is to rank well in multiple countries but at the same time do not lose rankings in India. Any help here would be appreciated so whatever we do, we do it right.
International SEO | | fourseven0 -
How to handle rel canonical on secondary TLD's - multi regional sites.
I currently have a .com domain which I am think of duplicating the content on to another tld, CO.UK (and regionalize some aspects like contact numbers etc). From my research, it seems that in gwt you must then indicate which country you wish to target, in the co.uk case the UK. My question is how should I handle rel canonical in the duplicated site. should it rel canonical back to the .com or the co.uk? Any other pointers would also be appreciated. Thx
International SEO | | dmccarthy0 -
Correct Hreflang & Canonical Implementation for Multilingual Site
OK, 2 primary questions for a multilingual site. This specific site has 2 language so I'll use that for the examples. 1 - Self-Referencing Hreflang Tag Necessary? The first is regarding the correct implementation of hreflang, and whether or not I should have a self-referencing hreflang tag. In other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), I am uncertain whether the source code should contain the second line below: Obviously the Spanish version should reference the English version, but does it need to reference itself? I have seen both versions implemented, with seemingly good results, but I want to know the best practice if it exists. 2 - Canonical of Current Language or Default Language? The second questions is regarding which canonical to use on the secondary language pages. I am aware of the update to the Google Webmaster Guidelines recently that state not to use canonical, but they say not to do it because everyone was messing it up, not because it shouldn't be done. So, in other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), which of the two following canonicals is correct? OR For this question, you can assume that (A) the English version of the site is our default and (B) the content is identical. Thanks guys, feel free to ask any qualifiers you think are relevant.
International SEO | | KaneJamison1 -
Same language many countries
Hello, I live in Belgium and in this country you've 3 languages : french, dutch and german. I've customers from many countries : France, Nederlands,... and for my website in ".be" (we'll say www.mysite.be for example) I've choosen the french language. My question is can I've the same content on my site : www.mysite.be and www.mysite.fr without duplicate content or should I forgot using www.mysite.fr to avoid the D.C. problem? And with my site : www.mysite.be should I've more difficult to rank in France for example? Thank you for your answer, Jonathan
International SEO | | JonathanLeplang0