Hacked, then rehacked, now static... and what about Google?

[rogerRoger]

We have an old classic ASP app that has recently been hacked, and then we published again... and it got hacked again... So, we've run a utility to convert all of our ASP pages to static HTML, as a temporary solution, so that visitors can still find the site information, until we're able to harden up the ASP code.

We expect the hardened site to be back up within 2 weeks, but what about Google. We've worked long and hard to get the placement we have now, how can we post these new static pages, with different urls, and then expect Google to come back and find the ASP urls later?

1. Should we just live with the pain and let Google get confused?
2. Place a robots.txt file blocking Google, Then open the site back up when the old site is back online?
3. Your suggestion goes here - and thank you!

[JohnW]

Why woud you want the URIs to be different? This would cause unnecessary trouble. Just simply hardcode the html so the URIs are the same as the asp URIs.

If for some reason this cant be done you could use 302 redirects to point from each of the old pages to the new html page.

[rogerRoger]

The problem is that we have LOTS of pages (about 1000).

Thankfully, we've taken care of the problem. The old site used fairly generic urls (e.g. /Products/Product#), so we were able to match up the content URLs for 90% of the site without too much difficulty.

Thanks for the response!