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
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
-
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 -
How can I restrict the domains country by country?
Hello, I have Two Domains one is xyz.co.uk and other is xyz.com Now, my main target for .com is United States, and I don't want to open that .com domain in any other country especially India. The same with the .co.uk, I dont want to open .co.uk in other countries. I did it with some developer help but it gave me redirected error in Google Webmaster. Can anyone please guide me how I can do this the proper way ? And Other issues is, how can I implement ,if any user in United States open xyz.co.uk than he should redirect to the .com version. Thank you.
International SEO | | AmitTulsiyani0 -
Country subfolders showing as sitelinks in Google, country targeting for home page no longer working
Hi There, Just wondering if you can help. Our site has 3 region versions (General .com, /ie/ for Ireland and /gb/ for UK), each submitted to Google Webmaster Tools as seperate sites with hreflang tags in the head section of all pages. Google was showing the correct results for a few weeks, but I resubmitted the home pages with slight text changes last week and something strange happened, though it may have been coincidental timing. When we search for the brand name in google.ie or google.co.uk, the .com now shows as the main site, where the sitelinks still show the correct country versions. However, the country subdirectories are now appearing as sitelinks, which is likely causing the problem. I have demoted these on GWT, but unsure as to whether that will work and it seems to take a while for sitelink demotion to work. Has anyone had anything similar happen? I thought perhaps it was a markup issue breaking the head section so that Google can no longer see the hreflangs pointing to each other as alternates. I checked the source code in w3 validator and it doesn't show any errors. Anyway, any help would be much appreciated - and thanks to anyone who gets back, it's a tricky type of issue to troubleshoot. Thanks, Ro
International SEO | | romh0 -
Can multiple hreflang tags point to one URL? International SEO question
Moz, Hi Moz, Can multiple hreflang tags point to a single URL? For example, if I have a Canadian site (www.example.com/ca) that targets French and English speakers can I have the following: or would I use: Any insight would be very helpful and greatly appreciated! Thank you in advance!
International SEO | | DA20131 -
Blocking domestic Google's in Robots.txt
Hey, I want to block Google.co.uk from crawling a site but want Google.de to crawl it. I know how to configure the Robots.txt to block Google and other engines - is there a fix to block certain domestic crawlers? any ideas? Thanks B
International SEO | | Bush_JSM0 -
URL Structure - Homepage, Country and State Pages
Hello, I am creating a website (or websites if best format) that will have state-specific boating license courses for every state in the US, Canada and Australia. I would like the content to be available on the website in English, French and Spanish. I want to be the global leader in providing boat test courses. For the (1) homepage, (2) country pages, and (3) state pages, what is best SEO format I should use for:
International SEO | | Monologix
(a) URL structure
(b) "href lang" code
(c) rel canonical code
(d) will meta content with non-English pages need to also be in the non-English language of that page? Also, what server company do you recommend I host my website with? I am a non-programmer and learning SEO, so any and all help will be greatly appreciated! Thank you very much in advance!!!0 -
.com versus local domains
Hi all, One of my clients has local domain websites in various parts of the world (co.uk etc. etc.) and there has always been a discussion about where a move from local domain (the current set-up) to a targeted .com domain (i.e. .com/uk) would benefit from a SEO perspective. The main reasoning (seo-wise) that keeps coming up is that there'd only be one domain to link to which would help with link juice being passed around. Any thoughts as whether this would actually be the case or if this possible benefit would be outweighed by other cons? Recent moves (local to .com) from a few websites (the Guardian newspaper in the UK being the most recent one off the top of my head) has made me start thinking about it again! Diana
International SEO | | Diana.varbanescu0 -
Upper case or/and lower case in rel="alternate" hreflang
Hi Mozzers, I have a question about the rel="alternate" hreflang tag, with an example. When I use two subfolders for two different countries/languages, for instance www.domain.com/nl-nl/ and www.domain.com/nl-en/ (for the English version) and I want to use the rel="alternate" hreflang tag, do I need to follow the ISO standards concerning Uppercase country code and Lowercase language code (en-NL)? Or is it okay to use the Lowercase country and language code (en-nl), since we also use this in the URL of the Subfolder. What does Google prefer? Thanks in advance.
International SEO | | MartijnHoving820