Search

Kentico CMS 4.1 for ASP.Net was recently released. Kentico, the software vendor, announced that this version of the CMS contains a new enterprise-class search engine and several usability improvements.

The new search engine is based on the Lucene.NET search engine which is already known to provide excellent performance and search results. The new Smart Engine can be used side-by-side with existing SQL-based search engine. The main features of Kentico's search engine includes:

Yesterday afternoon Google announced at their Webmaster Central Blog that Google is changing the architecture of its search engine. These changes are expected to improve the speed, accuracy, and completeness of the Google search engine. Better yet, the prototype for the enhanced search engine is available for public testing.

For the last several months, a large team of Googlers has been working on a secret project: a next-generation architecture for Google's web search. It's the first step in a process that will let us push the envelope on size, indexing speed, accuracy, comprehensiveness and other dimensions. The new infrastructure sits "under the hood" of Google's search engine, which means that most users won't notice a difference in search results. But web developers and power searchers might notice a few differences, so we're opening up a web developer preview to collect feedback.

Some parts of this system aren't completely finished yet, so we'd welcome feedback on any issues you see. We invite you to visit the web developer preview of Google's new infrastructure at [link broken] and try searches there.

When first using Microsoft's new Bing search engine one of the surprises for me was the speed in which the results were delivered. I suspect that it's probably no coincidence that as competition heats up Google now sees a need to improve the infrastructure for delivering search results to its users. Whatever the reason, I'm happy to see that changes are coming.

I also have to admit that I get a secret pleasure in knowing that changes with Google's search engine will put those search engine optimization (SEO) folks on even shakier ground. These are the folks that claim for a price they can put your website pages on top of Google's index pages. As you can tell from my tone, I'm not a big believer in SEO. I'm a big believer that writing good content on your site is the only search engine optimization you ever really need. Hopefully Google's new search engine will continue to prove my point.

The Blog Herald has posted an interesting piece on an unannounced change in WordPress 2.8. Basically, Wordpress no longer notifies other servers of your updated articles at the same time you post those articles.

A couple days ago, Acquia moved Acquia Search out of beta and made it available commercially available through their Acquia Network service. Acquia Search is a hosted search service based on the Software as a Service (SaaS) model. The technology supporting Acquia Search is based on the the Open Source Lucene and Solr distributions from the Apache project.  While a free search module is already available in Drupal, as well as Acquia Drupal, Acquia Search is significantly different and geared toward the enterprise. Smaller but high traffic websites would also benefit from Acquia Search.

CMS Report has been beta testing Acquia Search for the past four months and we've had nothing but a positive experience with the service. In fact I feel as a beta tester I somehow didn't do my job since I didn't have any issues to report to Acquia. However, Acquia did acquire various usage statistics, email exchanges, and surveys from us that they still benefited from CMSReport.com's participation in the beta program. Since I know only enough about Drupal to be dangerous, if I can't break it then Acquia must be on the right track with this product.

Acquia used the first day of DrupalCon DC as well as their corporate site to announce the availability of their new service via a public beta program, Acquia Search. Acquia Search is "based on the powerful Lucene and Solr technologies from the Apache project" and "creates a rich index of your site content".  While Apache Lucene and Apache Solr are "free" and open source, the implementation and maintenance of these products can be rather daunting.  Acquia wishes to solve this complexity problem by offering Solr search as a service in their Acquia Network.

Before the beta was available to the public, CMSReport.com was invited by Jacob Singh to join the private beta program to test and review Acquia Search. I have only been using Acquia Search for a week so I still have some learning to do in order to take full advantage of the advanced configuration options in Apache Solr.  Although I'm new to Apache Solr,  I have to say that from a website owner's perspective the implementation of Apache Search was extremely easy.  After I signed up for the service on the network, implementing Acquia Search within the Acquia Drupal CMS was just a matter of activating the appropriate modules and waiting for my content to be indexed by the server.  Acquia Search works straight "out of the box" and I couldn't have asked for anything simpler.

I'm not a huge fan of creating sites with Adobe's Flash.  I personally find Flash sites difficult to navigate, bookmark, and retrieve worthwhile information.  However, I can understand why the more artistic Web designers and site owners out there prefer to use Flash when building a website.  But in my mind, one of the biggest drawbacks with Flash is that Google and other search engines have a difficult time reading and indexing Flash sites.  Let's face it, if Google can't search your site then it is highly unlikely your customers will find your site in the first few pages displayed by Google no matter which keywords are being used.

A few months ago I came across Alexa Web Search for the very first time. Alexa not only offers the usual search engine features, but also additional site statistics dealing with traffic ranking. Naturally, I entered my own site into the rankings to see what I could find. Considering my site has been around for only six months I was impressed that I had a traffic rank under 300,000.

Considering that there are nearly 50 million sites presently on the Internet, a site ranking under half a million is pretty good in my book. I had heard that sites using the Drupal content management system ranked well with the various search engines so I was pleased I chose Drupal for my site. All and all, those first few moments visiting Alexa were spent patting myself on the back for a job well done.

Then to my surprise I noticed that although I had typed in cmsreport.com, Alexa displayed uly.net. Uly.net was a domain I had never heard of before visiting Alexa.com. Worse, it appears that uly.net may have been benefiting from the traffic my site receives.

Traffic Rank for uly.net: 218,200

Where do people go on uly.net?

• cmsreport.com - 98%

Now some of you might be asking yourself, why do I really care how my site is ranked? I'd like to say, it really doesn't matter to me either since I do run this site for "fun". But, I have an ego. I do get a sense of pride for finally having a site where people actually show up and visit. Put it this way, when you host sites that rank above 2 million you feel somewhat rewarded to finally have a site with only six digits in its rank. More importantly, there is benefit to understanding how traffic rankings from sites such as Alexa, Google, and Technorati are being utilized.