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
-
Important pages are being 302 redirected, then 301 redirected to support language versions. Is this affecting negatively the linking juice distribution of our domain?
Hi mozzers, Prior to my arrival, in order to support and better serve the international locations and offering multiple language versions of the same content the company decided to restructure its URLs focused on locale urls. We went from
International SEO | | Ty1986
https://example.com/subfolder to https://example.com/us/en-us/new-subfolder (US)
https://example.com/ca/en-us/new-subfolder (CAN)
https://example.com/ca/fr-ca/new-subfolder (CAN)
https://example.com/de/en-us/new-subfolder (Ger)
https://example.com/de/de-de/new-subfolder (Ger) This had implications on redirecting old URLs to new ones. All important URLs such as https://example.com/subfolder were
302 redirected to https://example.com/us/en-us/subfolder and then 301 redirected to the final URL. According to the devs: If you change the translation to the page or locale, then a 302 needs to happen so you see the same version of the page in German or French, then a 301 redirect happens from the legacy URL to the new version. If the 302 redirect was skipped, then you would only be able to one version/language of that page.
For instance:
http://example.com/subfolder/state/city --> 301 redirect to {LEGACY URL]
https://example.com/subfolder/state/city --> 302 redirect to
https://example.com/en-us/subfolder/state/city --> 301 redirect to
https://example.com/us/en-us/new-subfolder/city-state [NEW URL] I am wondering if these 302s are hurting our link juice distribution or that is completely fine since they all end up as a 301 redirect? Thanks.1 -
What strategy is better for a multilingual site for the SEO point of view?
Hi everyone, in a case for a site with two languages like spanish and english, how would do you deal with it? I can see 4 cases, which is better?? 1. With differents domains: mydomain.es (for spanish version) and mydomain.com (for english version). 2. With subfolder mydomain.com/es/ and mydomain.com/en/ 3. With Subdomain: es.mydomain.com and en.mydomain.com 4 With URL translation (any url is translated in ther languages but not use of subdomain or subfolder): mydominain.com/hola and mydomiain.com/hello Thanks very much for your answers (i love this forum). 🙂
International SEO | | webtematica0 -
International SEO Mobile directory
I was wondering, What if I went with international sub-directory route (not ccTLD), for example: sitename.com/fr (fr being france)...But the question is, what's the best practice for MOBILE?sitename.com/mobile/frORsitename.com/fr/mobileORm.sitename.com/fr Again, ccTLD is not an option (currently, sites are in ccTLD but we are now transitioning to sub folders)Now, the next question is WHY is it best practices for it to be sitename.com/mobile/fr or sitename.com/fr/mobile or m.sitename.com/fr ? Please cite source. Thanks!
International SEO | | ggpaul5620 -
Auto-Redirecting Homepage on Multilingual Site
The website has an auto-redirecting homepage on a multilingual site. Here is some background: User visits the site for first time > sent to javascript age verification page with country of origin selector. If selects "France" then served French page (.com/fr-fr/). If selects any other country, then served English page (.com/en-int/). A cookie is set, and next time the user visits the site, they are automatically served the appropriate language URL. 1st Question: .com/ essentially does not exist. It is being redirected to .com/en-int/ as this is the default page. Should this be a 301 redirect since I want this to serve as the new homepage? 2nd Question:. In the multilingual sitemap, should I still set .com/ as the hreflang="x-default" even though the user is automatically redirected to a language directory? According to Google, as just released here: http://googlewebmastercentral.blogspot.com/2014/05/creating-right-homepage-for-your.html "automatically serve the appropriate HTML content to your users depending on their location and language settings. You will either do that by using server-side 302 redirects or by dynamically serving the right HTML content. Remember to use x-default rel-alternate-hreflang annotation on the homepage / generic page even if the latter is a redirect page that is not accessible directly for users." So, this is where I am not clear. If use a 302 redirect of .com/ to either .com/en-int/ or .com/fr-fr/, won't I then lose the inbound link value and DA/PA of .com/ if I just use a 302? Note: there is no .com/ at this moment. Any advice is appreciated. Thanks,Alex
International SEO | | Alex.Weintraub0 -
Cross domain rel alternate, will it help or hurt?
I have a website that has similar pages on a US version and a UK version. Currently we want Uk traffic to go to the US, but the US domain is so strong it is outranking the UK in the UK. We want to try using rel alternate but have some concerns. Currently for some of our keywords US is #1, UK is #4. If we implement rel alternate, will it just remove our US page? We don't want to shoot ourselves in the foot and lose traffic. Is this worth doing, will it just remove our US ranking and our double listing? Any anecdotes, experiences or opinions are appreciated. Thanks.
International SEO | | MarloSchneider0 -
How to optimise a site for 2 countries
Hi there - Any help with the below much appreciated I am helping an Australian company, producing packaging products for businesses. Their site is hosted in Australia and their offices are in Australia. They have asked me to take care of both on-page and off-page SEO so that they rank for keywords related to their products - e.g. 'cardboard boxes'. This should be fairly straightforward for Australian based (.com.au) searchers, but they also supply their products to South Africa, and so want their results to show up also for South African based (.co.za) searchers. Also consider: it is not typical for searchers for these products to use geomodifiers in their search terms there is no unique content for the South African market versus the Australian... the product information is essentially identical. What should we do to ensure their results show up equally for those in South Africa as well as Australia? I am considering building a completely separate site, hosted in South Africa and specifically for the S.A market, but will the duplicate content effect be an issue? Also, this would essentially mean double the SEO effort, is there no way I could achieve our goals more efficiently? many thanks to any help
International SEO | | dnaynay0 -
Does it matter whether you use /en vs /uk
I have a global site targeting many countries including the UK which is the only English language site. Does it matter whether I use /en or /uk for the UK sub-folder? If I already have /en in place, but my Google UK listings are struggling, will it benefit me to switch to /uk? I honestly don't think it matters too much, but given the choice would've gone for the /uk I'm trying to weigh up whether it is worth the effort of changing it.
International SEO | | Red_Mud_Rookie0 -
Different country, same language
I have read the blog posts by Rand and other community members at YouMoz but i still have a question on trageting and domains / sub-directories usage. Suppose, my business is located in France but my prospects are in US and UK as well. The issue is, they are not English speakers but French. If i use ccTLD, i don't think it will rank well in US and UK. gTLD will not be a good option for prospects in France. What should i do? Regards, Shailendra
International SEO | | IM_Learner1