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
-
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 -
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 -
What's the difference between 'en-gb' and 'en-uk; when choosing Search engines in campaign set up?
Hi What's the difference search engine wise and which one should I choose, i presume GB since covers entire British landmass whereas UK excludes Ireland according to political definition, is it the same according to Google (& other engines) ? All Best Dan
International SEO | | Dan-Lawrence0 -
Where is it appropriate to use a .eu domain?
My client, a UK company, has a .eu domain and want to rank primarily in the UK but also worldwide, is a .eu domain appropriate?
International SEO | | peeveezee0 -
Does Google's algorithm work the same in every country?
I can't help but feel this is a silly question! but does Google algorithm work exactly the same throughout all countries? I run a few sites in the UK and a couple in Spain but can't help but feel that my Spanish sites are harder to rank for. The sites that rank the best are business directories in Spain... whereas here in the UK you'd be lucky to find one on page one..
International SEO | | david.smith.segarra0 -
Thai Characters in URL's
Does anyone have experience with non-Latin characters in URL's? We've launched a website in Thailand and picked Thai characters for URL's. However, when you copy it, it turns into something like this: http://www.imoneythailand.com/บัตรเครดิต Can it impact our website's crawlability? Also, is keyword in URL a ranking factor for non-Latin languages? Thanks in advance for help!
International SEO | | imoney0 -
Sub-domains or sub-directories for country-specific versions of the site?
What approach do you think would be better from an SEO perspective when creating country-targeted versions for an eCommerce site (all in the same language with slight regional changes) - sub-domains or sub-directories? Is any of the approaches more cost effective, web development-wise? I know this topic's been under much debate and I would really like to hear your opinion. Many thanks!
International SEO | | ramarketing0 -
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