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
-
New ecommerce site: Close old site and full domain redirect or keep it linking to new site?
We have rebranded and are working on our new site (B). Our old site (A) has a much higher domain/page authority than our new site. Currently we have the original Site A still there, with all links/pages pointing to the new Site B when people click. I am unsure whether we'd be best to close down the Site A completely and do a full domain redirect to Site B. Site A: 10 years age and has a moderate amount of links to it.
Web Design | | ModowestNZ
Homepage - PA: 24 DA:11 Site B: 6 months age, few links
Homepage - PA: 1 DA:2 My concern with the full domain redirect is that the indexed/ranking pages would dissapear. The benefit is less brand confusion for our niche range of party accessories.0 -
Affects of a Home Link 301 Permanent Redirect in the Main Nav Bar
Hi I created a home page link in the main nav bar using functions.php request, and this leads to the home page, and it works fine. The logo on the site when clicked, resolves the home page domain.com which is fine. Is it ok to have a home page link in my main nav bar, as well as a clickable logo which on-click returns the web user to the home page also? (any seo implications with the permanent 301 redirects?) I like to give web users the choice especially as not all users are aware that they can click back to the home page by clicking on the logo. I considered breadcrumbs already. Thanks.
Web Design | | SEOguy10 -
Should I Kill the Old Domain or Work Through the Redirect?
Our IT department wasn't able to create a new directory on the current domain name for whatever reason and so we had to create a new domain name called ww2.domain.com to build the new site. So now we have the new site up and appartly some PDFs and pages are being directed to the from the old site. www.domain.com but 10,000 pages /PDFs are still indexed in Google and are not redirected. So when you open the page you get the old www.domain.com instead of it redirecting to ww2.domain.com. It's sort of a mess! My question is can we just kill the old domain name and move the ww2.domain.com back to the old domain? We also want to do away with the ww2.domain.com and go back to www.domain.com. I know it's confusing as heck! What would you recommend?
Web Design | | Eagle-ABS0 -
Is there a way to redirect URLs with a hash-bang (#!) format?
Hi Moz, I'm trying to redirect www.site.com/locations/#!city to www.site.com/locations/city. This seems difficult because anything after the hash character in the URL does not make it to the server thus cannot be parsed for rewriting. Is there an SEO friendly way to implement these redirects? Thanks for reading!
Web Design | | DA20130 -
Redirects (301/302) versus errors (404)
I am not able to convincingly decide between using redirects versus using 404 errors. People are giving varied opinions. Here are my cases 1. Coding errors - we put out a bad link a. Some people are saying redirect to home page; the user at least has something to do PLUS more importantly it does NOT hurt your SEO ranking. b. Counter - the page ain't there. Return 404 2. Product removed - link1 to product 1 was out there. We removed product1; so link1 is also gone. It is either lying in people's bookmarks, OR because of coding errors we left it hanging out at some places on our site.
Web Design | | proptiger0 -
Redirecting Images
Hi, I'm wondering how important it is when relaunching a site on a new platform (switching to Drupal) to serve up images from the same file paths in order to ensure consistency during the changeover. I've tried to keep the questions straightforward so that this post can be useful to people in a similar situation in future: How much difference do the file paths make to SEO? Does Google care or even notice if the image file paths change? Is it worth forcing Drupal to mimic our old file paths for the sake of consistency with the old site in order to maintain rankings OR do we take the opportunity to redesign our file paths for better SEO? Any help would be much appreciated 🙂
Web Design | | Tinhat0 -
Is there a limit for 301 redirection in htaccess file?
For the SEO perspective, there is a limit for the number of 301 redirection inside the htaccess file?
Web Design | | Naghirniac0 -
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