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.
Is it safe to redirect our .nl (netherlands) domain that we have just purchased to our .com domain?
-
Hi all!
We've recently developed a German version of our website with German translation and now we have just purchased a .nl domain, but with this one, we want all of the copy to remain in English. Is it ok to redirect our .nl domain to our current .com website or will this give us bad SEO points?
Thank you!
-
I would add a link from the home page to the rest of your content (the .com site) but make it clear that people will be taken to a new site.
Redirects not required.
-
Thank you so much for all of your responses.
I thought the redirect would be the easiest option for now but then we would want the contact page, and preferably the homepage, to have the Dutch telephone number, email address and map (of the Amsterdam office).
At the moment, translation for the .nl website is not an option, but this is something we are thinking about for phase 2. Our .de domain has been translated, and for now, we just want to get the .nl domain up and running!
Is there a way we would be able to have a dutch homepage, with the correct telephone numbers and map, but then redirect to the rest of the website on .com?
Building links to .de and .nl will be something to think about in the future but for now we just want the sites to be indexed and accessible to users from their respective countries.
Thank you!
-
The 301 shouldn't be a problem but as stated it might be odd if used on advertising and then people end up on a different domain. It will help you snap up domain name so no-one else can use it though.
If you don't want a duplicate nl site in Dutch, you could keep the nl domain to a single page with Dutch content and then suggest Dutch visitors visit your main .com site. Would be worth having a contact page with address in Holland too.
If you make the nl site a re-gig of your .com site, make the content as different (and appealing to Dutch visitors) as possible.
Although many Dutch can speak English, they can't all, especially older generations so bear in mind when thinking about just serving English content.
-
If you made the .nl site the same as the .com com site, you could also cross-domain rel=canonical each page over to the .com site, which would leave visitors on the .nl site but assign all value over to the .com. As Ash said though, putting unique content--either Dutch or English--might me your most effective option. It may be even more effective if you host it in the Netherlands, too.
-
Yes, doing a 301 redirect from your .nl to the .com site will be fine, but why are you doing that?
Are you going to advertise in Holland and show the .nl URL? If so, users might be unsettled if they end up at the .com site. If it is just 301'd and that's all you do, then hardly anyone other than a person guessing your URL will even use it. You might not even rank in Holland.
There are no bad SEO points for the .com site, but you could be losing the chance to rank on Google.nl. I don't think Google.nl will note the 301 and therefore show the .com as well as a well-SEO'd .nl site.
You could put English content on the .nl site, preferably a rewritten version of the .com site. The key is to get .nl links to the .nl domain (if not 301'd). Make it a Dutch site as much as you can - get listed in Dutch directories, get Dutch citations, etc.
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
-
We are redirecting http and non www versions of our website. Should all versions http (non www version and www version) and https (non www version) should just have 1 redirect to the https www version?
We are redirecting http and non www versions of our website. Should all versions http (non www version and www version) and https (non www version) should just have 1 redirect to the https www version? Thant way all forms of the website are pointing to one version?
Intermediate & Advanced SEO | | Caffeine_Marketing0 -
Legacy domains
Hi all, A couple of years ago we amalgamated five separate domains into one, and set up 301 redirects from all the pages on the old domains to their equivalent pages on the new site. We were a bit tardy in using the "change of address" tool in Search Console, but that was done nearly 8 months ago now as well. Two years after implementing all the redirects, the old domains still have significant authority (DAs of between 20-35) and some strong inbound links. I expected to see the DA of the legacy domains taper off during this period and (hopefully!) the DA of the new domain increase. The latter has happened, although not as much as I'd hoped, but the DA of the legacy domains is more or less as good as it ever was? Google is still indexing a handful of links from the legacy sites, strangely even when it is picking up the redirects correctly. So, for example, if you do a site:legacydomain1.com query, it will give a list of results which includes pages where it shows the title and snippet of the page on newdomain.com, but the link is to the page on legacydomain1.com. What has prompted me to finally try and resolve this is that the server which hosted the original 5 domains is now due to be decommissioned which obviously means the 301 redirects for the original pages will no longer be served. I can set up web forwarding for each of the legacy domains at the hosting level, but to maintain the page-by-page redirects I'd have to actually host the websites somewhere. I'd like to know the best way forward both in terms of the redirect issue, and also in terms of the indexing of the legacy domains? Many thanks, Dan
Intermediate & Advanced SEO | | clarkovitch0 -
Domain Redirect and SSL Cert
Hi, When redirecting an entire site to another domain, do you have to maintain the SSL certificate? The SSL expires 3 days before the planned redirect. Thanks in advance.
Intermediate & Advanced SEO | | sofla_seo0 -
What happens to a domain in SERPs when it's set to redirect to another?
We have just acquired a competing website and are wondering whether to leave it running as is for now, or set the domain to redirect to our own site. If we set up this redirect, what would happen to the old site in Google SERPs? Would the site drop off from results? If so, would we capture this new search traffic or is it a free for all and all sites compete for the search traffic as normal? Thanks in advance. Paul
Intermediate & Advanced SEO | | kevinliao0 -
303 redirect
Hi, 303 redirect is a good thing or not ? I have a homepage in 2 languages FR and EN > mywebsite.com/fr/ and mywebsite.com/en/. A 303 redirect is on mywebsite.com to mywebsite.com/fr/. Thanks D.
Intermediate & Advanced SEO | | android_lyon0 -
Primary Domain or Redirect?
We are starting a new travel guide for a resort town. I have bought an expired domain with decent related links and PR (which seems to have survived the transfer (4 months ago). Beofre we launch the new site I am trying to decide if we should use this expired domain as the primary URL for the new site or just do a permanent redirect and buy a new domain that better matches the theme of the site. I am obviously concerned with starting from scatch with a new domain. I am confident we can build some good rellevant links in a short time but this space is very competetive. Any input would be greatly appreciated.
Intermediate & Advanced SEO | | Locals0 -
Redirect old .net domain to new .com domain
I have a quick question that I think I know the answer to but I wanted to get some feedback to make sure or see if there's additional feedback. The long and short of it is that I'm working with a site that currently has a .net domain that they've been running for 6 years. They've recently bought a .com of the same name as well. So the question is: I think it's obviously preferable to keep the .net and just direct the .com to it. However, if they would prefer to have the .com domain, is 301'ing the .net to the .com going to lose a lot of the equity they've built up in the site over the past years? And are there any steps that would make such a move easier? Also, if you have any tips or insight just into a general transition of this nature it would be much appreciated. Thanks!
Intermediate & Advanced SEO | | BrandLabs0 -
Login redirect 302
Ok - anyone knows what to do with the temporary redirect to the login page? In our e-commerce system we have a checkout page, which requires user to be logged in - if they are not, we redirect them to the login page using simple php header("Locaiton: url"). This however has been found as a Warning as it's a temporary redirect. I can't really put there permanent redirect for obvious reasons so if someone could give me some clue on this situation that would be much appreciated.
Intermediate & Advanced SEO | | coremediadesign0