Jump to content

Cre8asiteforums

Discussing Web Design & Marketing Since 1998

  • Announcements

    • cre8pc

      Thank you! Cre8asiteforums 1998 - 2018   01/18/2018

      Internet Marketing Ninjas released many of the online forums they had acquired, such as WebmasterWorld, SEOChat, several DevShed properties and these forums back to their founders. You will notice a new user interface for Cre8asiteforums, the software was upgraded, and it was moved to a new server. Thank you for your support as we turn 20 years old.  
Sign in to follow this  
glyn

Forcing Http Not Www

Recommended Posts

I have a client that is indexed under http://domain.com. I think it looks quite nice in the listings like this. However, I can also see that the domain is accessible under www.domain.com, when running some spiders over the site.

 

I've never really thought of the difference of going to other way, forcing the webserver to redirect all www requests to http://.

 

Is there any reason why I would not want to do this and force instead www in requests?

 

Glyn.

Share this post


Link to post
Share on other sites

I have two domains with www. They were started by me a long time ago when everyone did that.

 

In about 2005 I realized that going without the www gave an important domain better visibility in the SERPs and made it easier for people to "get it". So, from then on all of my domains have not used www.

 

I did not redirect the www domains in the past because I worried about linkjuice being lost from all of the old links. Within the past couple of years Google has claimed that no linkjuice is lost in a redirect. So, after thinking about your question, I might redirect them and get rid of the www.

Share this post


Link to post
Share on other sites

It does look nicer especially with your name as a domain name. I do the same thing (non-www). I prefer it.

 

Had not considered the visibility in the SERPS. Did not know this.

 

In the "get it" department, it sounds clearer in speech instead of stuttering W-W-W. Go to thisdomain dot com instead of w-w-w dot thisdomain dot com

Share this post


Link to post
Share on other sites

Is there any technical challenges in preferencing http over www? Maybe we have a server head in the house?

Share this post


Link to post
Share on other sites
Is there any technical challenges in preferencing http over www?

I'm not sure what that means but will presume it means how is www->non or non->www done. And I presume an Apache server.

 

The first is www->non. I'm not sure if the ,L is needed but I usually have it in.

RewriteEngine OnRewriteCond %{HTTP_HOST} ^www.this\.com [nc]RewriteRule (.*) http://this.com/ [R=301,L]
RewriteEngine OnRewriteCond %{HTTP_HOST} ^this\.com [nc]RewriteRule (.*) http://www.this.com/ [R=301,L]
Edited by bobbb
  • Like 1

Share this post


Link to post
Share on other sites

And I also forgot to mention this goes into (near the top) of the .htaccess file in the root directory of the server.

 

I'm also making the assumption that your DNS entries for the domain point both the domain and the www sub-domain (standard practice) to the same IP.

Edited by bobbb

Share this post


Link to post
Share on other sites

Thanks, it was more about whether there was a technical server https reason not to.

Share this post


Link to post
Share on other sites

Ah! I see what you mean. Like what domain the SSL certificate is valid for.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

×