International hreflang - will this handle duplicate content?
-
The title says it all - if i have duplicate content on my US and UK website, will adding the hreflang tag help google figure out that they are duplicate for a reason and avoid any penalties?
-
hreflang and geo-targeting are in fact two different things.
If you have exactly the same content, no changes for the regional variations in the language, hreflang is not intended for that.
Why do you have two sets of pages that are the same? If you have the same content on .com with no geo-targeting, then Google is going to offer up the original content on .com rather than /lu because you never changed the content in any way to target Luxembourg. Had you changed the content to translate or really geo-targeted the content to that audience, I think the situation would be different.
Check my tool here, answer the questions and see what is right for your situation. Then follow the instructions at the end.
-
After reading this thread, I have decided to implement this solution in order to target multiple countries. In my case France and Luxembourg.
My website URL uses a gTLD such as www.example.com. The content is in French.
I have duplicated all pages and blog posts in a subfolder /lu and I have used the hreflang markup to indicate that the content is either in fr-lu or fr-fr.
In the Google WebMaster Tools, I have geo-targeted the /lu subfolder to Luxembourg. For the main domain I have not targeted any country.
After a few days, my website started ranking much better on google.lu than it used to be. It lasted a month or so, but today www.example.com/lu/ has lost dozens of positions for my keywords of interest. In fact www.example.com ranks #20 on google.lu and seems to have replaced www.example.com/lu/ which ranked #12 and is now nowhere to be found....
I have no idea why this happened. Like I said the content is indeed duplicated, but I have used hreflang to make it clear that I'm targeting a specific country.
What should I do ?
-
Thanks Kate! This is really helpful. I guess we will go with no hreflang tag, and just .com and .co.uk sites
-
Tommy is getting to the point but things are still very confusing when it comes to international.
Can you go check out this flow chart, see what is best for your business, and then let me know? http://www.distilled.net/wp-content/uploads/2013/05/International-Search-Strategy-Guide.pdf
That should answer most of your implementation questions as well, but I want to make sure it make sense. So check it out first and let me know.
But if what I am assuming is the case that you have geo-targeted sites and there is no translation going on within the geotargeted sites (.com and .co.uk), then HREFLANG is not needed. What I mean by translation isn't happening in the site is that the .com (US) site isn't translated to Spanish or any other language. And the same in the UK. If no translation is happening within a geo-targeted site, HREFLANG is not necessary.
Let me know what you're trying to do with geo-targeting and international strategy and I can help better answer your question.
-
HI Alice,
Just want to confirm whether your US and UK site is under the same domain or different domain. If it is different domain, the ccTLD domain (.com and .co.uk) should've solved the issue since Google will understand that each domain is targeting the different location. However, both website are under same domain (using subdomain or directories) then the hreflang tag will solve the issue. This tell Google that the site with hreflang="en-us is targeting US and the other to UK.
Hope this can help a bit
-
Didn't know about that last tag!
haha you and Lesley are giving me 2 different answers, so I'm even more confused!
Hopefully more people can chip in their comments?
-
Yea we are currently working on producing different content, including complete separate content + converting US to UK english, but there are some pages where duplicates are unavoidable.
I also thought this tag was not to handle duplicate content at all, but when you think about it more that is essentially what it is doing - it exists for websites that have the exact same content in 2 separate languages. It's just a bit confusing when you have US and UK, since the language is the same, but there are still separate hreflag tags for them...
-
I think hreflang is intended for your very situation. Check out Google's guidelines which will very much confirm this. What you should do is reference both the UK and US URL on both versions of the content, so for example you would add this to both versions.
If you intend to have a default 'en' version which doesn't target any specific locale then you might want to add as well.
Ideally, of course, as Lesley suggests, you should provide content that is unique in each locale, but resource-wise this is not always possible and that is why hreflang will help you in this instance and will help avoid duplicate issues. In theory your US URL should appear in Google.com and your UK URL should appear in Google.co.uk, but it can take a while for Google to catch up and reflect this in SERPs.
-
From my understanding, that is not what that tag is for. You can read more about it here, http://googlewebmastercentral.blogspot.com/2013/04/x-default-hreflang-for-international-pages.html
As a suggestion, I would recommend having different content. Just because they both speak english, it does not mean that they speak the same flavor of english. If you can change the content enough to suit the people in the UK I think you will have better overall results.
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
-
International targeting
I submitted each language URL as a separated website to google webmasters, I've submitted Hreflang sitemap which has language codes only(without countries codes) each page in my website has hreflang language and country code. Should i use international target option for each language to target the countries? will that hurt the language targeting? or I have to leave international targeting option unchecked for each language? My Goal to target by languages, not countries.
International SEO | | MTBE0 -
Providing a default hreflang for translations
I've been doing a lot of research on hreflang and had a question regarding the implementation with location targeting. I have a translation for Brazilian Portuguese, I'd like to target Brazil with this translation on my site but also provide it as the default for other users that speak Portuguese outside of Brazil. Can I use the same translation for two different sites? So my hreflang would look like this: So in this example the pt-br and pt sites would be duplicates but with one being specifically targeted to Brazil and the other for all other people speaking Portuguese anywhere else in the world. The default language of the site is English so the full implementation would look like this:
International SEO | | Brando160 -
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 -
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?
International SEO | | jennifer.new0 -
What is the proper way to setup hreflang tags on my English and Spanish site?
I have a full English website at http://www.example.com and I have a Spanish version of the website at http://spanish.example.com but only about half of the English pages were translated and exist on the Spanish site. Should I just add a sitemap to both sites with hreflang tags that point to the correct version of the page? Is this a proper way to set this up? I was going to repeat this same process for all of the applicable URLs that exist on both versions of the website (English and Spanish). Is it okay to have hreflang="es" or do I need to have a country code attached as well? There are many Spanish speaking countries and I don't know if I need to list them all out. For example hreflang="es-bo" (Bolivia), hreflang="es-cl" (Chile), hreflang="es-co" (Columbia), etc... Sitemap example for English website URL:
International SEO | | peteboyd
<url><loc>http://www.example.com/</loc></url> Sitemap example for Spanish website URL:
<url><loc>http://spanish.example.com/</loc></url> Thanks in advance for your feedback and help!0 -
Are Subdomains better or SubDirectories better for an international website ?
Can anyone explain why the structure of your website: yourbrand.com/es/category is better than es.yourbrand.com for multi language and multi country website.
International SEO | | Tushar_P0 -
International SEO | URL Structure
I'm looking for advice/point of view for setting up international domains. I.e. sub-domains, ccTLD, etc. At the 10,000 ft. view - the client (international retail company) is trying to decide which type of URL structure to use in their new platform: Option 1: Root Domain ccTLD - www.brand.ca, www.brand.fr, etc. Option 2: Subdomains - fr.brand.com, ca.brand.com, au.brand.com Option 3: Subfolders - ]www.brand.com/ca/, ]www.brand.com/au/ Consider these scenarios/questions and use to help decide which URL structure makes sense: 1) I'm an Aussie in Australia and I do a Google search on Hank Myer Aron, which is a huge seller in the U.S. and also included at the Australia locale site. If we go with subfolders, am I likely to see the U.S. Aron page higher in my search results than the Australia Aron page? Or is the U.S. site not a factor in a search done outside the U.S.? If we use subfolders AND geo-detection, does this bump the ranking of the locale page? Do sites using ccTLDs always get ranked above those that don't? For example, if an Australian dealer selling Aron has URLs dealer.com.au/..., would their pages rank ahead of hankmyer.com/au/...? If we went the ccTLD route, would the Aron page at hankmyer.com.au take precedence over the U.S. page? (Again, assuming U.S. site is relevant in this scenario.) 2) I'm a Frenchman in France searching on Hank Myer Aron. If we use subfolders AND an alias URL that's translated to French (brand.com/fr/produits/sieges/sieges-aron), would we expect the page rank to be comparable to using the ccTLD and/or expect greater trust than just using subfolders without translated URLs? Do translated URLs have any mitigating affect on duplicate page content? Which URL strategy is best choice from a SEO standpont?
International SEO | | CrownPartners0 -
International SEO - auto geo-targetting
I read with interest the recent post on international SEO and the top level domain architecture approaches to local content: http://www.seomoz.org/ugc/folders-vs-subdomains-vs-cctld-in-international-seo-an-overview#jtc135670 The issue I have is a little more complex: The business sells a wide variety of products (37) but one is by far and away the biggest and most popular. This means that due to the link profile of the various country sites and HQ site, search engines categorise the site according to this product (this is easily seen with the Google Adplanner) and the other product lines suffer as a result. The current architecture is to have a .com site and then individual ccTLD country sites, again with all products on each site. This creates an issue as in most countries the brand is not strong (compared to the keyword names and search volumes of the products) and so it is not that effective in generating organic traffic. The .com hogs much of the inbound links and the country sites themselves are not that well optimised for a number of reasons. A proposed solution has been to leverage the strength of the .com and the search volume for the product names, and to produce thematic sites based on each product: productA.brand.com
International SEO | | StevieCC
productB.brand.com
productC.brand.com In this way, the sites, content and link profiles are aligned around the more desirable products and we can expect improved organic search performance as a result (or at least ensure relevant traffic finds the relevant content fast). In terms of providing localised content, the plan was to use content mirroring and to then assign each content mirror to a specific geo-location using the webmaster tools console (and other SE equivilents). This is shown I think in one of Rand's videos. ProductA.brand.com/de/de Germany site for product A with unique German content
ProductA.brand.com/fr/fr French site for product A with unique French content This makes economic sense to me as to utilise the ccTLDs would result in hundreds of separate sites with all the licence and server considerations that entails. For example, for product A alone we would have to produce: productA.brand.de
productA.brand.fr
productA.brand.cn
productA.brand.jp
ect ect ect This just would not be sustainable in license/server costs alone across 37 products and 24 countries. However, I saw in a recent presentation at SES London that (auto) geo-targeting is risky, often doesn't work well for SEO and can even be seen as cloaking. I think the above strategy could still work, but perhaps we should avoid the use of auto-geotargetting altogether and hope the search engines alone do their job in getting users to the right content as we optimise the unique content for each country (and if they don't, ensure our desgn, UX and country selectors do the job instead). SEO guru consensus is to use the ccTLD if you own it, but as described above, in the real world that just isn't possible or practical given the company's strategic position. Which leads to the final question- we do own the brand ccTLDs- if they are directed back to the content mirror for the country on the .com, is there any SEO benefit in doing so aside from directing back any link juice associated with the domain)?0