Type of redirect?
-
I'm almost ready to launch a website redesign. We are going to move what's currently being hosted on olddomain.com to newdomain.com. We want to do this early to avoid error and to have olddomain.com redirect to newdomain.com until the new content is ready.
Once the redesign is complete, we'll push the new content to olddomain.com (as it holds a higher SEO value) and take away the redirect.
A. Does this sound like a good idea?
B. What kind of redirect should I use? 302? 307?
Thanks, and sorry for the confusion
-
The 301 cancellation itself is immediate. It may take time for search engines to crawl your site and notice the change on any given page.
-
How long does it take to cancle the 301?
I had a 301, I just canceled it & uploaded my new content.
-
If you needed to proceed with your plan, then a 302 allows you to redirect traffic for a short period such as what you are describing. I would define "short" as being 7 days or less.
If you are going to move for 30 days or more, I would use a 301 redirect. Once the upgrade is complete, cancel the 301 and send your traffic back.
-
I get why you're confused -- it lies with the presence of our old site and the permissions we have to change content.
So we're not just taking the site down for maintenance upon completion -- we're pointing the domain to a different server (both domains will be pointing to different places). The main question for me is how to do this smoothly?
But, mostly I just needed confirmation that the developer's idea wasn't the best one and reading your responses has helped me understand this a bit better.
-
I am still a bit confused.
You are currently using olddomain.com. You wish to upgrade the site.
You have beta.olddomain.com. You perform your development work on beta.olddomain.com while your live site continues to receive traffic.
Upon completion of development you would take "olddomain.com" down for maintenance. You update the site with the changes from the beta site, then you re-open the site and are live.
The above method represents the stand process under which most sites are upgraded. What you are describing sounds more like what happens in the offline world. You own an office which needs to be remodeled. You then move to a temporary office because the construction workers require access to your old office to make the changes. That method is not required in the virtual world.
-
You're correct in the direction things need to go.
The point isn't to preserve link juice in 2 ways -- it's to maintain a domain that we've had for years and that has tons of links pointing to it.
Pretty confusing stuff if you ask me.
-
We want to use olddomain.com because we've had it for years, our customers know it, and we have tons of links pointing to it. We set up beta.olddomain.com for testing.
The only reason we even need newdomain.com is because our old site was mandated to us by the manufacturer and we need to keep it per their rules. We don't care about that site at all though -- we just need to transfer it at the same time that we get the new content onto the old domain, does that make sense?
-
I agree with Dan's approach.
It sounds like you want to use your current "olddomain.com" as your development area. That doesn't make sense to me. If you use your "newdomain.com" site for development, then when you are ready upgrade/switch your current domain with the newly re-designed content, you wont need to use any form of redirect. It's less work for you and search engines.
-
so your saying that:
beta.olddomain.com will go to: olddomain.com
existing content at olddomain.com will go to newdomain.comif that's correct it may be a bit over my head. perhaps someone else can chime in?
it sounds like you are trying to preserve link juice two ways, which i don't think you can do . perhaps a staggered launch that will allow the 301 to redirect the content, and then a relaunch via the beta content later (no 301s)?
-
Hi Dan, thanks for the response.
I agree that it sounds risky, that's why I posted here It was the route my developer suggested.
The site is being developed on a local server but we also have a subdomain set up (beta.olddomain.com). We'll be using the same domain, but the content that used to be there will be going to a new domain because it is a website that was mandated to us by our corporate manufacturer.
We have already planned to set up the 301 redirects from our old urls to the new ones. The main concern I have is the transfer of the new content to the old domain (from beta.olddomain.com to olddomain.com). Do you have any suggestions for a smooth transition in this regard?
-
hi Kyle,
all the domain forwarding sounds kind of dangerous to me.i've done a few site redesigns and can offer the following advice:
1.) if it ain't broke, don't move it.2.) if you can develop your new site via a local server, or a cheap host (set up a pw so only you can see it while you develop), i would do that. again, just moving domains seems risky.
301 redirects communicate to the search engines that you are permanently redirecting your content to your new site. you want to consider doing a 301 for ALL content/urls. this will help preserve rankings. a lot of times you can use a program like rewrite to handle this if you have tons of urls.
your best bet is to get all your "new" content ready to go, live, and then 301 redirect to it at your new domain. if that is happening on THE SAME domain (old content -> new content ; same domain), you want to 301 redirect your old url's to their equivalent new urls.
hope that helps! :>)
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
-
How long should an old site redirecting to a new site remain activated on a server?
Once I switch a site to a new domain (with links to corresponding/relative pages), will I have to keep the old site live forever for those links to work, or how long should I wait before I inactivate the old site on our server?
Web Design | | jwanner0 -
301 Redirect Issue for URL with # and !
Hi All, We had a WIX website and now moved to Wordpress. I m having issue while doing redirecting from old URL to new URL. Example: Old Url: http://www.firsttraffic.com.au/#!traffic-management/ccfn New Url: http://www.firsttraffic.com.au/our-services/traffic-management/ I tried different wordpress plugin but nothing works. I m thinking its due to the # . But How can I to redirection for URL like this . Thanks
Web Design | | emarketexperts0 -
How to Redirect Old Domain to a New Domain?
One of my clients has chosen a new domain for her website so we will redirect the old domain to the new. I understand that once redirected, most of the authority built up over the years for the old domain will pass through to the new domain. Is this correct? Can this be done through the Wordpress dashboard, say with a plugin perhaps? I have a plugin called 404 Redirected I was going to try to use for this purpose. Finally, the client has other domains (5 total) she has used for one reason or another. She wants to consolidate all of them and have everything redirected to her new domain. Do you see any downside to this in terms of crawling, Google trust and authority? I know there are some user experience issues to deal with, but we're addressing those. I just don't want to do anything that may cause Google not to trust the new domain. Thanks, Dino
Web Design | | Dino640 -
HTTPS redirecting to subdomain; do I need to 301 to HTTP first?
Hello there, quick question on HTTPS downgrade to HTTP. Originally, full site was HTTPS. Redesign eliminated need for secure layer. Site currently has https 301'd to sub.domain.com. Ideally, site would live at domain.com, but with the old site having been indexed https, the security warning triggers when you visit, hence the 301 to a subdomain. Thinking possible solutions here are to a) add back in secure layer or b) 301 all old https pages to new http pages. Have I overlooked something? With (a), I will see no SEO impact, correct? With (b), can I expect impact similar to a relaunch? Have seen a lot of chatter that there is some impact in switching http to https, but not much the other way. Any help much appreciated!
Web Design | | alimo0 -
Redirect From .aspx to .html if already indexed - Website Redesign
Hi Guys I would like to know if somebody could possibly shed some light on this for me. We are in the process of re-designing our site, but we are keeping all of our content in terms of site structure, internal linking etc. the same. Now we were wondering if it would be a SEO best practice for us to change our pages' extension from .aspx to .html and just put a re-direct from the aspx to the html pages. Or should we keep everything as is, and maybe just revise our on-page seo efforts as well as do some more link-building. I just have to note that we are currently ranking very well for top positions and obviously all these pages are already nicely indexed. And then another question I have is with regards to our mobi site of this same website.Our dev team created it using Responsive Web Design, but they decided to implement techniques that show and hide content based on what device you are viewing it on. So when viewing it on your desktop, it will show content as per normal, but when viewing it on a mobile device it will hide this content and show the content formatted for that specific mobile device. So we are obviously sitting with a case of dup content here.Is this technique acceptable, or is there a workaround/different way of implementing this? Thanks In Advance Dave
Web Design | | DavidZA10 -
Optimal redirect configuration from a misspelled domain that we own.
We have a handful of inbound links to www.t-chek.com (note the hyphen). Our normal site is www.tchek.com (no hyphen). We own both domains and have some sort of domain-wide redirect set up now. This works fine for traffic, but I suspect it's not optimal for SEO purposes. I came to this conclusion by looking in OSE and noticing that none of the inbound links to www.t-chek.com were also being attributed to www.tchek.com. 2 questions: Is it immediately evident what type of redirect I have in place now, or do I need to figure that out? Is the fix as simple as editing the .htaccess file on the hyphenated domain? I don't have direct control over the hyphenated domain, and I'd like to be able to know exactly what we need to do so I can request help from my IT department. I'd appreciate hearing your wisdom. Thanks!
Web Design | | SheriGolla0 -
Parked Domain or Redirect
Should I park a domain or Redirect? And what is the best way? I need to switch our domain name. I currently have all of our domains redirecting to our main website. I have set up there own hosting in our cpanel account so I could redirect them to our main domain. Was this too many steps? I tried putting all of our domains in our main domains, .htaccess file, and redirected them to our main website, but they did not work. So that is why I set up there own cpanel accounts. Now they work fine. However, my hosting company told me that I could just park the domain on our current domains account. If I can redirect all of these domain in one place, that would be great. I thought that a parked domain is considered duplicate websites, as both urls work, displaying the entire website with both urls. So Would I have to re upload our entire website to the account that I want as our main domain? Or is there another way of going about doing this?
Web Design | | hfranz0 -
Is it necessary to redirect every Error page (404 or 500) found?
If I have Hundreds of pages with 404 and 500 erros should set up 301 redirects for all of them? Some of the pages have external links, some don't.
Web Design | | jmansd0