Understanding Web Page Redirection, the smart way
This article is intended to help you understand web page redirection and some of the technologies involved with doing so.
If you are looking for a more comprehensive guide to redirecting your page. Or if you are anxious for code samples on redirecting your page, then please reference this article: How to redirect a web page, the smart way.
What is Web Page Redirection?
Well, obviously this is simple, and not very complicated; redirecting a web page just means that you get transfered to another web page when accessing the current page or attempting to. That is pretty clear.
What isn’t clear — is that there are really at least 2 major different forms of web page redirection; Client-side Redirection & Server-side Redirection
What is Client-side Redirection?
Well in this context, it’s your browser. More specifically: the contents of the web page your browser literally downloaded is the client (html). Because when you visit a web page, that page is downloaded and stored temporarily on your computer (also known as being cached).
What is Server-side Redirection?
Basically, as a user visiting a web page — you can’t see anything that happens on the server-side.
This means that when a redirection occurs on the server-side, the only way you see it is that the original URL you were contacting suddenly changes to the new URL that the server-side is redirecting to. This is typically the best way to go about redirecting, because it is really the only “safe” way of communicating to a search engine “Hey, this page has been moved, here is the correct URL”
With that said, it is important to understand the different types of URL redirection. Ultimately, the redirection occurs when your browser or client is instructed of the redirection. My rule of thumb is to not ever redirect unless it is permanent. That doesn’t necessarily apply to everything, but it is a safe route.
The 301 redirect is really the only redirect I use, because it is intended to be a permanent redirect, and search engines recognize this.
What should I stay away from?
In short: Client-side Redirection. These methods of redirecting a web page range from using html meta tags, to javascript, and even using flash embedded on a page to redirect. All of these methods are notorious for getting you de-indexed from search engines, or at the very least, you’re page getting automatically penalized from search engines. Stay away from client-side redirection, unless it is user-initiated (like clicking on a link).
That pretty much sums it up. It is important to keep in mind that if you are trying to redirect your page, do some research to find out exactly which redirect is right for you.
Lary Stucker said,
January 11, 2010 @ 8:10 pm
In iis is there a way to create a 301 redirect on the server side where I don’t have to leave the old file in place? We chenged the directory strucutre of our site and want to delete the old files once we have our 301s in place.
Maynard Hidrogo said,
January 6, 2010 @ 2:36 pm
Where do you get this information? Thanks a lot
David Becker said,
December 22, 2009 @ 10:16 pm
Hi Steven,
I’m having an issue with my web host. All I want is a permanent redirect from http://elearningconsultant.com.au to http://www.elearningconsultant.com.au because I’m told my page rank will be diluted without it. Firstly is this true? and secondly why is my ISP saying it cant be done? They are running IIS and I sent them some links on how to do it on IIS. Thier last email was:
I’ve had a look at the links your provided and while you can indeed
provide a permanent redirect to _another_ site, if you redirect your
site permanently to your site, I think you would cause a looping error.
HT access files do not form a part of the windows IIS server framework,
and as such don’t work on windows IIS servers.
Unfortunately after much discussion in the office we are not able to
offer you another solution other than Joels initial one.
Joels solution was:
There is no way to redirect from non-www to www with IIS. The only way
this can be performed is in the code of your website.
The way Deepna set it up earlier would be on for people going directly
to your domain, but if they browse to a page on your domain, it would
not be able to redirect them as it only redirects access to the
index.html page.
Essentially, the only way you will be able to set up this redirect is to
write some code that is on each page of your site, that checks the URL
for the ‘www’ and if it doesn’t exist, redirects people to the correct
place.
Unfortunately there’s no easier way to accomplish this that will cover
every URL people will browse to.
I only want the domain redirected, not every page. Anyway I’m not technical enough to offer them a solution, so any suggestions you can give me are greatly appreciated:)
Happy holidays!
Dave