Our client has an existing web site (their main one) which is set up as a custom-built web application (http://example.com). They are using Sitefinity for several of their other web properties (in a Multisite install), and they would like to start integrating their main site into this Sitefinity install -- in effect, migrating their main site over to Sitefinity piece by piece.
The first project to use Sitefinity is to expand their online magazine. To use their pre-existing SEO equity, they would like this site to be under their main domain as a subdirectory (http://example.com/magazine/). I had initially assumed that we could simply add the existing top-level domain to multisite install (http://example.com), create the pages in it, and then set up the a child application of the existing custom web application, pointing it at the Sitefinity multisite installation folder.
So, I would have:
and set up a site in Sitefinity with
- Magazine section one
- Magazine section two
and so on ...
Unfortunately, what ends up happening is that http://example.com/magazine/ resolves to the Home page, and not the Magazine page, and the Magazine page URL ends up being http://example.com/magazine/magazine
The only workaround I could come up with was to make the child application URL http://example.com/sf/ (so that the Magazine page URL is http://example.com/sf/magazine), and then use 301 redirects to send requests to the proper Magazine URL. However, I am dissatisfied with that solution. I am neither a server config expert nor a Sitefinity expert, so I was wondering if anyone had any ideas of how to set this up correctly.