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
-
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 -
What to do with old content after 301 redirect
I'm going through all our blog and FAQ pages to see which ones are performing well and which ones are competing with one another. Basically doing an SEO content clean up. Is there any SEO benefit to keeping the page published vs trashing it after you apply a 301 redirect to a better performing page?
Technical SEO | | LindsayE0 -
Migrating to new subdomain with new site and new content.
Our marketing department has decided that a new site with new content is needed to launch new products and support our existing ones. We cannot use the same subdomain(www = old subdomain and ww1 = new subdomain)as there is a technically clash between the windows server currently used, and the lamp stack required to run the new wordpress based CMS and site. We also have an aging piece of SAAS software on the www domain which is makes moving it to it's own subdomain far too risky. 301's have been floated as a way of managing the transition. I'm not too keen on that idea due to the double effect of new subdomain and content, and the SEO impact it might have. I've suggested uploading the new site to the new subdomain while leaving the old site in place. Then gradually migrating sections over before turning parts of the old site off and using a 301 at that point to finalise the move. The old site would inform user's there is a new version and it would then convert them to the new site(along with a cookie to auto redirect them in future.) while still leaving the old content in place for existing search traffic, bookmarks and visitors via static URLs. Before turning off sections on the old site we would create rel canonicals to redirect to the new pages based on a a mapped set of URLs(this in itself concerns me as the rel canonical is essentially linking to different content). Would be grateful for any advice on whether this strategy is flawed or whether another strategy might be more suitable?
Technical SEO | | Rezza0 -
Redirect URLS with 301 twice
Hello, I had asked my client to ask her web developer to move to a more simplified URL structure. There was a folder called "home" after the root which served no purpose. I asked for the URLs to be redirected using 301 to the new URLs which did not have this structure. However, the web developer didn't agree and decided to just rename the "home" folder "p". I don't know why he did this. We argued the case and he then created the URL structure we wanted. Initially he had 301 redirected the old URLS (the one with "Home") to his new version (the one with the "p"). When we asked for the more simplified URL after arguing, he just redirected all the "p" URLS to the PAGE NOT FOUND. However, remember, all the original URLs are now being redirected to the PAGE NOT FOUND as a result. The problems I see are these unless he redirects again: The new simplified URLS have to start from scratch to rank 2)We have duplicated content - two URLs with the same content Customers clicking products in the SERPs will currently find that they are being redirect to the 404 page. I understand that redirection has to occur but my questions are these: Is it ok to redirect twice with 301 - so old URL to the "p" version then to final simplified version. Will link juice be lost doing this twice? If he redirects from the original URLS to the final version missing out the "p" version, what should happen to the "p" version - they are currently indexed. Any help would be appreciated. Thanks
Technical SEO | | AL123al0 -
301 redirect relative or absolute path?
Hello everyone, Recently we've changed the URL structure on our website, and of course we had to 301 redirect the old urls to the coresponding new ones. The way the technical guys did this is: "http://www.domain.com/old-url.html" 301 redirect to "/new-url.html"
Technical SEO | | Silviu
meaning as a relative redirect path, not an absolute one like this:
"http://www.domain.com/old-url.html" 301 redirect to "http://www.domain.com/new-url.html" This happened for few thousands urls, and the fact is the organic traffic dropped for those pages after this change. (no other changes were made on these pages and the new urls are as seo friendly as possible, A grade on On-Page Grader). The question is: does the relative redirect negatively affects seo, or it counts the same as an absolute path redirect? Thanks,
S.0 -
I can buy a domain from a competitor. Whats the best way to make good use of these links for my existing website
I can buy a domain from a competitor. Whats the best way to make good use of these links for my existing website
Technical SEO | | Archers0 -
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 -
How to Redirect only specific pages to new domain
My HTACCESS FILE IS AS FOLLOWS: rewriteengine on
Technical SEO | | askthetrainer
rewritecond %{HTTP_HOST} ^mydomain.com$
rewriterule ^mydomain/(.*)$ "http://www.mydomain.com/$1" [R=301,L] #4d864805b49b5 I want to move ONLY specific pages from this domain to a new domain How do I edit my HTACCESS (which redirects http:// to www.) to move specific pages from old domain (which I have to delete) to new domain.... I.e. http://mydomaon.com/move.html needs to move to http://mynewdomain.com/move.html Where i can delete the original domains0