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
-
Setting up international site subdirectories in GSC as separate properties for better geotargeting?
My client has an international website with a subdirectory structure for each country and language version - eg. /en-US. At present, there is a single property set up for the domain in Google Search Console but there are currently various geotargeting issues I’m trying to correct with hreflang tags. My question is, is it still recommended practise and helpful to add each international subdirectory to Google Search Console as an individual property to help with correct language and region tagging? I know there used to be properly sets for this but haven’t found any up to date guidance on whether setting up all the different versions as their own properties might help with targeting. Many thanks in advance!
International SEO | | MMcCalden0 -
Duplicate store (subdomain) not ranking
I have a store ( www.grocare.com ) and I made a duplicate store recently ( in.grocare.com ) for a different region. Both have different currencies and target different regions. I even targeted the new store ( in.grocare.com ) to that particular country in google search console. They both have different href lang tags to mark different regions too. Now its been a month since this has been done. But the new store is not ranking in the region. The old one is still ranking and I have to redirect the traffic from old to new based on IP.
International SEO | | grocare
I thought making a new store and targeting specifically would help with rankings. Am i doing something wrong here?0 -
International SEO & Duplicate Content: ccTLD, hreflang, and relcanonical tags
Hi Everyone, I have a client that has two sites (example.com & example.co.uk) each have the same English content, but no hreflang or rel="canonical" tags in place. Would this be interpreted as duplicate content? They haven't changed the copy to speak to specific regions, but have tried targeting the UK with a ccTLD. I've taken a look at some other comparable question on MOZ like this post - > https://moz.com/community/q/international-hreflang-will-this-handle-duplicate-content where one of the answers says **"If no translation is happening within a geo-targeted site, HREFLANG is not necessary." **If hreflang tags are not necessary, then would I need rel="canonical" to avoid duplicate content? Thanks for taking the time to help a fellow SEO out.
International SEO | | ccox10 -
Near-Duplicate Content
Hi, On my website, we are showcasing many products in both English and Spanish. We originally create each a product description in English, then we translate to Spanish. But sometimes, due to having numerous products, we don't translate to Spanish, and we just pull the English description on the Spanish page (so it has menus etc in Spanish, but the long Product Description in in English). English Example: http://www.viatrading.com/product.jhtm?id=34608
International SEO | | viatrading1
Spanish Example: http://www.viatrading.com/wholesale/product/TIGR-LN-APP/Ropa,-Relojes,-Gafas-y-Accesorios.html?cid=4 Could that be considered duplicated (or near-duplicated) content? For SEO, would it be better if the Spanish product page was redirected to the English one if not translated? Thank you,0 -
Different urls for the homepage on an international website
Hi! I was wondering what would be the best strategy to solve duplicated content generated by the homepage and its differents URLS This is an international website. Now it only has one language working: Spanish, but the url structure is already ready to work with the language approach So we have now www.brand.com -> Spanish Homepage (canonical www.brand.com/es)
International SEO | | teconsite
www.brand.com/es -> Spanish Homepage (canonical www.brand.com/es)
www.brand.com/index.php -> Spanish Homepage (canonical www.brand.com/es) I would like to know if this is the correct approach of if we should add 301 redirects instead of canonical. Let's image that they want to active the /en language, so they will have www.brand.com
www.brand.com/index.php
www.brand.com/es
www.brand.com/en now what? I image they have to use hreflang, but I am a little lost with how this should work. 301? canonical? hreflang? Could you help me? Thank you! Victoria0 -
"Hreflang=x" tag and multinational websites
Hello, We have multiple websites targeted at multiple countries and languages, each with the correct country extension. We have a corporate blog for each of these websites, where the blogs are subdomains of the main website. Currently we have a process of rewriting our blog posts completely – while keeping the same subjects – in order to have original content on each of our blogs, although we have up to 3 blogs in the same language. These are the languages we target: French – FRANCE French – SWITZERLAND French – BELGIUM Italian – ITALY Italian – SWITZERLAND German – GERMANY German – SWITZERLAND German – AUSTRIA Spanish – SPAIN Spanish – COLOMBIA Spanish – PANAMA Czech – CZECH REPUBLIC Swedish – SWEDEN Dutch – BELGIUM / NETHERLANDS English – UK English – INTERNATIONAL The process is obviously very tedious, and not always applied rigorously – i.e. some of the texts are posted on 2-3 different blogs, creating duplicate content.
International SEO | | ESL_Education
The questions : Would there be any reason for us to privilege the use the rel="canonical" tag over the "hreflang=x" tag, thus giving privilege to a "master" version for each language? Are there any risks in using the "hreflang="x" tag for our blogs considering that the posts would be very similar, except for references to additional content? Could there be any risk that Google would consider our sites as duplicate content after all? Should we specify on each blog that we have all the above versions, or should we only specify the other markets versions in each language? For example, should we specify on our French, Swiss and Belgium blog that we have 3 different French versions, on our UK blog that we also have an international version, and so on, or should we list all versions on each of the blogs? Does the "hreflang="x" tag facilitate the indexation of each of the versions in the SERPs of their targeted market? Lastly, are there any precautions we should take in order to put this in place? Looking forward to your feedback. Best wishes, Maëlle0 -
International SEO
Anyone have any good free resources for international SEO best practices? I've read through most of the common stuff and wondered if there's anything I'm missing. We are getting ready to launch a version of our website in the UK and I could use any hints or advice that could make my life easier. My biggest question is whether to keep the sites as 1 site (single domain with sub-folder for sharing incoming link profile) or to get a .UK domain and do everything from scratch. (it seems like a sub-domain is not the way to go?). I also wonder if any of you can share things to look out for, pitfalls, mistakes, etc...? TIA for any help/answers!
International SEO | | DownPour0 -
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