Ok, I'm getting ready to yank the old content on our web server and replace it with a completely new site layout and design. I have not been able to find any good resources that outline how to set up a 301 redirect for specific pages, not for the entire site. In apache, it seems to be very easy with the .htaccess file. But in IIS, other than setting up a 301 in the asp of the old pages and having to leave them on the server, (I want to get this old crap off the server) I'm completely discombobulated as to how to make this happen most effectively.
Subscribe to HRA Now!
SEO Class in Chicago, IL
Learn How To Optimize Your Website on July 26, 2013
Looking for personalized in-depth SEO training among your peers?
High Rankings is offering a 1-day customized SEO training class in Chicago. Class size is limited so please sign-up now if you want in!
Are you a Google Analytics enthusiast?
Share and download Custom Google Analytics Reports, dashboards and advanced segments--for FREE!
www.CustomReportSharing.com
From the folks who brought you High Rankings!
More SEO Content
International SEM | Social Media | Search Friendly Design | SEO | Paid Search / PPC | Seminars | Forum Threads | Q&A | Copywriting | Keyword Research | Web Analytics / Conversions | Blogging | Dynamic Sites | Linking | SEO Services | Site Architecture | Search Engine Spam | Wrap-ups | Business Issues | HRA Questions | Online Courses
301 Redirect In Iis
Started by
mopacfan
, Sep 17 2003 10:25 AM
5 replies to this topic
#2
mopacfan
-
- Active Members
-
- 103 posts
HR 3
- Location:Missouri
Posted 18 September 2003 - 08:47 AM
No replies yet? Sheesh, I thought at least one person would have the answer 
I can set up a redirect on an entire domain, but setting up a redirect on the content when the domain is the same is proving quite difficult.
Someone has had to come across this before, I hope...
I can set up a redirect on an entire domain, but setting up a redirect on the content when the domain is the same is proving quite difficult.
Someone has had to come across this before, I hope...
#3
Matt B
-
- Active Members
-
- 558 posts
The modem is the message.
- Location:Canton, OH
Posted 18 September 2003 - 08:53 AM
When we have re-designed websites, we have simply used a custom 404 error page to retain anyone coming to the new site on old links. You can add this page when your new site goes live, and you shouldn't lose any traffic. It will take a few weeks for the major SE's to update their index, but once they do you should be fine.
A 301 for individual pages is overkill, IMO.
A 301 for individual pages is overkill, IMO.
#4
polarmate
-
- Active Members
-
- 65 posts
HR 3
Posted 18 September 2003 - 09:46 AM
The steps are very simple. To redirect a file:
1. Start Internet Services Manager on the server
2. Click on your web site
3. Select the appropriate folder you want to redirect in the right pane and drill down to the file you want to redirect
4. Right-click and select Properties from the menu
6. Select the Tab labeled File
7. Select the option called 'A redirection to a URL'
8. In the textbox labeled 'Redirect to' type in the new URL for this directory
9. In the section 'The client will be sent to:', check the option 'A permanent redirection for this resource'
10. Click the button OK
11. Repeat this for all files.
However doing this file by file is cumbersome and may cause undue server load - I am not entirely sure.
But you can do this same thing at the folder level: in #6, you will use the Tab called Directory instead of File.
If you are doing this for a web site then you need to do it only at the web site level. You will select Properties from the left pane of IIS and set up the redirect in the tab called Home Directory.
Setting up a redirect for each and every file is really not necessary. Alternately, you can use a custom 404 page that is an ASP page - not htm - and redirect using ASP headers to the appropriate file. You will need to maintain a 1-1 map of old filename to new to be able to do this.
1. Start Internet Services Manager on the server
2. Click on your web site
3. Select the appropriate folder you want to redirect in the right pane and drill down to the file you want to redirect
4. Right-click and select Properties from the menu
6. Select the Tab labeled File
7. Select the option called 'A redirection to a URL'
8. In the textbox labeled 'Redirect to' type in the new URL for this directory
9. In the section 'The client will be sent to:', check the option 'A permanent redirection for this resource'
10. Click the button OK
11. Repeat this for all files.
However doing this file by file is cumbersome and may cause undue server load - I am not entirely sure.
But you can do this same thing at the folder level: in #6, you will use the Tab called Directory instead of File.
If you are doing this for a web site then you need to do it only at the web site level. You will select Properties from the left pane of IIS and set up the redirect in the tab called Home Directory.
Setting up a redirect for each and every file is really not necessary. Alternately, you can use a custom 404 page that is an ASP page - not htm - and redirect using ASP headers to the appropriate file. You will need to maintain a 1-1 map of old filename to new to be able to do this.
#5
mopacfan
-
- Active Members
-
- 103 posts
HR 3
- Location:Missouri
Posted 18 September 2003 - 12:59 PM
Polarmate,
Thanks for the reply, but I found that set of instructions many times over. However, you can't direct to a new url when you're using the same address
The page names are currently named something like sc.asp and the new file is square_plastic_cap.asp. I don't want to leave all the old files on the server to be mixed in with all the new files. With the .htaccess file in apache, I could just list the files and the new 301 redirects. (Matt, the 404 does not allow G. to transfer page rank)
However, it appears that the only solution is to leave the files on the server and use an asp 301 redirect in the code. I'll just have to leave the pages on the server for a few months until the spiders have all updated their indexes.
Thanks Billy (gates)
Thanks for the reply, but I found that set of instructions many times over. However, you can't direct to a new url when you're using the same address
The page names are currently named something like sc.asp and the new file is square_plastic_cap.asp. I don't want to leave all the old files on the server to be mixed in with all the new files. With the .htaccess file in apache, I could just list the files and the new 301 redirects. (Matt, the 404 does not allow G. to transfer page rank)
However, it appears that the only solution is to leave the files on the server and use an asp 301 redirect in the code. I'll just have to leave the pages on the server for a few months until the spiders have all updated their indexes.
Thanks Billy (gates)
#6
polarmate
-
- Active Members
-
- 65 posts
HR 3
Posted 18 September 2003 - 03:16 PM
Hmmm I can't get to the IIS server that I have access to from time to time. I will check up on that for you.
As for 404 thing:If you make your 404 handler an ASP page then you may be able to transfer the Pagerank. An htm 404 handler will not allow you to do that. That's what I was talking about earlier.
That is how URL Rewriting is done using ASP: a 404 handler written in ASP and an ASP 301 redirect. The PageRank should transfer to the new page because the 404 page changes the headers to 301. We had a very interesting thread on the IHY Forums about this. In your case, you are not really rewriting the URL, but you want to do the same thing: trap a 404 and route the browser/spider on to the correct page.
Check out the thread here:
http://www.ihelpyous...6363#post106363
I am linking you to the middle of the thread - you may want to scroll above this marker and read the whole thing.
HTH!
As for 404 thing:If you make your 404 handler an ASP page then you may be able to transfer the Pagerank. An htm 404 handler will not allow you to do that. That's what I was talking about earlier.
That is how URL Rewriting is done using ASP: a 404 handler written in ASP and an ASP 301 redirect. The PageRank should transfer to the new page because the 404 page changes the headers to 301. We had a very interesting thread on the IHY Forums about this. In your case, you are not really rewriting the URL, but you want to do the same thing: trap a 404 and route the browser/spider on to the correct page.
Check out the thread here:
http://www.ihelpyous...6363#post106363
I am linking you to the middle of the thread - you may want to scroll above this marker and read the whole thing.
HTH!
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
