In this last post about SEO friendly redirects I will be covering IIS, ASP, and PHP redirects. In the first post I explained the differences between a 301 and 302 redirect and also gave some examples of when you would use them. The second post discussed actually implementing those redirects with the Apache web server. Please read my previous posts if you don’t understand what an SEO friendly redirect is.
Today I will talk about implementing 301 redirects on IIS. I will briefly discuss
server-side scripting and how it can be used to perform redirects as well.Read More
In my last post titled “When and why to use 301 or 302 redirects”, I talked about why you might use these redirects and briefly explained the differences between the two. It would be a good idea to read the last post if you don’t know what a 301 or 302 redirect are because today I’m going to discuss ways to implement them.
So, you have decided that your site has a need for a SEO friendly redirect. The good news is that they are not too hard to setup on most server configurations, If you are using Apache or IIS, the tools you need are already installed and ready to go.
Since I’m a pretty big Linux fan I tend to focus on Apache, but we can’t ignore the popularity and power of IIS, so I will go over that configuration on my next post. Today though we will focus on Apache.
URL Mapping is a good way to get lost — especially if you don’t know what you’re doing. And, it’s important because doing it wrong can have dire consequences for your site. This is definitely a job for the professionals. So, who’re you gonna call?
Before you pick up the phone, you need a few facts. First, it depends on how you’re going to do it and that depends on your web server. Lost yet? Consult this handy guide:
Apache server: Mod Re-write.
Microsoft IIS: either an ISAPI Rewrite or the URL Mapping option of ASP.NET.
If all this sounds like Geek to you, call a web developer and do it right.