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 SEO & redirects - do these solutions make sense?
I’m currently working on SEO for an international website with subdirectories set up for each international version. The site is has never had any SEO previously and is having a lot of indexing and visibility issues. Also geotargeting seems very off in search results. I’ve diagnosed various issues and want to check my assumptions and solutions below make sense... The root domain uses a 302 redirect to display content from the /en-GB page. (302 redirects seem to be a default language fallback setting configured in the CMS) and they’re used for most key pages. I’m concerned these redirects are contributing to a lot of the issues with incorrect indexing. The en-GB is the default language version of the site. So far, the en-GB has been set as the canonical version too. Both the root domain and this subdirectory URL display the same content. (en-US is also a near duplicate page). All other international homepages appear only on their subfolder URL. Various SEO tools have been showing redirect loops (caused by language changing parameter versions of URLs being crawled that don’t have redirects on them) and issues with hreflang and canonicals. I believe the hreflang tags and canonicals have been ignored due to relative URLs being used for each, as search results don’t always contain the desired versions of the URLs (in terms of regional version and preferred canonical versions). My questions are: Could these 302 redirects be conflicting with hreflang tags? If so, I’m thinking they should be removed (if not made 301s). GSC doesn’t like the fact these are on key pages, as redirected pages are listed in the sitemap. Will changing hreflang tags and canonical tags to absolute URLs possibly be enough to fix these issues from what you can tell? (Or will redirects need to go too?) Is the en-GB correctly set as the canonical when the root domain is also accessible, indexed and using this page’s content within the CMS too? (I feel like the root domain should be the canonical version, but not sure that works together with other language version subfolders or with a redirect in place from root to subfolder). As an extra point to the last question, GSC has recently chosen the root domain as the canonical (despite en-GB being set as user preference) and is now choosing to deindex some international versions of the homepage as a result. Hoping that getting the hreflang tags fixed and possibly redirects removed should correct this ASAP. But perhaps this also confirms en-GB should be the canonical and marked X-default too. I hope that all makes sense and sorry it’s a small collection of related questions. Really appreciate any replies.
International SEO | | MMcCalden0 -
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 -
Hreflang tag on every page?
Hello Moz Community, I'm working with a client who has translated their top 50 landing pages into Spanish. It's a large website and we don't have the resources to properly translate all pages at once, so we started with the top 50. We've already translated the content, title tags, URLs, etc. and the content will live in it's own /es-us/ directory. The client's website is set up in a way that all content follows a URL structure such as: https://www.example.com/en-us/. For Page A, it will live in English at: https://www.example.com/en-us/page-a For Page A, it will live in Spanish at https://www.example.com/es-us/page-a ("page-a" may vary since that part of the URL is translated) From my research in the Moz forums and Webmaster Support Console, I've written the following hreflang tags: /> For Page B, it will follow the same structure as Page A, and I wrote the corresponding hreflang tags the same way. My question is, do both of these tags need to be on both the Spanish and English version of the page? Or, would I put the "en-us" hreflang tag on the Spanish page and the "es-us" hreflang tag on the English page? I'm thinking that both hreflang tags should be on both the Spanish and English pages, but would love some clarification/confirmation from someone that has implemented this successfully before.
International SEO | | DigitalThirdCoast0 -
How to handle different content on same domain internationally?
Dear community, I have encountered a unique situation and I am unsure as how to proceed, I have a U.S. based website for intentions of this question is www.musicstore.com. The customer has decided to offer their products up for sale internationally, however, has two business requirements, one is that his international presence differs with product offering and content then the domestic version and two, that they both live on the same domain of www.musicstore.com without any reference to offering a differing international presence. Many of his products are offered for purchase directly overseas, while not against his suppliers rules, it is frowned upon. All this said, now to my question. I'm currently running a Magento two website install. With GeoIP setting which version of www.musicstore.com is presented. Do I have to worry about different content being displayed on the same exact url even though the experience is completely location based? If it is a concern, any risks I should be concerned with. I could possibly do something along the lines of www.musicstore.com/in/ while this is not ideal for the customer, if it prevents many larger issues I'd steer the customer this way. I just want my customer to be able to sell his product internationally without upsetting his suppliers or making Google go, what does this site actually have. Hopefully I explained my question well enough for those who can help to understand. Please ask if you need any more information. Any help would be greatly appreciated, thank you.
International SEO | | swarming0 -
Multilanguage duplicate content question
I have following situation; First site, in four languages
International SEO | | nans
Second site, in one language Let's say we have the following setup: www.domain1.be/nl (dutch)
www.domain1.be/fr (french)
www.domain1.be/en (english)
www.domain1.be/de (german) www.domain2.be/ (french only) Possible problem is the content on
www.domain1.be/fr
www.domain2.be
Content on domain2 is a copy of domain1/fr. So French content is duplicated. For domain1, the majority (80%) are Dutch speaking clients, domain2 is 100% French.
Both companies operate in same country, one in the north, the second one in the south. QUESTION; what about duplicate content?
Can we 'fix' that with using the canonical tag? Canonical on domain1 (fr pages), pointin to domain2? Or vice versa.
Domain1 is more important than domain2, but customers of domain2 should not be pointed to domain1. Anybody any advice?0 -
International SEO
Hi If you were developing a US version of an existing UK site then is this the correct format/instructions for on-page SEO. Ive taken quite a lot from Aleydas great post: http://moz.com/blog/the-international-seo-checklist but just want to confirm below is a good overall checklist to provide to clients developers ? Create US & UK country & language subfolders such as: domain.com/en-us/ and domain.com/en-gb/ Add 'rel=alternatehreflang' attribute according to google guidelines Add individual site map to each subfolder or will the hreflang attribute do or vice versa or both best? Don't redirect users via IP sniffing their location and serving up country/language version. Instead obviously link between language/country versions with a crawlable and very visible menu. Use the meta content language/country by adding the 'country-language' meta-tag in your html head Create individual profiles in GWT & GA for each country/language version and geotarget accordingly Localise content: spelling, currency, contacts etc Anything else re on-page/technical im missing ? Many Thanks
International SEO | | Dan-Lawrence
Dan [edited to fix formatting]0 -
Anchor text for international SEO
HI I am looking to rank sites in multiple foreign search engines. I am thinking about the anchor text strategies I need to employ. My key phrase: golfschläger (golf club) I am targeting a German page (written in German). Would Google understand that if I use the anchor text “golf club” to my German “golfschläger” page, it is infact the same word and therefore give anchor text benefits to that page, or for anchor text benefits to pass does the anchor text have to be in the same language? thanks for any help!!!!
International SEO | | Turkey0 -
Ranking local content against English content
Hi SEOMoz, If I have a site that has multiple language selection, how would it be possible for my site with localized content to rank higher than the default/English content? For example, in Google.co.th, my site with English content (http://www.xyz.com/en-us/) ranks higher than the localized content (http://www.xyz.com/th-th/). How is it possible for me to turn things around and ensure that for local markets like Indonesia, Thailand, Vietnam, China etc the localized content organically ranks higher than the default-English page? Thanks! Steve
International SEO | | sjcbayona-412180