September 25th, 2014, 09:42 AM
Changing file extensions - breaking links
We have been asked to rework a biggish website (about 30 000 static .html pages). The site is template based - on an old Microsoft template technology called .dwt (Dynamic Web Template) To cut a long story short, we are having to move away from this and we are re-thinking how best to apply new and more modern template offerings on the site. We generally use ASP.Net Masterpages as our template base on all our new sites - and where this would be fairly easily done in this case, one major issue is that all text files in the site would have to change file extension from .html to .aspx. This is a massive concern for our client as all the text files are professional documents acquired over the last 15 years and all of which have been cross-referenced from many other professional journals and web sites - so changing file names is a virtual no-no.
Does anyone have any ideas how to possibly get around this?
September 25th, 2014, 05:05 PM
URL rewriting. Make every *.html request redirect to *.aspx: the old links will still work and they'll redirect the user to the new location. Then Google and other search engines will (slowly) stop sending people to the .html pages but to the .aspx pages instead.