4 replies to this topic

[scribnar]

Hi,
We have a ASP.NET project created which is installed in a virtual directory of IIS.
Lets say the domain name is www.xxxyyy.com and the virtual directory is trial.
when the users type the domain name or come from any search engine, we have a default.htm page which has meta tags and javascript code to redirect the user to, www.xxxyyy.com/trial vritual direcotry.

The problem with this approach is, the search eignines[Spiders] ignores the sites doing this. So, we have decided to host the site in the IIS root instead of the virtual direcory we have. thus, the search engines does not ignore the pages in the site. Does any one know how to get the spiders still work having the system hosted at a virtual directory in IIS?

PS: We are not going to use the FORWARD meta tag. Since, the pages using this tag are completely ignored by the search engines. Frames are also not going to be used.

Any help will be greatly appreciated.
Thanks in advance!

[Jill]

Welcome scribnar!

I've moved this to the Technology and Coding area of the forum as you will be more apt to get some answers in this section for your question.

Good luck!

Jill

[qwerty]

You can use the management console snap-in to set up any page as the domain's default. I'm not certain whether that page can be located somewhere other than the root directory, but I don't see why not.

The result of setting things up that way is that when a user goes to www.xxxyyy.com they will get www.xxxyyy.com/trial/default.htm (or whatever page in the virtual directory you'd previously been redirecting to), but the browser's address bar will still read www.xxxyyy.com, just as it would if the default document were www.xxxyyy.com/default.htm. That's difference #1. Difference number 2 is that this is not a redirect and doesn't require metas and scripts.

At least I think so...

[Randy]

Welcome Scribnar !

Have you considered use a 301 Permanent Redirect to send visitors and spiders alike to your virtual directory location?

I'm not an IIS guru by any stretch of the imagination, however I know you can configure IIS to do this if you have admin privleges. If you do have Admin access the steps for setting up a 301 at the server level goes something like:

• Launch your IIS Manager.
• Right click on your default.htm file that you want redirected.
• Select Properties.
• In the "File" tab select A redirection to a URL and enter the destination you want everything redirected to.
• Select A permanent redirection for this resource.
• Click on the Apply button.

If you don't have Admin access you can also ask your host to set up the redirect for you. Assuming it won't be changing often they'll generally do this for you.

You can also use ASP to redirect from the normal default file to your virtual location. There are some posts around here somewhere that give you the code to do that. You can either do a search for those or wait for one of the resident ASP code-junkies to stop by and reply here.

[scribnar]

Thanks randy and qwerty for your suggestions. Thanks jill for moving my post to the right place.

1. I don't want to use permanant redirection. [ I understand that the 301 Permanent Redirection is required to list the site in search engines if we're redirecting from root to virtual directory. ] The reason is that may be in the future we will decide to move to wwwroot instead of a virtual directory. So, i'm looking for a solution which does not involve permanant redirection.

2. IIS doesnot allow you to give a document as default, if it has paths in it.

3. When we use server side redirection [Not Permanant], regardless of whether asp redirection or IIS redirection, its a redirection for search engines. So, the site is ignored by search engines.

Interestingly, i found that if we have a page which does not need to be placed under virtual directory and has linkes to the default page in the virtual directory, then we can place that page under wwwroot. This way, when a user types the www.xxxyyy.com in addressbar or he comes from search engine, he will be shown the page we have placed under wwwroot. Since, that page has the link to default page under virtual directory, the search eignes will list the site. But, in my case, the default page shown under virtual directory can't be moved to wwwroot.

So, from your answers and what i have learnt, i feel that there is no way to have the system hosted at virtual directory level and have the search engines still work better. Most probably, i will move the site from virtual directory to wwwroot in IIS.

If anyone could still give me a solution, it would be great. FYI, the server is completly under my control and i can do anything. So please let me know, if there is any way to do so or if i have to simply go for placing the system directly under wwwroot.

Thanks Guys for your help.