Note: Windows Servers use different instructions, which can be found in this posting

Our blog posting on verifying 301 redirects led to several questions about the technical details of redirects. Therefore, we are posting some information which you may find useful.

Below you will find out how to do canonical 301 redirects, redirect individual pages, and redirect whole domains.

301 redirects for Linux/Apache servers are created using a special file called .htaccess. Once the redirects have been specified in this file, it is simply uploaded to the root of the hosting account and the server handles it from there. 301 redirects can be easily created in this way for both shared and dedicated hosting accounts.

Very special note: This information is by no means comprehensive. Creating .htaccess files should be done carefully. If you already have an HTACESS file, you should back it up, so if anything goes wrong, you can revert to the old code!

Creating a 301 Redirect to Solve Canonicalization Duplicate Content

Canonicalization duplicate content is created when a site shows content at http://www.domain.com and http://domain.com. Search engines consider this 2 separate sets of content (even though they’re both exactly the same), and this can sometimes negatively impact the site’s rankings.

A 301 redirect can be set up to force all non-www URLs to the corresponding www URLs, or vice versa. In addition to eliminating any potential duplicate content issues, this will also combine the strength of all links pointing to both non-www and www pages on the site, allowing the site to maximize the impact of any link to its pages.

REQUIREMENT: The following 301 redirect instructions will NOT work unless the Apache ModRewrite module is enabled on the hosting server. This is a standard Apache module that is normally enabled by default, so if the redirects don’t work within 24 hours of uploading the .htaccess file you will need to contact the hosting company or administrator to check if ModRewrite is enabled.

From non-www to www:

1. FTP into the site’s hosting account and check to see if there’s an existing .htaccess file.
2. If there’s not, create a file in Notepad or any text editor called .htaccess (technically, this file is just an extension with no name).
   Note: Some programs may not let you create a file with no name and just an extension, and if you need to email this file to a webmaster for implementation many email clients such as Outlook may refuse to send it. To get around this, create the file with a regular name like “test.htaccess”, and then rename it in an FTP client right before uploading
3. Paste the code below this list into the site’s .htaccess file:
4. Upload the file into the root directory of the site’s hosting account.
   Once the .htaccess file has been uploaded, it should take effect within 24 hours or less. If it does not, check with the hosting company or administrator to make sure that the ModRewrite module is enabled for the site’s hosting account.

Code:

RewriteEngine on
RewriteCond %{HTTP_HOST} ^yoursite.com
RewriteRule (.*) http://www.yoursite.com/$1 [R=301,L]

From www to non-www:

1. FTP into the site’s hosting account and check to see if there’s an existing .htaccess file.
2. If there’s not, create a file in Notepad or any text editor called .htaccess (technically, this file is just an extension with no name).
   Note: Some programs may not let you create a file with no name and just an extension, and if you need to email this file to a webmaster for implementation many email clients such as Outlook may refuse to send it. To get around this, create the file with a regular name like “test.htaccess”, and then rename it in an FTP client right before uploading
3. Paste the code below this list into the site’s .htaccess file:
4. Upload the file into the root directory of the site’s hosting account.

Code:

RewriteEngine on
RewriteCond %{HTTP_HOST} ^www.yoursite.com
RewriteRule (.*) http://yoursite.com/$1 [R=301,L]

Once the .htaccess file has been uploaded, it should take effect within 24 hours or less. If it does not, check with the hosting company or administrator to make sure that the ModRewrite module is enabled for the site’s hosting account.

Creating a 301 Redirect from One Internal Page to Another

1. FTP into the site’s hosting account and check to see if there’s an existing .htaccess file.
2. If there’s not, create a file in Notepad or any text editor called .htaccess (technically, this file is just an extension with no name).
   Note: Some programs may not let you create a file with no name and just an extension, and if you need to email this file to a webmaster for implementation many email clients such as Outlook may refuse to send it. To get around this, create the file with a regular name like “test.htaccess”, and then rename it in an FTP client right before uploading
3. Paste the following code into the site’s .htaccess file:
   Redirect 301 /oldpagename http://domain.com/newpagename
   Note: If you need to redirect multiple pages, simply add a new line to the .htaccess file for each page you’d like to redirect.
4. Upload the file into the root directory of the site’s hosting account.
   Once the .htaccess file has been uploaded, it should take effect within 24 hours or less. If it does not, check with the hosting company or administrator to make sure that the ModRewrite module is enabled for the site’s hosting account.

Creating a 301 Redirect from an Old Domain to a New One

1. FTP into the site’s hosting account and check to see if there’s an existing .htaccess file.
2. If there’s not, create a file in Notepad or any text editor called .htaccess (technically, this file is just an extension with no name).
   Note: Some programs may not let you create a file with no name and just an extension, and if you need to email this file to a webmaster for implementation many email clients such as Outlook may refuse to send it. To get around this, create the file with a regular name like “test.htaccess”, and then rename it in an FTP client right before uploading
3. Paste the following code into the site’s .htaccess file:
   Redirect 301 / http://www.newdomain.com/
4. Upload the file into the root directory of the site’s hosting account.
   Once the .htaccess file has been uploaded, it should take effect within 24 hours or less. If it does not, check with the hosting company or administrator to make sure that the ModRewrite module is enabled for the site’s hosting account.

For special cases and other server configurations, there are multiple sites online which are server specific and give more instructions about how to do 301 redirects. As we stated above, 301 redirects should be done carefully, and if the site fails to operate after an HTACESS file is uploaded or change, you should revert back to the old code until a fix can be made.

Tags: 301 redirect, apache 301 redirect, linux 301 redirect

This entry was posted on Wednesday, July 29th, 2009 at 2:11 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.