08-02-2018, 07:12 AM
A 301 redirect is a permanent redirect which passes between 90-99% of link equity (ranking power) to the redirected page. 301 refers to the HTTP status code for this type of redirect. In most instances, the 301 redirect is the best method for implementing redirects on a website.
301 Redirects in Apache
Problem:
Back when we launched our first website, seomoz.org, it was hosted at <!-- w --><a class="postlink" href="http://www.socengine.com/seo/">www.socengine.com/seo/</a><!-- w --> rather than on its own domain. When the original developers were moving seomoz.org to its own dedicated server, they wanted it to be accessed as its own domain rather than as a subdirectory of socengine.com. They needed visitors accessing anything in <!-- w --><a class="postlink" href="http://www.socengine.com/seo/">www.socengine.com/seo/</a><!-- w --> to be redirected to <!-- w --><a class="postlink" href="http://www.seomoz.org">www.seomoz.org</a><!-- w -->. The redirection had to accommodate several file and folder name changes and had to be done with 301 redirects in order to be search engine-friendly. They also needed to forward <!-- m --><a class="postlink" href="http://seomoz.org">http://seomoz.org</a><!-- m -->, too, for aesthetic purposes and to avoid canonicalization errors.
Solution:
The simplest approach to do this would have been to add 301 redirects to the PHP code that powered seomoz.org using PHP's header function. Utilizing the power of the apache module mod_rewrite, however, the developers realized they could match specific patterns for entire folders and redirect them to their new URLs without having to go through every PHP script.
301 Redirects in Apache
Problem:
Back when we launched our first website, seomoz.org, it was hosted at <!-- w --><a class="postlink" href="http://www.socengine.com/seo/">www.socengine.com/seo/</a><!-- w --> rather than on its own domain. When the original developers were moving seomoz.org to its own dedicated server, they wanted it to be accessed as its own domain rather than as a subdirectory of socengine.com. They needed visitors accessing anything in <!-- w --><a class="postlink" href="http://www.socengine.com/seo/">www.socengine.com/seo/</a><!-- w --> to be redirected to <!-- w --><a class="postlink" href="http://www.seomoz.org">www.seomoz.org</a><!-- w -->. The redirection had to accommodate several file and folder name changes and had to be done with 301 redirects in order to be search engine-friendly. They also needed to forward <!-- m --><a class="postlink" href="http://seomoz.org">http://seomoz.org</a><!-- m -->, too, for aesthetic purposes and to avoid canonicalization errors.
Solution:
The simplest approach to do this would have been to add 301 redirects to the PHP code that powered seomoz.org using PHP's header function. Utilizing the power of the apache module mod_rewrite, however, the developers realized they could match specific patterns for entire folders and redirect them to their new URLs without having to go through every PHP script.
![[-]](https://seomotionz.com/themes/cerulean/collapse.png "[-]")
