Welcome to WebmasterWorld Guest from 188.8.131.52
Site hosted on IIS server, what is the best way of doing 301 redirect from asp page to html? I am not sure whether client has got access to IIS Manager.
Don't use the removal tool. Especially don't use it on your homepage.
Get a lot of new links to the pages that have a new extension name.
Submitting Option 1: Do nothing, Google will pick up the changes (my preference)
Option 2: Do a sitemap and submit after you've made the changes.
I did it a couple of years ago. My isp helped me set up comprehensive 301 redirects but it didn't make any difference. I disappeared off the face of the earth... according to Google, and didn't begin to recover for over 12 months.
(of course Big Daddy probably didn't help either!)
Yahoo, on the other hand, took the change in its stride.
Block googlebot from the old domain with robots.txt to avoid duplicate problems.
The indexed content pages will be there in Google cache, I doubt blocking pages of old domain in robot.txt will resolve the duplicate content issue, will it?
I've done it - it worked, and it's also supposed to work. Yes, Google keeps a copy of a previously cached document "somewhere" or other, but the robots.txt blocked domain will get removed from active scoring.
How about blocking overall old asp pages in robot.txt file for the current scenario.
Just because you change the technology that runs the website, that does not mean that any of the URLs visible to the public have to change.
You can leave the URLs as .asp even though there is no ASP code within those pages.
Alternatively, you can use an internal rewrite so that when a URL with .asp is requested, the server sends the correct .htm page, but does so with a 200 OK status code and does NOT redirect to the .htm URL.
You didn't say if you were moving away from using asp as your server technology, but you can also set the .html extension to be processed by the asp engine so you don't lose any asp functionality even on the .html pages.
I've used both of the above techniques on many sites and I've never had a problem, and you don't need any 3rd party components to utilize them.
I setup the original site in a development environment. I built a 2nd site who's whole purpose was to walk through the sitemap and scrape the 1st site and put it into html files in a directory to upload.
I then made wrote small asp page stubs for each original page to provide 301's.
Made a sitemap with the new pages.
I didn't lose any rank.
Client wants it to be static html pages, as it is somewhat difficult for me using rewrite engines cause I haven't done this previously, as for as I feel it will be good to keep the existing asp pages with 301 redirecting to the respective html page till the Search engines find the html pages, once html pages are been indexed, deleting those old asp pages will not hurt the ranking I guess.
deleting those old asp pages will not hurt the ranking I guess
You will loose your PR. It is advisable to keep your redirects for as long as you can.
How long to keep 301 redirect [webmasterworld.com]
I'm with the others... A link is forever, not just for Christmas.
Certainly a month is nowhere near long enough. ... But I'd leave it there for a long long time.