1

I have an old website that hasn't gotten much love over the years and that's about to change. The existing site is based on a 3.* version of an ASP.NET portal framework called DotNetNuke (DNN).

I'm going to pull that site down and bring up a new site based on a static site generator called Nanoc (Ruby based). I'll be serving the site with nginx.

I'm not sure how to go about redirecting the old pages on the new site. Many of the new pages will be completely new; several of the old pages will not be back up. I suspect there will be a few that I'll want to keep alive in some form, but certainly not with the same urls.

Should I be concerned with doing a fine grained redirect on each of the pages on the site (it's not a large site), or just handle it with a general redirect?

wchrisjohnson
  • 190
  • 12
  • I don't know how to do Response.Redirect() after setting Response Code to 301, but you'll be wanting a 301 (permanent) rather than a 302. – Brian Webster Jul 19 '11 at 04:07

1 Answers1

0

You only need to bother with 301's (permanent redirect, better than 302) on links you want search engines to know changed, or if people might have them bookmarked. Other than that, I would just redirect 404's that look like an old URL to your new home page.

dahlbyk
  • 75,175
  • 8
  • 100
  • 122