Are your 301 Redirects Really Permanent 301's?

{ Posted on 1:00 PM by Noah Wieder }
In working with several developers over the past decade I've learned that many really don't understand SEO. And while I now enough about web development and programming to break something when I'm curious or impatient I had to find tools to help me double check the work being performed.

One of the biggest issues I've run into is when I move a web site or convert a site from blogger to Wordpress or from a .Net or Web 2.0 property to a Wordpress platform.  The issue is how not to lose the Google Link Juice and your subscribers or followers. All that work done on SEO could be lost if your developers don't follow some SEO principles and concepts.

Most importantly redirecting old URL's to new URL's with a proper 301 redirect. The way you redirect your own web pages is usually dependent on your web Server for a server side redirect. Most Linux servers running web sites use Apache so redirection is done using the Apache Mod Rewrite, simple 301 redirects or both.  Either of which are administered by an HTACCESS file. Mod Rewrite requires you install the Mod Rewrite Engine on your Apache Server. I'm not going to write about how to best implement your 301 redirects as there are already many great write ups on that topic. This site does a nice job of providing 301 redirect examples if that's what you're looking for.

According to Google's help pages:
If you need to change the URL of a page as it is shown in search engine results, we recommended that you use a server-side 301 redirect. This is the best way to ensure that users and search engines are directed to the correct page. The 301 status code means that a page has permanently moved to a new location.
Some developers may find it easier to use client side redirects which can hinder your SEO friendliness.  A perfect server side 301 redirect will ell the search engine the old page has permanently moved.  For example: the URL http://www.searchbug.com/peoplefinder/peoplebyname.aspx now takes users to http://www.searchbug.com/peoplefinder/ which is exactly what the web developer wants.

Once you have added your 301 redirect, make sure the search engines see that your process is seeing the header as "HTTP/1.1·301·Moved·Permanently".  


An easy way to accomplish this is to use an HTTP Viewer.  Simply enter your URL in the viewer and click submit. Let it work it's magic and then under "Receiving Header" information make sure it shows "HTTP/1.1·301·Moved·Permanently" and not something else like "HTTP/1.1·200·OK". 


Once you confirm your link is a 301 redirect, you are all set.

2 Response to "Are your 301 Redirects Really Permanent 301's?"

well thats why you do it in google webmaster tool so regardless of server technology, google knows there is a 301 in place

You can't use webmaster tools once you forward the URL on the backend since you need to validate the site in order to use webmaster tools. If you know of a step by step trick, my readers and I would appreciate the tip.