6 {{ upvoteCount | shortNum }}
6 {{ upvoteCount | shortNum }}

IIS 301 Redirects

by d3xt3r
5 replies
First I want to apologize if this is the wrong forum to post this in. I reviewed the list and it seemed to be the closest fit for what I'm looking for but I apologize in advance if that's not the case.

I'm working on a project for a client and need to setup some 301 redirects. They are using a IIS 7. Every tutorial I read on how to do this starts by clicking the file you want to redirect and selecting properties. The problem is the files don't exist, they are 404s that I want to redirect to similar pages.

Thanks in advance for any help on how to do this!
#301 #iis #redirects
  • Profile picture of the author RyanAndrews
    Could you create the files?
    Otherwise do the redirects at the scripting level (ASP?) rather than the web server level.
    {{ DiscussionBoard.errors[3418935].message }}
    • Profile picture of the author d3xt3r
      Hi Guys,

      Thanks for all the replies. We're talking about hundreds of files here, so moving them back unfortunately is not an option. I agree a 301 is the best way to handle this. I guess if there's no way to do it in IIS directly I'll have to loop into an ASP solution.
      {{ DiscussionBoard.errors[3429733].message }}
      • Profile picture of the author GotLiveChat
        Originally Posted by d3xt3r View Post

        Hi Guys,

        Thanks for all the replies. We're talking about hundreds of files here, so moving them back unfortunately is not an option. I agree a 301 is the best way to handle this. I guess if there's no way to do it in IIS directly I'll have to loop into an ASP solution.
        Have you logged into the IIS Admin console, selected the web site in question, select PROPERTIES and see the redirection options within that app? From what I've seen online you can also do 301 redirects within the console app but it's possibly for the entire site and not just a specified number of pages.
        But check the properties of the site and see what redirect options are available as it would definitely be easier than re-creating hundreds of asp 301 pages...
        {{ DiscussionBoard.errors[3429766].message }}
  • Profile picture of the author herry
    301 redirect is the most efficient and Search engine optimization method for webpage redirection. It's not that hard to implement and it should preserve your search engine rankings for that particular page. If you have to change file names or move pages around, it's the safest option. The code "301" is interpreted as "moved permanently".
    {{ DiscussionBoard.errors[3420772].message }}
  • Profile picture of the author GotLiveChat
    Are the non-existent pages really somewhere else on your client's web server? Or were they just removed due to not being needed? If you leave them as 404 then eventually Google will pick up on the 404s and remove them from their DB. If they need 301 redirects, create each pagename.asp then use
    <@ Language=VBScript %>
    <%
    Response.Status="301 Moved Permanently" Response.AddHeader "Location",
    "newpagesite.asp"
    %>
    changing location to the actual current page locale.
    {{ DiscussionBoard.errors[3424210].message }}

Trending Topics