Welcome to WebmasterWorld Guest from 34.238.194.166

Forum Moderators: phranque

Message Too Old, No Replies

301 redirect question?

     
1:43 am on Feb 8, 2006 (gmt 0)

New User

10+ Year Member

joined:Jan 8, 2005
posts:24
votes: 0


I am still trying to figure this one out.

My site shows up for the non www and the www.

When I check site: my site the two have a different numbers of pages in the search engines.

I want to redirect to the www site.

My hosting service told me that they have both the non and the www. at the DNS level redirecting to the same IP address.

They also told me to learn some asp to figure it out.

If anyone has a idea please make it simple step by step. It sounds like I just need to put a little code in a file.

Thanks

6:22 am on Feb 8, 2006 (gmt 0)

Administrator from JP 

WebmasterWorld Administrator bill is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Oct 12, 2000
posts:15150
votes: 170


It sounds like you have an IIS server, correct? If so my first advice to you would be to check through some of the threads here as we've had quite a few about 301 redirects for IIS [google.com].
2:35 pm on Feb 8, 2006 (gmt 0)

New User

10+ Year Member

joined:Jan 8, 2005
posts:24
votes: 0


I believe you are correct on the IIS server.

I have really been looking around the internet a lot and I have not found a clear cut example.

I am using Frontpage 2003 and I found some advice recommending not using FP extensions and creating a htaccess file with the standard few lines of code.

Any ideas on this?

9:14 pm on Feb 8, 2006 (gmt 0)

New User

10+ Year Member

joined:Jan 8, 2005
posts:24
votes: 0


They are telling me that it is being redirected at the DNS level and that there is no problem?
8:18 am on Feb 9, 2006 (gmt 0)

Administrator from JP 

WebmasterWorld Administrator bill is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Oct 12, 2000
posts:15150
votes: 170


You can't use an .htaccess file on an IIS server.

Normally you need to be able to access the IIS Manager on your hosting account to mess around with redirects. Another option would be to install something like ISAPI_Rewrite.

Have you checked the threads I linked to above?

7:20 pm on Feb 10, 2006 (gmt 0)

New User

10+ Year Member

joined:Jan 8, 2005
posts:24
votes: 0


I looked at the links and still don't have the answer. The hosting service is of no help and they say there is no problem.

Based on all that I have read, if both www and non www show up when I type them in a browser then I need to redirect.

The web site is in Frontpage and just html.

Do I need to think about moving this site and not using Frontpage extensions to fix this? Is it worth this much work?

Thanks

6:38 pm on Feb 11, 2006 (gmt 0)

Full Member

10+ Year Member

joined:July 11, 2003
posts:276
votes: 0


I too need to do the same thing for a FP ASP site on a windows server and the hosting company said the same thing but also that I needed to add scripting to the pages pointing them to where they need to re-direct. Looks like this is the one. [webmasterworld.com...] - see last post for asp script.
7:36 am on Feb 12, 2006 (gmt 0)

Administrator from JP 

WebmasterWorld Administrator bill is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Oct 12, 2000
posts:15150
votes: 170


This is a server issue. It doesn't matter if you have FrontPage or SharePoint or other extensions installed. The redirection settings are on the server level for IIS.

The link provided in msg #:13 of this thread: IIS 5.0 and 301 redirection [webmasterworld.com] will work.

12:09 am on Mar 10, 2006 (gmt 0)

Full Member

10+ Year Member

joined:Feb 21, 2002
posts:228
votes: 0


Are there any specific 301 redirect instructions for .NET server?
1:36 am on Mar 10, 2006 (gmt 0)

Full Member

10+ Year Member

joined:July 11, 2003
posts:276
votes: 0


I agree completely this is a server issue however some host just won't comply with the request to set it in the IIS Manager, and it is those cases we need another solution (or another host ;)).