Direct link vs 302 redirect

[cbarron]

So we have recently relaunched a site that we manage. As part of this we have changed the domain. The webdesign agency that built the new site have implemented a direct link from the old domain to the new domain. What is best practice a direct link or a 302 redirect? Thanks

[GPainter]

Is it a temp redirect ? If you're planning on move permanently you may want to think about 301ing the whole site to its relevant counter parts. a Direct Link is good for building up some authority and slowly migrating the site over time making sure each stage goes to plan rather than 301 the whole thing and panic if something goes wrong.  It really boils down to your longer term goal.

[cbarron]

Sorry yes I got a bit confused there. It is moved permanently so it should be a 301 rather than 302. But what is difference between the direct link and the 301. Is it just a case that the 301 can be more difficult to implement? I will not actually be implementing the redirect myself. This will be done by a 3rd party webdesign agency. I suppose I am keen to keep as much of the authority as possible from the old domain. Thanks

[GPainter]

A 301 is telling Search engines (and any links) that this link or site has moved permanently, this would then mean the value of the links would be moved to the new location. A link would imply the site is staying and a % of link juice would flow though it compared to more through a 301.  Other problem could be you may have duplicate content if your moving the domain.

If you do get a 301 done make sure they don't just 301 it all to the homepage it should be moved each category moved to its counter part (or as close to) as possible to maintain the transfer of authority & juice.

Hope that helps, and good luck!

[JaneCopland]

Hi Conor,

Chris's answer here is perfect.

You definitely don't just want to link from the old site to the new; you want the old site to be "gone" and to serve a 301 redirect to tell search engines "this resource has permanently moved, and is now over here ----> [new site]".

301 redirects are vital; 302s do not pass authority from one URL to another (there is speculation that a 302 that has been in place for a very long time might be treated as a 301 by Bing, but let's go with the fact that they're next to useless in most cases for passing SEO value).

The 301 redirect should be implemented on a page by page basis, meaning that the home page at www.oldiste.com redirects to www.newsite.com. www.oldsite.com/page1.html redirects to that page's new location, e.g. www.newsite.com/page1.html, and so forth. As Chris says, you do not want www.oldsite.com/page23.html to redirect to the home page of www.newsite.com. The only case in which you'd want to do this is if /page23.html no longer exists on the new site.

How this is done depends on what type of server your site sits on. If you are using an Apache server, the web developers will do this in the site's .htaccess file. If you are using a Microsoft IIS server, this will be done in a control panel. The web development company will clearly know which server you're using and where this will be done.

Some servers and hosts still implement 302 redirects as standard and not 301s, which is very frustrating from an SEO point of view. There should be nothing more difficult about creating a 301 than a 302.

The short version is: 301 the old site to the new if you want to transfer the authority from the old site to the new one. This will ensure that you bring most of that authority with you.

[cbarron]

Thanks a million for the help guys.