Canonical and hreflang mess of international desktop and mobile site versions
-
Hello, I have an interesting case and I am lost in it. There are two versions of the site: desktop and mobile. And there are also international versions: English and Spanish. I'm stuck at implementation of canonical tags. Currently my setup has the following:
English (default) desktop page has these:
English Mobile page has these:
Spanish Desktop version:
Spanish Mobile version:
But I somewhat feel that I messed the things... Could you guys point me to what I did wrong and explain how to set it right? Also, if you know URLs of blog posts or articles, where similar case is explained - share with me please.
-
Just for my own organization. I know that in all the Google examples, the x-default tag is at the bottom. Overall, I don't believe it makes a difference.
-
Oleg,
did you change the order of the tags by intention? Canonical on top, x-default on bottom. Does the order matter?
-
Thanks.
I hope to get more responses from others to see if they agree with your solution.
-
I don't think it should be removed, that's why I included it.
-
Oleg,
Why do you think canonical tag should be removed from mobile pages?
-
Check out: https://www.youtube.com/watch?v=8ce9jv91beQ
English (default) desktop page has these:
http://www.site.com/">
http://www.site.com" hreflang="en">
http://www.site.com/es/" hreflang="es">
http://www.site.com" hreflang="x-default">
http://m.site.com/" >English Mobile page has these:
http://www.site.com/">
http://m.site.com/" hreflang="en">
http://m.site.com/es/" hreflang="es">
http://m.site.com/" hreflang="x-default">Spanish Desktop version:
http://www.site.com/es/">
http://www.site.com/es/" hreflang="es">
http://www.site.com/" hreflang="en">
http://www.site.com/" hreflang="x-default">
http://m.site.com/es/" >Spanish Mobile version:
http://www.site.com/es/"> http://m.site.com/es/" hreflang="es">
http://m.site.com/" hreflang="en">
http://m.site.com/" hreflang="x-default">
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
-
When should hreflang be deployed in this situation; now or later ?
Hi I have a question in regard to point 1 in Gianluca Fiorelli first comment on Aleyda Solis old but great international targeting article in regard to hreflang: https://moz.com/blog/using-the-correct-hreflang-tag-a-new-generator-tool it would obvs be amazing if either Gianlucca or Aleyda can answer but if anyone else feels they can do so confidently then that would be great too 🙂 I'm advising someone in similar situation as that (their main brand is USA based on a .com showing up in UK searches too) and they have launched .co.uk sites (without any seo) to target UK brand searches, so obviously the .com is still dominating UK serps for brand, and the .co.uk is ranking on page 4 on average for a brand search. **BUT **before I tell them to roll out hreflang shouldn't they build up some authority etc first for their new country specific (.co.uk) site ? since they are very new and have no authority or even basic SEO and don't rank higher than page 4 for brand searches (the .com is in no1 in both usa and uk). I know hreflang needs to be used correctly here but im not sure when it should be, now or later (after authority has built up for the new uk focused sites) ? In other words I take it deploying the hreflang correctly wont simply cause these home pages to swap positions for brand search in uk (or will it) ? Im worried deploying it immediately could actually destroy the brands current page 1 serps for brand term (since will remove the .com page from the uk serp). Hence i take it its best to build up the new .co.uk sites seo/authority etc first and at least get that sites brand ranking moving up the listings before deploying hreflang on the .com, to then hopefully remove the .com listing in place of the .co.uk for brand ? OR does Gianlucca point in his comment suggest that correct hreflang usage on both sites should swap the high authority .com no1 position with the low authority .co.uk for a brand search ? Many Thanks Dan
International SEO | | Dan-Lawrence0 -
MultiRegional site indexing problems
Hello there!!! I have a multiregional site and dealing with some indexing problems. The problem is that google have only indexed our USA site We have: -set up hreflang tags -set up specific subdirectories https://www.website.com/ (en-us site and our main site) https://www.website.com/en-gb https://www.website.com/en-ca https://www.website.com/fr-ca https://www.website.com/fr-fr https://www.website.com/es-es ..... -set up automatic GEO IP redirects (301 redirects) -created a sitemap index and a different sitemap for each regional site -created a google webmaster's tool for each country targeted -created translations for each different language and added some canonicals to the US' site when using English content. The problem is that Google is not indexing our regional sites. I think that the problem is that google is using a US bot when spidering the site, so it will be always redirect to the US version by a 301 redirect. I have used fetch as google with some of our regional folders and asked for "Indexing requested for URL and linked pages", but still waiting. Some ideas?? changing 301 to 302? Really don't know what to do. Thank you so much!!
International SEO | | Alejandrodurn0 -
US site vs New Canadian site for Brand
Hi Everyone, My company decided to create a Canadian site for Canadian customers. How do I slowly transition the US site for ranking in Google.ca? I was thinking of using robots.txt to block Google.Ca from crawling the US site? Can anyone provide some advice oh how this should be managed? Thank you!
International SEO | | JMSCC0 -
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 -
Alternate Hreflang Problem
We have two travel websites.
International SEO | | Izzet
One in English language for people living in the UK.
One in Turkish language for people living in Turkey. The major difference is:
English (UK) website shows 4+ nights accomodation prices because UK travellers never come for less than 4 nights.
Turkish website shows 1-night, 2-night, 3-night prices because Turkish travellers never stay for more than 3 nights. We are using rel="alternate" hreflang="x" tags properly on our two websites. Today, I am disappointed to see Google display the wrong result. When a user in Turkey searches a Turkish keyword on Google.com.tr;
Google is showing the English language website. When I click on Search Settings > Language;
I see that English is selected under this question:
"Which language should Google products use?" This is a big problem for us.
Many rich users in Turkey, who are more willing to buy our services, speak English fluently and they may choose to use Gmail in English. But we are losing business because these Turkish customers don't convert at all on the Enlish (UK) website because of the reason I explained above. 1) What can we do?
2) If we remove the rel="alternate" hreflang="x" tags now, will it hurt any of the websites?
We have seen an increase in Google rankings for the Turkish language website after using rel="alternate" hreflang="x" tags. Izzet0 -
Are my hreflang and canonical link tags set correctly?
Currently we have a website in english but over time we will roll out parts of the whole site in different languages for different countries which will also result in country specific English versions of the website. The goal is that Google shows the country specific version of a page in a native language or English if available or falls back to the default English version of the same page otherwise. I listed below how we plan to use hreflang and canonical link tags to achieve this and was hoping to get some feedback from the Moz community if this will work as expected. (1) A page (www.mysite.com/page1) exists only in English as default. Users should be able to find it in every country unless there is an English version specifically for this country. We would use the following tags: (2) A page exists in English (www.mysite.com/id/en/page2) and Bahasa (www.mysite.com/id/id/page2) for a specific country (Indonesia in this case). Users in Indonesia searching in English should find the country specific English page. Indonesians searching in Bahasa should find the Bahasa version of that page. We would use the following tags on the English version: and therefor the following tags on the Bahasa version: In this case there wouldn't be a default English version available for the page. (3) If a page exists in English global, English for Indonesians and Bahasa for Indonesians we would use: on www.mysite.com/id/en/page3 on www.mysite.com/id/id/page3 on www.mysite.com/page3 If www.mysite.com/id/en/page3 and www.mysite.com/page3 are very similar we would risk google picking the page they want to rank for an english keyword searched in Indonesia, correct? (4) If a page in (1) and (2) can be reached with a different URL, we would only use a canonical and don't specify any hreflang tags e.g.: www.mysite.com/en/other-url-to-page1 or
International SEO | | ddspg
www.mysite.com/id/en/other-url-to-page2-english-indonesia (5) If a page that exists as global English page becomes available in English for a specific country as e.g. www.mysite.com/uk/en/page1 we would use the following tags: and also add one more hreflang to www.mysite.com/page1: The assumption here is that Google would rank the localized page instead of the global page after crawling our site again. But since this will be a new page, are we going to lose traffic because www.mysite.com/uk/en/page1 won't rank as well in the beginning (e.g. no offsite optimization)?0 -
Upper case or/and lower case in rel="alternate" hreflang
Hi Mozzers, I have a question about the rel="alternate" hreflang tag, with an example. When I use two subfolders for two different countries/languages, for instance www.domain.com/nl-nl/ and www.domain.com/nl-en/ (for the English version) and I want to use the rel="alternate" hreflang tag, do I need to follow the ISO standards concerning Uppercase country code and Lowercase language code (en-NL)? Or is it okay to use the Lowercase country and language code (en-nl), since we also use this in the URL of the Subfolder. What does Google prefer? Thanks in advance.
International SEO | | MartijnHoving820 -
Multi-lingual SEO: Country-specific TLD's, or migration to a huge .com site?
Dear SEOmoz team, I’m an in-house SEO looking after a number of sites in a competitive vertical. Right now we have our core example.com site translated into over thirty different languages, with each one sitting on its own country-specific TLD (so example.de, example.jp, example.es, example.co.kr etc…). Though we’re using a template system so that changes to the .com domain propagate across all languages, over the years things have become more complex in quite a few areas. For example, the level of analytics script hacks and filters we have created in order to channel users through to each language profile is now bordering on the epic. For a number of reasons we’ve recently been discussing the cost/benefit of migrating all of these languages into the single example.com domain. On first look this would appear to simplify things greatly; however I’m nervous about what effect this would have on our organic SE traffic. All these separate sites have cumulatively received years of on/off-site work, and even if we went through the process of setting up page-for-page redirects to their new home on example.com, I would hate to lose all this hard-work (and business) if we saw our rankings tank as a result of the move. So I guess the question is, for an international business such as ours, which is the optimal site structure in the eyes of the search engines; Local sites on local TLD’s, or one mammoth site with language identifiers in the URL path (or subdomains)? Is Google still so reliant on TLD for geo targeting search results, or is it less of a factor in today’s search engine environment? Cheers!
International SEO | | linklater0