Casey Dougall wrote: > > Be careful of wildcard settings on your sites. Yeah it's cool but Search > Engins do not like it at all. The problem stems from Google, yahoo etc > thinking there are more than one website with the exact same content. This > of course means when someone goes to domain1.thedomain.com or > domain2.thedomain.com they view the same index.cfm page as > domain3.thedomain.com.
That doesn't really apply if you're using host headers. So "domain1.domain.com" and "domain2.domain.com" are completely different sites - even if they're running the same CFML code base. I can do this with BlogCFM - a single code base installed in a single web site can run multiple blogs (from a single database), where each blog has its own template and its own content - all based on CGI.HTTP_HOST. I could have a DNS wildcard set for *.myblogdomain.com, and have 3 different blogs, blog1.myblogdomain.com, blog2.myblogdomain.com and blog3.myblogdomain.com All running the same virtual host / web server. > Now of course if you use some #CGI.SERVER_NAME# lookups first, then set the > content of index.cfm to match the domain in question you could be ok. Right, and I think that's what he's talking about doing. Of course, if we're just talking about the admin, then it doesn't matter cuz you don't need the admin login page showing up in google anyway :) Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262614 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
