Hey guys,

I am confident that there is an easy, clean way to do this, but I am currently stuck.

I have an old site that I rebuilt in DNN.  The domain name is the same, but obviously the page URLs are different between the site.  My new site works fine, but all the SEO we did on our old site is useless because the links in google (and other search engines) point to the old URL.

Is there a clean way to handle this?  Here is an example of what I want to do...

(Keep in mind that the base domain is the same, but I simply pointed the domain away from our old site to the new DNN site we built.)

The google search on our key words return the link:
http://mydomain.com/Products/Semina...aspx?ID=48
...but the actually link is now
http://mydomain.com/Default.aspx?TabID=130

I tried playing with the siteurls.config file, but I could have my regular expressions mixed up.

Any ideas?  I need to make sure about 7-8 of these old links now point to the proper place in my new DNN site.  Any help would be appreciated.

You might see if Ifinity's URL rewriter product will do the job for you.

Also, check out Tom Kraak's seablick.com site and blog. He has some good SEO tips there.

Joe,

Thanks for the reply, but I found my work around.  I was overlooking the obvious as I was not simply leveraging 301 redirects.

I am posting this for anyone else who runs into this issue when they convert from on old site to their new DNN site and are concerned about their old links in google and other search engines.

I had old links such as:

http://domain/Products/EventsAndProducts.aspx?ID=21
http://domain/Products/EventsAndProducts.aspx?ID=9
http://domain/Products/EventsAndProducts.aspx?ID=32
http://domain/Testimonials/Testimonial.aspx
http://domain/Testimonials/Testimonial.aspx?ID=11

All I did was create the Products folder and the Testimonials folder in my root folder, and added the respective aspx files in each (i.e. EventsAndProducts.aspx in Products, and Testimonial.aspx in Testimonials).

Here is an example of what the EventsAndProducts.aspx page would look like. Do not forget the "<" before the word script at the beginning and add you ending brackets and the end script tag at the end. Sorry, this is the only way I could get it to display in a way that would make sense:

script runat="server" language="c#" >
private void Page_Load(object sender, System.EventArgs e)
{
string pageid = Request.QueryString["ID"];
switch (pageid)
{
    case "9":
        Response.Status = "301 Moved Permanently";
        Response.AddHeader("Location","http://new target");
        break;
    case "21":
        Response.Status = "301 Moved Permanently";
        Response.AddHeader("Location","http://new target");
        break;
    case "32":
        Response.Status = "301 Moved Permanently";
        Response.AddHeader("Location","http://new target");
        break;
    default:
        Response.Status = "301 Moved Permanently";
        Response.AddHeader("Location","http://new target");break;
end bracket
end bracket
end script tag

Thank you for the details!

Glad you wrote about this jncraig, this is (IMO) an extremely important issue; one that gets overlooked far too many times by the general DNN community.

Question for you though; is there a reason you did the 301's through a script method, instead of doing it straight through IIS? (Steven Hargrove has a great how-to).

Or were you doing it this way because you don't have access to your hosting server's IIS?

Thanks for the crystal clear explanation!