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.
Any way around buying hosting for an old domain to 301 redirect to a new domain?
-
Howdy.
I have just read this QA thread, so I think I have my answer. But I'm going to ask anyway!
Basically DomainA.com is being retired, and DomainB.com is going to be launched.
We're going to have to redirect numerous URLs from DomainA.com to DomainB.com. I think the way to go about this is to continue paying for hosting for DomainA.com, serving a .htaccess from that hosting account, and then hosting DomainB.com separately.
Anybody know of a way to avoid paying for hosting a .htaccess file on DomainA.com?
Thanks!
-
If I am understanding correctly you want people to access DomainA.com when they go to DomainB.com? If this is the case, you could set up DomainB.com as a Domain Forward to DomainA.com.
For instance a Client I have right now has www.drcharlescrane.com and www.drcharlescrane.net. Hosting is only set up for .com and we domain forward .net.
You can also have this set up as a domain forwarding with mask so if you wanted the user would actually see in the URL domainb.com but pulling domaina.com's content.
I hope this makes sense and if you need further clarification let me know. Also where is your domain registered. I use Godaddy primarily to the low costs for domains. Here is a how to domain forward provided by them and more information on the topic - http://help.godaddy.com/article/422
-
DNS, resolves a name to a ip number,
that ip number should route to your website. Inthe headers of the resquest is the domain name, your web site should be configured to accept either all requests on a ip number and port or filtered by host headers (domains names), add all teh host headers needed, then in htaccess 30 to the pirmary domain name.
-
Thank you Alan. Are you suggesting that via DNS records I have DomainA.com "live" in the same place as DomainB.com, and then host the .htaccess on DomainB.com's hosting space?
So somebody requests DomainA.com, the DNS points to the hosting for DomainB.com, and then the .htaccess for DomainB.com can process the original DomainA.com request?
-
Thanks, but does this help with 301s for inner pages?
-
I had just the same experience. It was only one occasion but I did nothing more to the site then putting it under a new account on my shared hosting, so only the last digit of the ip has changed. I saw a drop in rankings however the original I gained back the original rankings a few weeks later.
-
I cant say it does, but when I changed ips i had a drop in rankings. But i cant prove it was the change in ip
but there is some logic to it,
A domain name is resolved to a ip address to find the website, the domain name is sent in the header. Your web site accepts a connection on a socket, ip number and port 123.123.123.123:80, it then looks in the header for the domain name
so a SE will see a difference, it will know this is not the same address -
100% disagree.
Most of the biggest websites in the world use DNS load balancing which will change the IP address of the server every request.
301 redirects lose a small amount of juice but IP changes don't.
Hosting changes don't (assuming no errors or outages).
Who-is changes do, but that is not relevant here.
-
1. you need to make a change to your DNS settings.
where every you registered your domain, you ned to change your Arecord to point at the correct ip number
2. you need to do a 301 redirect to primary domain.
-
If you have Cpanel here are the instructions. For godaddy or plesk call your host and tell them what you are trying to do.
Log into where you purchased domain A and forward it to the name servers at B's hosting. Then go into B Cpanel and click on add on domains. Add your domain. Once the domain has been added go to domain redirects and redirect your old domain to new.
For type choose permanent 301
Choose the domain you want to redirect from the drop down. Next manually type in your new domain name where it says "redirects to".
-
I think I disagree as moving site A's hosting to a new ip causes a drop in rankings.
Never heard about this before. I think this is not true, i have chagned IP's in the past without any consequences.
-
You shouldn't have to continue to pay for hosting for the site you are getting rid of, just keep renewing the domain name and then 301 it to the new site and you should be fine.
-
Thank you. I'm actually not understanding. How do I Park A on B. What is "explicit .htaccess"?
-
There is no penalty or loss for changing an IP address. There are many legitimat reasons for doing that. IP changes often occr when your host moves your site to a different server, or, when you upgrade your hosting package, or move to a different hosting service. No worries at all about new IPs.
-
The .htaccess that have the information about the A domain is inside B hosting, so, you don't need anymore A hosting when you do all the redirections.
I think this post can help:
http://searchenginewatch.com/article/2067216/The-10-Step-Site-Migration-Process
bye
-
Egol has usually got great answers that woths linstening to, this time however I think I disagree as moving site A's hosting to a new ip causes a drop in rankings. Put the redirection on top of that and you get some more fallback. I think in the above case I would not change the hosting but do the redirect and wait for google to notice the change. Maybe a few months later I would give up site A's original hosting and migrate it to site B's hosting to be able to keep the original urls live for some more time.
-
Park A on B and redirect with explicit .htaccess.
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
-
I have a question about the impact of a root domain redirect on site-wide redirects and slugs.
I have a question about the impact (if any) of site-wide redirects for DNS/hosting change purposes. I am preparing to redirect the domain for a site I manage from https://siteImanage.com to https://www.siteImanage.com. Traffic to the site currently redirects in reverse, from https://www.siteImanage.com to https://siteImanage.com. Based on my research, I understand that making this change should not affect the site’s excellent SEO as long as my canonical tags are updated and a 301 redirect is in place. But I wanted to make sure there wasn’t a potential consequence of this switch I’m not considering. Because this redirect lives at the root of all the site’s slugs and existing redirects, will it technically produce a redirect chain or a redirect loop? If it does, is that problematic? Thanks for your input!
Technical SEO | | mollykathariner_ms0 -
301 redirect syntax for htaccess
I'm working on some htaccess redirects for a few stray pages and have come across a few different varieties of 301s that are confusing me a bit....Most sources suggest: Redirect 301 /pageA.html http://www.site.com/pageB.html or using some combination of: RewriteRule + RewriteCond + RegEx I've also found examples of: RedirectPermanent /pageA.html http://www.site.com/pageB.html I'm confused because our current htaccess file has quite a few (working) redirects that look like this: Redirect permanent /pageA.html http://www.site.com/pageB.html This syntax seems to work, but I'm yet to find another Redirect permanent in the wild, only examples of Redirect 301 or RedirectPermanent Is there any difference between these? Would I benefit at all from replacing Redirect permanent with Redirect 301?
Technical SEO | | SamKlep1 -
1000 Pages on old website. What to do with the 301 redirects for this domain?
Hi Moz Community, I have a 301 redirect question... I just acquired an old domain: Totally in my niche Domain is 14 years old Website exists of 1000 pages Great amount of backlinks Website is offline since about 2 weeks Will place a new website online asap with new url structure For the 50 best scoring pages I wrote a new, but fully comparable/related article. I will put a 301 redirect from those old to the new pages. My question: What to do with the 950 other url's? Should I put a 301 redirect to the homepage? Should I forward those pages to the 404 page? Should I divide the 950 url's with a 301 redirect to the 50 new ones? Another solution maybe? Any idea what would be the best solution so we can save as much Google juice as possible? Thanks in advance!
Technical SEO | | snorkel0 -
Old domain to new domain
Hi, A website on server A is no longer required. The owner has redirected some URLS of this website (via plugin) to his new website on server B -but not all URLS. So when I use COMMAND site:website A , I see a mixture of redirected URLS and not redirected URLS.Therefore two websites are still being indexed in some form and causing duplication. However, weirdly when I crawl with Screaming Frog I only see one URL which is 301 redirected to the new website. I would have thought I'd see lots of URLs which hadn't been redirected. How come it is different to using the site:command? Anyway, how do I move to the new website completely without the old one being indexed anymore. I thought I knew this but have read so many blogs I've confused myself! Should I: Redirect all URLS via the HTACESS file on old website on server A? There are lots of pages indexed so a lot of URLs. What if I miss some? or Point the old domain via DNS to server B and do the redirects in website B HTaccess file? This seems more sensible but does this method still retain the website rankings? Thanks for any help
Technical SEO | | AL123al0 -
Spammers created bad links to old hacked domain, now redirected to our new domain. Advice?
My client had an old site hacked (let's call it "myolddomain.com") and the hackers created many links in other hacked sites with links such as http://myolddomain.com/styless.asp?jordan-12-taxi-kids-cheap-T8927.html The old myolddomain.com site was redirected to a different new site since then, but we still see over a thousand spam links showing up in the new site's Search Console 404 crawl errors report. Also, using the links: operator in google search, we see many results of spam links. Should we be worried about these bad links pointing to our old site and redirecting to 404s on the new site? What is the best recommendation to clean them up? Ignore? 410s? Other? I'm seeing conflicting advice out there. The old site is hosted by the client's previous web developer who doesn't want to clean anything up on their end without an ongoing hosting contract. So beyond turning redirects on or off, the client doesn't want to pay for any additional hosting. So we don't have much control over anything related to "myolddomain.com". 😞 Thanks in advance for any assistance!
Technical SEO | | usDragons0 -
Switching from a .org to .io (301 domain redirect)
I'm considering switching my main site from a .org to .io address; the .org is an exact match domain which helped to kickstart it a few years ago and now has about 50% repeat visitors, but was thrown off the Apple affiliation program for trademark infringement. I've found and purchased a nice (non-infringing) .io domain, and I've read the advice here on how to properly 301 the old domain; but my question is - does it matter that it's .io? Is this going to significantly hurt my rankings, even when everything has been 301'd properly? Another thought I had is that I may actually come out better off in the long run, what with Google penalties being applied to exact match domains. Is this a ranking suicide? If so, I'm tempted to leave it as is; even without the affiliation, it's making a good amount every month in ad fees that I don't want to disrupt. Thanks all!
Technical SEO | | w0lfiesmithUK0 -
Is it worth setting up 301 redirects from old products to new products?
This year we are using a new supplier and they have provided us a product database of approx. 5k products. About 80% of these products were in our existing database but once we have installed the new database all the URLs will have changed. There is no quick way to match the old products with the new products so we would have to manually match all 5k products if we were were to setup 301 rules for the old products pointing to the new products. Of course this would take a lot of time. So the options are: 1. Is it worth putting in this effort to make the 301 rules? 2. Or are we okay just to delete the old product pages, let the SE see the 404 and just wait for it to index the new pages? 3. Or, as a compromise, should we 301 the old product page to the new category page as this is a lot quicker for us do do than redirecting to the new product page?
Technical SEO | | indigoclothing0 -
200 Redirects for SEO instead of 301
We are working with a company on re-platforming our website. On a call yesterday they outlined a strategy to use 200 redirects for our top keywords instead of 301s. I am not familiar with this type of redirect and was wondering if anyone could provide some more insight.
Technical SEO | | EvergladesDirect0