Multi-Country Duplicate Content
-
Hello,
We have an ecommerce site that serves several countries on the same .com domain - US, UK and CA. We have duplicate content across these countries because they are all English speaking so there is little variance in the pages and they each sell most of the same products. We have implemented hreflang into our sitemaps but we need to address the duplicate content. We were advised to canonicalize our UK and CA pages back to the duplicate US pages (our US pages account for the majority of our traffic and sales). This would cause the UK and CA pages to fall out of the index but the visitor would still be taken to the correct country's page due to the hreflang.
I'm leary about doing this because they are across countries. Is this ok to do? If not, how do we address the duplicate content since they are not on their own CCTLD's?
-
Kelli (sorry, I had the wrong name somehow?)
First let me clarify a few things.
- Is the content between the US, Canada, and UK the exact same but on different URLs?
- Is any of the content translated to cater to the different markets (spellings, word usage, etc.)?
- Does each country have the same product set, etc.?
The HREFLANG is not necessary unless you are changing the language in some way. I am not sure that is what you should be using here. But your answers will help me understand so I can tell you what to do.
Check out my tool here to help: http://www.katemorris.com/issg/
-
It is of course slightly harder to answer without seeing any examples. However, assuming that the canonicalisation of Products B & C is the right thing to do in the first place, then I'd suggest that you should be consistent with your canonicalisation.
So, if you're canonicalising Products B and C to Product A on the US site, you are asking Google "please don't deliver B and C in search results; deliver A instead". If you are to then start canonicalising UK content to B & C then, as you rightly point out, that creates a chain of canonicals. The purpose of canonicals is to help Google to identify the single page (within a group) that they should deliver to their users. So it wouldn't make sense to canonicalise to one page which then canonicalises to another, IMO.
As for having to use both the canonical and rel-alternate-hreflang attributes, I have to say I'm surprised. I read this and strangely there is no mention of the canonical - it seems to suggest that this is the solution you've been looking for! However, clearly that's not been your experience.
Perhaps a silly question - but have you checked that you have rel-alternate-hreflang has been implemented correctly? E.g. have you implemented on a page-by-page basis, as opposed to a site-level basis? From the Google thread:
"rel="alternate" hreflang="x"
is used as a page level, not a site level, and you need to mark up each set of pages, including the home page, as appropriate. You can specify as many content variations and language/regional clusters as you need." -
Here's another question, if we do canonicalize our UK and CA pages back to the corresponding US pages, how should we handle the following scenario where most of our products are in 'groups' meaning there are very slight variances, but they are the same product:
US Site
Product A - canonical
Product B - canonicalizes to A
Product C - canonicalizes to AUK Site
Product A - canonicalizes to US version of A
Product B - canonicalizes to US version of B - OR - canonicalizes to US version of A??
Product C - canonicalizes to US version of C - OR - canonicalizes to US version of A??With thousands of products, canonicalizing to the exact duplicate page may be much easier to implement, but there will be a chain of canonicals.
-
I used to think the same thing, but it seems that Google has been unclear on the effects of hreflang as to whether it addresses duplicate content because at one time they said to use hreflang together, then they crossed it off of their guidelines, now they say it's ok. Based on my research, I'm thinking it's ok to use together as long as the languages aren't different, for instance, variations of English is ok, but don't use it with English and Spanish together because they are completely different.
Here is a snippet from http://searchengineland.com/cutting-through-the-confusion-of-googles-guidance-to-multilingual-website-owners-113586 which reads:
The Effect Of Combining Canonical Tags & Hreflang Tags
Not forgetting that the canonical tags should only be used with content in the same language, when would we use both? Well firstly, the use of both would involve what I usually call world languages such as English, Spanish, French or Portuguese. These languages are used in many countries and, whilst there are variations between the use of these languages in those countries, the variations are sometimes small. A__dditionally, multinational publishers often save costs by using one version of the language for all countries speaking that general language, thus ignoring the regional variations. In other words, for Spain and Mexico, Google is presented with exactly the same content, letter for letter. The canonical acknowledges that this is the same content. The Hreflang tag identifies which URL should be displayed in different sets of results. So, in other words, canonical + Hreflang = same content + different URL. Google knows the content is the same, but displays the correct URL for the Google domain search (e.g. google.com.mx will see the relevant URLs for Mexico displayed in the results).
This is also another good article from Distilled: http://www.distilled.net/blog/distilled/distilledlive-london-a-few-thoughts-on-hreflang/
Also, when a page canonicalizes to another page, it eventually drops out of the 'Duplicate Meta Descriptions' area of Google Webmaster Tools. We have had the hreflang implemented for some time, and none of the 'cross-country' pages are dropping out.
-
I thought that the whole point of rel-alternate-hreflang was to deal with the duplication of content when delivering the same or similar content to users in different locales.
For example, you have two sites - 1. US example.com and 2. UK example.co.uk. You sell the same products in both countries and the content on the sites is exactly the same. So there are two sites with exactly the same content, but the currency and delivery information etc is different.
If you implement on the .com site and on the .co.uk site, that means you don't need to implement the canonical tag.
At least that's how I understand this - I don't see the point of hreflang if you start having to mess around with canonicals etc.
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
-
Duplicate Content Regarding Translated Pages
If we have one page in English, and another that is translated into Spanish, does google consider that duplicate content? I don't know if having something in a different language makes it different or if it will get flagged. Thanks, Ruben
International SEO | | KempRugeLawGroup1 -
How should I handle hreflang tags if it's the same language in all targeting countries?
My company is creating an international version of our site at international.example.com. We are located in the US with our main site at www.example.com targeting US & Canada but offering slightly different products elsewhere internationally. Ideally, we would have hreflang tags for different versions in different languages, however, it's going to be an almost duplicate site besides a few different SKUs. All language and content on the site is going to be in English. Again, the only content changing is slightly different SKUs, they are almost identical sites. The subdomain is our only option right now. Should we implement hreflang tags even if both languages are English and only some of the content is different? Or will having just canonicals be fine? How should we handle this? Would it make sense to use hreflang this way and include it on both versions? I believe this would be signaling for US & Canda visitors to visit our main site and all other users go to the international site. Am I thinking this correctly or should we be doing this a different way?
International SEO | | tcope250 -
Why Google is not indexing each country/language subfolder on the ranks?
Hi folks, We use Magento 2 for the multi-country shops (its a multistore). The URL: www.avarcas.com The first days Google indexed the proper url in each country: avarcas.com/uk avarcas.com/de ... Some days later, all the countries are just indexing / (the root). I correctly set the subfolders in Webmaster tools. What's happening? Thanks
International SEO | | administratorwibee0 -
Country specific SEO
Hi I have a question regarding country specific SEO and what would the best approach be? I have website A which is currently ranking well in Google country A, I would now like to introduce a new website B which is only specific to users in Google country B. The only difference between the 2 websites is that website B will have different prices and products for the users in Google country B. From a development point of view we would like to only have one instance of the website which can be served to users in country A and B all that we would do is change some of the content and prices based on the user IP which means that users in country A see a different version of the website to users in country B. Is this approach fine from and organic point of view? Or would we need to have 2 separate websites and make use of Href Lang?
International SEO | | Iannaude0 -
Multi Regional Website Best Practices
Hi there, I have a website that is targeting 3 countries AU/US & NZ. I have set up hreflang tags for each page on each of the site however I am having difficulties getting it work right. I read this article which was a great insight into the hreflang tags. https://moz.com/blog/hreflang-behaviour-insights and as a result I have implemented hreflang tags in the following manner: When users access the root domain http://[website] it will redirect the user to their locale with a 302 redirect. I have a few questions:
International SEO | | nathanfranklin
1. When building my external link profiles, I'm not sure if I should be building link profiles for http://[website]/ or for the geo graphical pages (http://[website]/aus/ etc..). Note that the http://[website]/ is never used, it just issues a 302 to the actual geographical location. 2. It seems that the hreflang tags are not working correctly. Perhaps its the result of the 302 on the root page, but in google.com.au (using the link http://www.google.com.au/search?hl=en&gl=au&pws=0&q=[branded search]) I would expect that I should see the search results for /aus/ given the fact that the hreflang tags are setup as en-au. Instead I am seeing the root domain page. Is that correct or should it be showing all the pages with /aus/. ALSO If I do a search in google thailand (http://www.google.com.au/search?hl=en&gl=th&pws=0&q=[branded search]) it returns the /aus/ version where it should be showing the /us/ using the x-default hreflang tag. In google webmaster tools I have setup 4 site profiles:
http://[website]/
http://[website]/us/
http://[website]/aus/ (Targeted to Australia)
http://[website]/nz/ (Targeted to New Zealand) Any help would be appreciated. Thanks Nathan1 -
Specific page URL in a multi-language environment
I've read a lot of great posts on this forum about how to go about deciding the best URL structure for each language that your site will support, so thank you to everyone that has provided input on that. I now have a question that I haven't really found answers/opinions on. When providing a page translation, should my content URL reflect that of the country I'm targeting or always remain the same across all sites? Below is an example using the "About Us" page. www.example.com/about-us/
International SEO | | Matchbox
www.example.com/es-mx/about-us/ -- OR -- www.example.com/about-us
www.example.com/es-mx/sobre-nosotros Thank you in advance for your help. Cheers!0 -
Geotargeting two locations using root and /country
Hello, I am in the process of turning my UK targeted website into a global website in multiple languages. I will be using the new HREFLANG tag but I'm wondering about geotargeting. I've set this up in Webmaster Tools as: example.com = UK content
International SEO | | Seaward-Group
example.com/us = US content
example.com/de = German content
example.com/es = Spanish content
example.com/fr = French content
example.com/it = Italian content
example.com/nl = Dutch content Will the root UK content override the following sub directories that are set as a different location because its not /uk? Thank you.0 -
Subdomain hosted in a different country - what are the implications?
Hello, We are looking at creating an eCommerce section to a website and we are just weighing up the options: Magento - host on hour own server - great but it can often be very slow when hosting a shared server. Shopify - hosted solution but hosting is in the US and we are in the UK and shop will be hosted on a subdomain as a result Build our own solution - time consuming and costly There are two issues that have arisen from this situation.... Is it worse for SEO to host your store in a different country or to host in your country but your store potentially run slower? I'm swaying to the side of the argument that says give your users a good and fast experience instead of worrying about where you host the store. Bearing in mind that the main website will be hosted in the UK anyway and it is just the subdomain that will be hosted in the US. Just wondered if anybody has had experience with this or if I'm missing something? All feedback greatly appreciated! Thanks, Elias
International SEO | | A_Q0