Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
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.
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 setup issues canonical URL
My site is www.grocare.com for one region and in.grocare.com for another region. Both of them have the same content except the currency for particular regions. Someone told me that google will take the content as duplicate and not rank either. I have setup hreflang and targeted different regions for both in the search console. I read many article which say canonical urls need to be setup for international seo sites. But Im not sure how to setup canonical urls and whether they are the right way to go . i just don't want my content deranked. Now i have setup hreflang properly after asking the moz community itself. So im hoping to get some help with this query too. TIA
International SEO | | grocare0 -
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 -
Worldwide and Europe hreflang implementation.
Hi Moz ! We're having quite a discussion here and I'd like to have some inputs. Let me explain the situation and what we plan to do so far. One of our client has two separate markets : World and Europe. Both pages versions will be mostly the same, except for the fact that they will have their own products. So basically, we'd want to show only the European EN version to Europe and the standard EN version to the rest of the world, same goes for FR and ES. As far as IT, DE, CS and SK, they will only be present within the european version. Since we cannot target all Europe with a single hreflang tag, we might have to do it for every single european countries. Regarding this subject, SMX Munich recently had quite an interesting session about this topic with a confirmation coming from John Mueller saying that we can target a single URL more than once with different hreflang tags. You can read more here : http://www.rebelytics.com/multiple-hreflang-tags-one-url/ So having all this in mind, here's the implementation we plan to do : www.example.com/en/ Self canonical www.example.com/fr/ - hreflang = fr www.example.com/es/ - hreflang = es www.example.eu/it/ - hreflang = it www.example.eu/de/ - hreflang = de www.example.eu/cs/ - hreflang = cs www.example.eu/sk/ - hreflang = sk www.example.eu/fr/ - hreflang = be-fr www.example.eu/fr/ - hreflang = ch-fr www.example.eu/fr/ - hreflang = cz-fr www.example.eu/fr/ - hreflang = de-fr www.example.eu/fr/ - hreflang = es-fr www.example.eu/fr/ - hreflang = fr-fr www.example.eu/fr/ - hreflang = uk-fr www.example.eu/fr/ - hreflang = gr-fr www.example.eu/fr/ - hreflang = hr-fr etc… . This will be done for all european countries (FR, EN and ES). www.example.com/en/ - x-default Let me know what you guys think. Thanks!
International SEO | | Netleaf.ca0 -
Hreflang Alternate & Pagination
Hi everybody, So I'm setting up hreflang tags on an ecommerce site. The sites are in the USA and Canada. The Canadian site will have fewer products than the American site, meaning that there won't be as many pages in each category as there are on the American site. What is the correct way to handle hreflang tags on these extra category pages? To put this another way, the American site may have a category with 3 pages of products, while the Canadian equivalent only has 2 pages of products. What happens to this extra American category page (example.com/widget-category/page-3) ? Does it get an hreflang tag linking to the first page of the equivalent Canadian category (example.ca/widget-category/)? Does it not get any hreflang tags because it has no true Canadian counterpart? Does it matter at all if it has a canonical tag pointing to the first page in the series anyway (example**.com**/widget-category/)? Thanks, Andrew B.
International SEO | | ABullis0 -
Is this setup of Hreflang xml sitemap correct?
Hi, I'm trying to setup hreflang for 2 domains. One is purely a US site and the other domain has the language-country as subdomains. For example: http://www.websiteUSA.com (Targets English - USA) https://www.websiteINT.com/en-CA (Targets English - Canada) https://www.websiteINT.com/fr-CA (Targets French - Canada) https://www.websiteINT/es (Targets Spanish) ..and so on and so forth for about 12 of these international URLs. I created an XML sitemap that looks something like this: <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>http://www.websiteUSA.com</loc></url></urlset> <url><loc>https://www.websiteINT.com/en-CA</loc></url> <url><loc>https://www.websiteINT.com/fr-CA</loc></url> Question 1: Is this correct? In my actual file, I have all the countries listed and self-referencing. Question 2: I'm hosting this file at https://www.websiteINT.com/hreflang.xml AND at http://www.websiteUSA.com/hreflang.xml. Is this correct? Question 3: Will this help the SERPs direct english speakers from the US to http://www.websiteUSA.com while show SERPs for say English Speakers in Canada to https://www.websiteINT.com/en-CA? Question 4: For some reason, when I put up the xml site, it only listed each URL once instead of the full XML file. Should I have uploaded a text file instead? It doesn't seem to render correctly. Thank you!
International SEO | | SylviaH0 -
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 -
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 -
International (foreign language) URL's best practices
I'm curious if there is a benefit or best practice with regards to using the localized language on international sites (with specific ccTLDs). For example, should my french site (site.fr) use the french language as keywords within the URLs or should they be in english? e.g. www.site.fr/nourriture vs. www.site.fr/food Is that considered best practice for SEO (or just for brand perception those markets?). Is there a tangible loss in SEO if we do not use the correct language for those URLs and just stick with English around the world? I recall seeing a Matt Cutts video on the topic and he said that google does support i18n URL's but other SE's might not support them as gracefully but he didn't come down with a hard recommendation to go with i18n URL's or just English. Would love a strong ruling in favor one direction based on best practices.
International SEO | | mongillo0