I have a DNN2 site that has pretty good search engine rankings. I would like to rebuild it using DNN4.
Here's my issue:
On the live DNN2 site I have links to pages like this: http://www.mydnn2.com/Default.aspx?tabid=1 (this is the home tab).
On
the DNN4 site the Home page is tabid 36 - and when I type
http://www.mydnn4.com/Default.aspx?tabid=1 in my address bar, DNN4
nicely ignores the query params (there is no tabid 1 in the database)
and just directs me to http://www.mydnn4.com/.
This is great.
Except what happens if I have a tabid 36 on the DNN2 site with content
such as "About our company"? I would like the new DNN4 site to
implement
301 redirects for URL's that existed on the
DNN2 site, but do not have the same URL on the DNN4 site. 301
redirects ensure that pages indexed by search engine crawlers will
still retain there relevance.
I have found some good, simple solutions for implementing a redirect programmatically (
see the blog on ventrian.com). But I'm not sure how to solve the problem of overlapping tabid's.
Can
I change the tabid on the DNN4 site that conflicts with the DNN2 site?
For example, can I go into the database and change all instances of
tabid=36 to tabid=360?
If I can do this, my plan is to create
pages on the DNN4 site that have tabid's corresponding to tabid's on
the DNN2 site - then use the 301 redirect code to redirect to the
correct content (for example, send tabid=1 to tabid=360).
(I also posted this question in Scott McCulloch's forum on
ventrian.com)