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.
How to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries?
-
Dear all,
what is the best way to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries?
What must I add to my code of websites my .nl domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl?
What must I add to my code of websites my .be domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl?
Thanks in advance!
-
In that case, I'll go for the Alternate link tag as mentionned before:
By using it, you will guide Google and tell him to show the flemish version in first position for your user in Belgium and vice-versa for the dutch users in Holland.
Hope this helps!
Maxime
-
Dear Maxime,
there texts and content are pretty much the same / identical. Maybe there are some slight textual differences since Flemish and Dutch are different sometimes.
Overall, all content is nearly the same.
Thanks for both of your help!
-
BenVer,
Please can you tell us what kind of duplicate content do you have on your different domains (.nl /.be) ?
Are the dutch and belgium page exactly the same? What are the differences?
Thanks,
Maxime
-
Maxime,
I saw this too, and there are certainly variants. Given, that for Google I have generally used WMT as the final source and usually that worked, I lean a bit more that way. But, your point is well stated and not wrong. For purposes of being absolutely safe, it will not hurt to have the hreflang attribute there. A better question might be: is it really necessary given the you have ccTLD's and the same language?
From WMT:
Some example scenarios where
rel="alternate" hreflang="x"is recommended:- You translate only the template of your page, such as the navigation and footer, and keep the main content in a single language. This is common on pages that feature user-generated content, like a forum post.
- Your pages have broadly similar content within a single language, but the content has small regional variations. For example, you might have English-language content targeted at readers in the US, GB, and Ireland.
- Your site content is fully translated. For example, you have both German and English versions of each page.
I will assume that it is a given that google uses the ccTLD as the indicator of country and that it is considered a "Strong" signal to Google.
WIthin GWMT re: multilingual/regional sites (the bolded/italics are mine

Websites that provide content for different regions and in different languages sometimes create content that is the same or similar but available on different URLs. This is generally not a problem as long as the content is for different users in different countries. While we strongly recommend that you provide unique content for each different group of users, we understand that this may not always be possible. There is generally no need to "hide" the duplicates by disallowing crawling in a robots.txt file or by using a "noindex" robots meta tag. However, if you're providing the same content to the same users on different URLs (for instance, if both __
example.de/andexample.com/de/show German language content for users in Germany), you should pick a preferred version and redirect (or use the rel=canonical link element) appropriately. In addition, you should follow the guidelines on rel-alternate-hreflang to make sure that the correct language or regional URL is served to searchers.Again, thanks for the replies. I find it really helpful to discuss back and forth as it adds to the learning adventure we are all on.
Best to you,
Robert
-
Maxime,
While I agree the speed might be different with in country hosting given they are both European countries. (Not true in some others.) But the question was around content duplication.
Again, I think your intent is good. But, since he has two separate domains. ExampleSite.be and ExampleSite.nl, he has no need of hreflang="x" since both are in Dutch. If he had Dutch and English it would not matter if it were the same domain or not:
From Gianluca Fiorelli mozPost**if Page A (US version) exists also in Page B (Spanish), C (French), and D (German) versions from other countires, no matter if they are in the same domain or different, then on page A you should suggest the last three URLs as the ones Google must show in the SERPs in their respective targeted Googles. **
Again, since they are ccTLD's and they are already geotargeted by virtue of same and since they are both in Dutch, there is no other worry re duplicate content.
I am open to being shown I am wrong as it will not be the first time

Best to you, thanks so much for your replies,
Robert
-
Hi Robert, 1. Yes indeed you are right, for a ccTLD, there is no geotargeting in GWMT. 2. Dutch is spoken in both Netherlands and Belgium so having the same content appearing on both .nl and .be domains is likely to be considered as duplicate content. Using rel=”alternate” hreflang=”x” seems to be the most appropriate solution. 3. In my opinion, hosting each website in the country targeted is a plus (server response will be quicker) but this is indeed not decisive. So do it only if you have a large budget.
-
Maxime,
I have to question this as you have it. The intent is there, but you are throwing everything at a problem and some of it does not work:
1. for a ccTLD, there is no geotargeting in WMT: from GWMT:
Sites with country-coded top-level domains (such as .ie) are already associated with a geographic region, in this case Ireland. In this case, you won't be able to specify a geographic location.
2. He does not need this in a cross domain setting.
3. Given he has ccTLD's this is an unnecessary expense and will add no value.
Hope this clarifies for you,
-
BenVer
In a short answer, not much. This is from GWMT:
Websites that provide content for different regions and in different languages sometimes create content that is the same or similar but available on different URLs. This is generally not a problem as long as the content is for different users in different countries.
Since you are using ccTLD's, Google already knows that you are targeting that specific country.
While this will not guarantee that the .nl doesn't outrank the .be in Belgium, it will take care of your duplicate content concerns.
-
Is this the best way?
http://googleproducts-nl.blogspot.nl/2012/02/meertalige-en-multiregionale-websites.html
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
-
"Duplicate without user-selected canonical” - impact to SERPs
Hello, we are facing some issues on our project and we would like to get some advice. Scenario
International SEO | | Alex_Pisa
We run several websites (www.brandName.com, www.brandName.be, www.brandName.ch, etc..) all in French language . All sites have nearly the same content & structure, only minor text (some headings and phone numbers due to different countries are different). There are many good quality pages, but again they are the same over all domains. Goal
We want local domains (be, ch, fr, etc.) to appear in SERPs and also comply with Google policy of local language variants and/or canonical links. Current solution
Currently we don’t use canonicals, instead we use rel="alternate" hreflang="x-default": <link rel="alternate" hreflang="fr-BE" href="https://www.brandName.be/" /> <link rel="alternate" hreflang="fr-CA" href="https://www.brandName.ca/" /> <link rel="alternate" hreflang="fr-CH" href="https://www.brandName.ch/" /> <link rel="alternate" hreflang="fr-FR" href="https://www.brandName.fr/" /> <link rel="alternate" hreflang="fr-LU" href="https://www.brandName.lu/" /> <link rel="alternate" hreflang="x-default" href="https://www.brandName.com/" /> Issue
After Googlebot crawled the websites we see lot of “Duplicate without user-selected canonical” in Coverage/Excluded report (Google Search Console) for most domains. When we inspect some of those URLs we can see Google has decided that canonical URL points to (example): User-declared canonical: None
Google-selected canonical: …same page, but on a different domain Strange is that even those URLs are on Google and can be found in SERPs. Obviously Google doesn’t know what to make of it. We noticed many websites in the same scenario use a self-referencing approach which is not really “kosher” - we are afraid if we use the same approach we can get penalized by Google. Question: What do you suggest to fix the “Duplicate without user-selected canonical” in our scenario? Any suggestions/ideas appreciated, thanks. Regards.0 -
Duplicate Content Regarding Translated Pages
If we have one page in English, and another that is translated into Spanish, does google consider that duplicate content? I don't know if having something in a different language makes it different or if it will get flagged. Thanks, Ruben
International SEO | | KempRugeLawGroup1 -
Redirect to 'default' or English (/en) version of site?
Hi Moz Community! I'm trying to work through a thorny internationalization issue with the 'default' and English versions of our site. We have an international set-up of: www.domain.com (in english) www.domain.com/en www.domain.com/en-gb www.domain.com/fr-fr www.domain.com/de-de and so on... All the canonicals and HREFLANGs are set up, except the English language version is giving me pause. If you visit www.domain.com, all of the internal links on that page (due to the current way our cms works) point to www.domain.com/en/ versions of the pages. Content is identical between the two versions. The canonical on, say, www.domain.com/en/products points to www.domain.com/products. Feels like we're pulling in two different directions with our internationalization signals. Links go one way, canonical goes another. Three options I can see: Remove the /en/ version of the site. 301 all the /en versions of pages to /. Update the hreflangs to point the EN language users to the / version. **Redirect the / version of the site to /en. **The reverse of the above. **Keep both the /en and the / versions, update the links on / version. **Make it so that visitors to the / version of the site follow links that don't take them to the /en site. It feels like the /en version of the site is redundant and potentially sending confusing signals to search engines (it's currently a bit of a toss-up as to which version of a page ranks). I'm leaning toward removing the /en version and redirecting to the / version. It would be a big step as currently - due to the internal linking - about 40% of our traffic goes through the /en path. Anything to be aware of? Any recommendations or advice would be much appreciated.
International SEO | | MaxSydenham0 -
Multi Regional Website Best Practices
Hi there, I have a website that is targeting 3 countries AU/US & NZ. I have set up hreflang tags for each page on each of the site however I am having difficulties getting it work right. I read this article which was a great insight into the hreflang tags. https://azwa.1clkaccess.in/blog/hreflang-behaviour-insights and as a result I have implemented hreflang tags in the following manner: When users access the root domain http://[website] it will redirect the user to their locale with a 302 redirect. I have a few questions:
International SEO | | nathanfranklin
1. When building my external link profiles, I'm not sure if I should be building link profiles for http://[website]/ or for the geo graphical pages (http://[website]/aus/ etc..). Note that the http://[website]/ is never used, it just issues a 302 to the actual geographical location. 2. It seems that the hreflang tags are not working correctly. Perhaps its the result of the 302 on the root page, but in google.com.au (using the link http://www.google.com.au/search?hl=en&gl=au&pws=0&q=[branded search]) I would expect that I should see the search results for /aus/ given the fact that the hreflang tags are setup as en-au. Instead I am seeing the root domain page. Is that correct or should it be showing all the pages with /aus/. ALSO If I do a search in google thailand (http://www.google.com.au/search?hl=en&gl=th&pws=0&q=[branded search]) it returns the /aus/ version where it should be showing the /us/ using the x-default hreflang tag. In google webmaster tools I have setup 4 site profiles:
http://[website]/
http://[website]/us/
http://[website]/aus/ (Targeted to Australia)
http://[website]/nz/ (Targeted to New Zealand) Any help would be appreciated. Thanks Nathan1 -
Multiple You-Tube Channels for Geo-Targeting ??
Hi I have a UK based e-commerce client/project who has authorised a US distributor/dealer to set up their own US site along with US focused Facebook & other socials etc etc Should they also have country specific YouTube channels (even if both target countries English language i.e. UK & US) ? They brand has lots of video content of 2 main types: Product reviews to host on the website (to win serps, snippets and hence conversions from search) Longer more entertaining productions to put on YouTube channel to captivate, entertain and eventually drive YT target traffic to website via 'in video annotations' external link feature etc. Hence it makes sense to me that the US agent should set up their own YT channel along with their other social pages like FB etc, since annotated links go to different sites (US & UK). Does Google allow this (multiple channels) If not and sticking with the one channel is it possible to geo-target in video annotated external links so depending upon viewer location serves up relevant country link ? Any other ideas, help/advice, comments from anyone who has experience in this type of scenario ? Many thanks Dan
International SEO | | Dan-Lawrence0 -
What are the best practices for translation of city/state names for international SEO? (ie. New York in English vs. Nueva York in Spanish)
I'm working on international SEO / translation of a global travel site. While we have a global keyword research and translation strategy in process for each market they serve, I've run into a unique question. Overall, we are translating (and localizing) content for each market but aren't sure what to do with location names. Each country/state has cities and locations that have their own dedicated pages. I see three options for these location names (when titling a page and writing content): keep them in English, translate the names in the market languages, or use a combination of the two. The challenge with altering the location names to the market languages is that they are truly not known by those names. Though there are some instances where it may make sense…for instance **New York **in Spanish would be "Nueva York" with **‘**Nueva' being the Spanish translation of ‘new’. There are other instances, where no translation exists. If you’ve had a similar experience I'd love to hear your approach/recommendation.
International SEO | | JonClark150 -
Best URL structure for Multinational/Multilingual websites
Hi I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.) As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product? To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format: hotelsite.com/en/hotel-name (for english) and hotelsite.com/se/hotel-name (for swedish content of that same product) and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc. Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name? Any thoughts on best practice would be greatly appreciated.
International SEO | | pikka0 -
Subdomain hosted in a different country - what are the implications?
Hello, We are looking at creating an eCommerce section to a website and we are just weighing up the options: Magento - host on hour own server - great but it can often be very slow when hosting a shared server. Shopify - hosted solution but hosting is in the US and we are in the UK and shop will be hosted on a subdomain as a result Build our own solution - time consuming and costly There are two issues that have arisen from this situation.... Is it worse for SEO to host your store in a different country or to host in your country but your store potentially run slower? I'm swaying to the side of the argument that says give your users a good and fast experience instead of worrying about where you host the store. Bearing in mind that the main website will be hosted in the UK anyway and it is just the subdomain that will be hosted in the US. Just wondered if anybody has had experience with this or if I'm missing something? All feedback greatly appreciated! Thanks, Elias
International SEO | | A_Q0