• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 700
  • Last Modified:

How to properly do a 301 redirect for SEO?

We are implementing a new website.  We will be switching web servers when we go live.
So, right now, I have the page example.com/example old 1.htm on the server #1, which I want to redirect to server #2 and the page of example.com/example NEW 1.aspx.

I have several hundred of these to setup, and am trying to figure out if I need to actually copy the original page from the old server and web to the new server and new web?  I did one that way and setup the redirect in IIS by selecting the file, choosing "HTTP Redirect" and inputting the new URL, and it worked like a charm but didnt' test perfectly on some online redirect testers.... However, I want to keep things simple in the file structure of the new website if possible and I don't want all my old web pages in there (even though they'd be redirected and innaccessible).

So, I setup a new record in the "Web.Config" file without physically moving the corresponding file from the old site to the new site and it was:
<location path="ABOUT US.htm">
        <system.webServer>
            <httpRedirect enabled="true" destination="/t-about.aspx" exactDestination="true" childOnly="true" httpResponseStatus="Permanent" />
        </system.webServer>
    </location>

This correctly redirected the file from the old one to the new one, but it won't register as a 301 redirect in any online redirect testers I try because my old website is a domain name right now and the new one is simply an IP Address for testing.

Does only using the Web.Config not register as an SEO friendly redirect because of the IP Address deal, did I do something wrong, or does the "About Us.htm" old file actually physically have to also be in the new site and be redirected?


Thanks for any help anyone provides!
0
ausman89
Asked:
ausman89
1 Solution
 
RovastarCommented:
"This correctly redirected the file from the old one to the new one, but it won't register as a 301 redirect " 

What did it do then?

A 302?! You imply it redirected - how did it do this?

Also I would look at using URLrewrite module in IIS7.5 for this it  might make it easier.

0
 
ausman89Author Commented:
So I was getting a 400 bad request when I only added the code the web.config file and not directly adding the file from the old web to the new web.

The URL had a space in it, and as soon as I fill that space with a "%20" the redirect link testers online are all recognizing the redirects as 301 redirects.

Do you think Google will be smart enough to figure this out and not view it as a 400 bad request, but view it as a correct 301 redirect?  
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now