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
-
Should Hreflang x-default be on every page of every country for an International company?
UPDATED 4/29/2019 4:33 PM I had made to many copy and pastes. Product pages are corrected Upon researching the hreflang x-default tag, I am getting some muddy results for implementation on an international company site older results say just homepage or the country selector but…. My Question/Direction going forward for the International Site I am working on: I believe I can to put x-default all the pages of every country and point it to the default language page for areas that are not covered with our current sites. Is this correct? From my internet reading, the x-default on every page is not truly necessary for Google but it will be valid implemented. My current site setup example:
International SEO | | gravymatt-se
https://www.bluewidgets.com Redirects to https://www.bluewidgets.com/us/en (functions as US/Global) Example Countries w/ code Site:- 4 countries/directories US/Global, France, Spain Would the code sample below be correct? https://www.bluewidgets.com/us/en/ (functions as US/Global) US/Global Country Homepage - https://www.bluewidgets.com/us/en/ US/Global Country Product Page(s) This would be for all products - https://www.bluewidgets.com/us/en/whizzer-5001/ http://www.bluewidgets.com/us/en (functions for France) France Country Homepage - https://www.bluewidgets.com/fr/fr/ France Country Product Page(s) This would be for all products- https://www.bluewidgets.com/es/es/whizzer-5001 http://www.bluewidgets.com/us/en (functions as Spain) Spain Country Homepage - https://www.bluewidgets.com/es/es/ Spain Country Product Page(s) This would be for all products - https://www.bluewidgets.com/es/es/whizzer-5001 Thanks for the spot check Gravy0 -
Country and Language Specific URL Paths
Wanted to ask everyone a questions: So our company is going to be doing a website that is going to be full of videos. The url path will be country.domain.com/language/slug/content-id. We redirect the user when they go to the different country. So if you're in spain on a train to france your URL will change from es.domain.com/es/slug/content-id to fr.domain.com/es/slug/content-id. Each country can listen to each video in all languages. My question is with hreflang tags and canonicals. Aside from targeting users in a certain country via Google Search Console, how do I eliminate duplication and tell Google which I'd like to show up via which country. In spain I would like es.domain.com/es/slug/content-id to show in Google and would have hreflang tags on each of the es.domain pages but what about fr.domain.com/es/slug/content-id since it would show the same content? I can't canonical to one of them since I need them to show in their respective country. How do I show the difference in language and country without showing duplication?
International SEO | | mattdinbrooklyn0 -
How to avoid duplication across multiple country domains
Here's the scenario: I have a client currently running one Shopify site (AU) They want to launch three more country domains (US, UK and EU) They want each to be a standalone site, primarily so the customers can purchase in their local currency, which is not possible from a single Shopify site The inventory is all from the same source The product desscriptions will all be the same as well Question: How do we avoid content duplication (ie. how will canonical tags work in this scenario)?
International SEO | | muzzmoz0 -
Can you target the same site with multiple country HREFlang entries?
Hi, I have a question regarding the country targeting aspect of HREFLANG. Can the same site be targeted with multiple country HREFlang entries? Example: A global company has an English South African site (geotargeted in webmaster tools to South Africa), with a hreflang entry targeted to "en-za", to signify English language and South Africa as the country. Could you add entries to the same site to target other English speaking South African countries? Entries would look something like this: (cd = Congo, a completely random example) etc... Since you can only geo-target a site to one country in WMT would this be a viable option? Thanks in advance for any help! Vince
International SEO | | SimonByrneIFS0 -
Duplicate content - news archive
Most of them are due to news items having more than 1 category – which is pretty normal.Also /us/blog, /uk/blog and /ca/blog are effectively the same page.None of them are actually duplicate content – just alternate URLs for the same pagehttp://www.fdmgroup.com/category/news/
International SEO | | fdmgroup0 -
Multi-Country Hosting
Hi all
International SEO | | yousayjump
I have read a few post that are similar to mine on this forum but still wanted to ask my specific question. We have a .com domain hosted on a dedicated server in the UK for our main website which takes online bookings and payments. We have purchased the following TLD's of our domain name:
.it, .es, .ch, .fr, .es, .at We essentially want to create a satellite site on each domain where the idea is that users in those countries will find our satellite sites via organic search engine results when searching for the information we sell. Due to the nature of our infrastructure, each satellite site will connect to the mysql database on the UK site to drawn down its text content. This is where the main CMS is located. I understand the following are important from an SEO point of view for our satellite sites: Hosting in the country we wish to target
Geographical targeting via WMT
Local addresses and telephone numbers on the site
Correct lang=" " tag in the source code
Content presented in the correct language (goes without saying really) Can you advise on any other considerations? Many Thanks Kris0 -
One global blog or a blog for each country?
We have a blog on each of our country sites, but the content on the English speaking sites is shared i.e. locally produced in US is mixed up with stuff produced in UK and vice versa. I'm not concerned about duplicate content because we have taken the necessary measures to let the search engines know that we have a US site for the US and and UK site for the UK. My question to you is whether we should develop the blog independently in each country or develop one blog to satisfy our global sites. I believe a local blog for each country is better because the content would speak to the audience better and any reference points or product and price points would be 100% relevant to the audience.
International SEO | | Red_Mud_Rookie0 -
How to improve SERP rankings in other countries?
We have a .com website in English targeting global visitors. We have good rankings on Google USA for our targeted keywords But we do not rank well in APAC e.g. Sigapore and Australia. What could we do to get ranked in these countries? We received a recommendation to sign up for .sg and .au domains and replicate our Website for Singapore and Australia. But wouldn’t it contribute to duplicate content Issue? We are in software industry and do not have locale specific content. Please advise.
International SEO | | Amjath0