Welcome to WebmasterWorld Guest from

Forum Moderators: Ocean10000 & incrediBILL & phranque

Message Too Old, No Replies

httpd.conf issue for virtual hosts

also is 301 redirect from non www to www bad?



1:27 am on Jan 18, 2006 (gmt 0)

5+ Year Member

I am having a bit of trouble getting indexed in Google. I saw today that my splash page was indexed and only an hour later it was gone. I decidided to investigate why Google may have pulled it and during my investigation I noticed that the non www version of my site was pulling up the first site in the list of my name based sites in my httpd.conf which was not the site that it was supposed to pull up. Anybody know why this is? I then changed the order of my virtual sites in httpd.conf and sure enough, it pulled the one from the top of the order. Now that I placed the site that I am trying to promote at the top of the virtual hosts order and changed the servername directive inside the site's virtual host settings it pulls up the same site for both non www and www but it doesnt do this for other virtual sites...only the one at the top of the order.

My redirect question is that I keep reading that google will penalize you for duplicate content if your www and non www sites are the same because they are seen as subdirectories and that makes sense I suppose but then I went to google and ran some tests. Every search that I did, no matter what the keywords were, the top listings always have both a www and non www that are identical and non of them were using redirects. I even went so far as to check their header output and there were no 301 redirects in there for any of the top sites. So is redirecting non www to www good or bad...and if its good then why are such a high percentage of top listings not using it.



1:30 am on Jan 18, 2006 (gmt 0)

10+ Year Member

This recent thread might help answer the first question.



1:51 am on Jan 18, 2006 (gmt 0)

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member


Welcome to WebmasterWorld!

If you have not defined ServerAliases for the non-www ServerName entries or vice-versa, then the server will default to the first VirualHost it finds, as documented.

A 301 redirect from www to non-www or vice-versa is recommended. This prevents multiple 'versions' of your URL from being linked-to by other webmasters, solidifies your site's 'branding' under one domain or the other, and prevents your PageRank and/or linkpop from being 'diluted' across two different domains.

I said two different domains; The major search engines will 'figure out' that these two domains resolve to the same content eventually, but then you are deopending on their back-end processing to do so. IMHO, it's better to just tell them up-front, and not rely on them taking the time to canonocalize your domain for you. This will make your ranking less 'fragile' IMO.

The top sites you saw may be succeeding in spite of these canonicalization problems. Try entering google.com in your address bar, though. Google thinks it's important. Instead of checking the 600-pound gorillas in whatever market segment you investigated, take a look at the smaller up-and-coming sites below them. Those that seem to be performing above their potential may indeed have all their server-side details in place.

Note that above, I didn't use the word 'penalty.' Webmasters see penalties in every dark doorway, and in some cases, invent them to compensate for poor SEO, design, or usability of their sites. In that regard, a warning: Users generally don't like their time being wasted with 'splash pages.' And if your splash page is done in Flash, your site won't perform in search unless you also provide lots of text for search engines to chew on.

This can be done on the same page, or you can 'cloak' for search engines. If you do that, though, make absolutely sure that your non-Flash page is usable by humans, and that it contains absolutely the same content as delivered in Flash -- No more, no less. In this way it is cloaking, but cloaking with no intent to deceive. If you wish to pursue this subject further, I'd recommend getting a 'second opinion' in some of our other forums here -- I'm far more comfortable discussing Apache that SEO for splash pages... :)



2:35 am on Jan 18, 2006 (gmt 0)

5+ Year Member

Thanks to both of you for your quick replies. I found the information very informative.


Is it safe to say by your statements that you do not recommend serveralias directives to non www and www but rather www only and a 301 redirect from non www to www?



3:52 am on Jan 18, 2006 (gmt 0)

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member

If you use a serveralias, you just have make sure the redirect is activated when that alias is requested. It doesn't really matter whether you resolve both names to the same server and then redirect based on the requested hostname, or resolve the non-prefered domain to a separate host, and redirect from there -- largely a matter of you preference for now and for future plans.



Featured Threads

Hot Threads This Week

Hot Threads This Month