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
-
Correct Hreflang & Canonical Tags for Multi-Regional Website English Language Only having URL Parameters
Dear friends, We have a multi-regional website in English language only having the country selector on the top of each page and it adds countrycode parameters on each url. Website is built in Magento 1.8 and having 1 store with multiple store views. There is no default store set in Magento as I discussed with developer. Content is same for all the countries and only currency is changed. In navigation there are urls without url parameters but when we change store from any page it add parameters in the url for same page hence there are total 7 URLs. 6 URLs for each page (with country parameters) and 1 master url (without parameters) and making content duplicity. We have implemented hreflang tags on each page with url parameters but for canonical we have implemented master page url as per navigation without url parameters Example on this page. I think this is correct for master page but we should use URL parameters in canonical tags for each counry url too and there should be only 1 canonical tag on each country page url. Currently all the country urls are having master page canoncial tag as per the example. Please correct me if I am wrong and **in this case what has to be done for master page? **as google is indexing the pages without parameters too. We are also using GEOIP redirection for each store with country IP detection and for rest of the countries which are not listed on the website we are redirecting to USA store. Earlier it was 301 but we changed it to 302. Hreflang tags are showing errors in SEMRush due to redirection but in GWT it's OK for some pages it's showing no return tags only. Should I use **x-default tags for hreflang and country selector only on home page like this or should I remove the redirection? **However some of the website like this using redirection but header check tool doesn't show the redirection for this and for our website it shows 302 redirection. Sorry for the long post but looking for your support, please.
International SEO | | spjain810 -
How to Localise per Region (Europe, America, APAC, EMEI) and not per country as best SEO practise?
Hi SEO expertises! I am currently working with a client that initially have an English website targeting UK users but want to expand their market into four new regions (Europe, America, APAC and EMEI) keeping English as a main language. I would like to request your help here as I told the client ISO location and hreflang it will be just possible per language and they must need to localise each English region with local keywords, however I would like to double check if it will be any way (Sitemap, Hreflang) we can tell Google we are targeting per region and not per country? Thanks a lot!
International SEO | | Atalig20 -
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 -
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 -
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 -
Redirect the main site to keyword-rich subfolder / specific page for SEO
Hi, I have two questions. Question 1: is it worthwhile to redirect the main site to keyword-rich subfolder / specific page for SEO? For example, my company's webpage is www.example.com. Would it make sense to redirect (301) the main site to address www.example.com/service-one-in-certain-city ? I am asking this as I have learned that it is important for SEO to have keywords in the URL, and I was thinking that we could do this and include the most important keywords to the subfolder / specific URL. What are the pros and cons of this? Should I create folders or pages just the sake of keywords? Question 2: Most companies have their main URL shown as www.example.com when you access their domain. However, some multi-language sites show e.g. www.example.com/en or www.example.com/en/main when you type the domain to your web browser to access the site. I understand that this is a common practice to use subdomains or folders to separate different language versions. My question is regarding subfolders. Is it better to have only the subfolder shown (www.example.com/en) or should I also include the specific page's URL after the subfolder with keywords (www.example.com/en/main or www.example.com/en/service-one-in-certain-city)? I don't really understand why some companies show only the subfolder of a specific language page and some the page's URL after the subfolder. Thanks in advance, Sam
International SEO | | Awaraman1 -
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 -
Country specific domains pointing to a .com site
Hello, I am new to seo so please be easy if this happens to be a "silly" question. My company has a .com site. We are expanding into global markets, focusing on specific countries right now. General question: Would I be penalized for duplicate content if I purchased country-specific domains and pointed them to the .com site? Thanks, Jim
International SEO | | jimmer0