Google

Google Panda Killed My Aggregation

During the Memorial weekend, I decided to pull the plug on the CMS related news feeds we were streaming into Planet CMS. One of CMS Report's biggest strengths has always been pointing people toward the right direction in their search for content management systems. Knowing that one site couldn't support all the stories that needed to be written about CMSs, we began to rely more heavily on using a news aggregator within our Drupal CMS to provide you the links and excerpts to articles written elsewhere. I did this all with good intentions, but Google apparently disagrees.

Open Source Meets Google Summer of Code 2012

Every year, I find it an honor when I'm asked by open source projects to announce that they have entered been accepted as mentoring organizations into Google's Summer of Code program. I'm a big advocate of college education and I also understand the importance of a summer job to keeping those college bills under control. Open source projects and the Google Summer of Code provides this opportinuty for upcoming software developers. The Summer of Code is a "global program sponsored by Google that offers post-secondary student developers ages 18 and older stipends to write code for various open source software projects".

Quoting IT: Guy Kawasaki on Google+

"I think it's easier to be a search engine adding social networking than a social network adding a search engine. Google is adding this social component to search. It totally makes sense. I think it's going to be a long time before people go to Facebook and type in "Hockey" to find the score for a game."

- Guy Kawasaki, Guy Kawasaki's Social Media Secret, Inc.com, February 28, 2012

CMS Report's Top Ten Content Management Stories of 2011

When I read the stories we post here at CMS Report, I am reminded how quickly the CMS market continues to evolve and mature. Every year, I worry that there is nothing "new" to write about in this information system niche only to have the developer, user, or owner of a CMS push another new story idea toward my screen. This time around when looking for the top ten content management stories of the year, I concluded we didn't have ten great CMS stories for 2011. Instead, I found more than two dozen great CMS stories for 2011.

Below are the top ten stories of 2011 that were posted here at CMSReport.com. The stories in this list are ranked based on the rate they were viewed since they first appeared at CMSReport.com.

Top Ten Content Management Stories of 2011

  1. The 2011 Open Source Awards
  2. Google+ first week of use review
  3. 10 New Content Management Systems via CMS Focus
  4. Another new term: Social Content Management
  5. CMS Expo 2011 Series
  6. Liferay Marketplace and Liferay Portal 6.1
  7. CMS Redefined: Cloud. Mobile. Social
  8. CMS Report upgrades to Drupal 7
  9. DotNetNuke, Drupal, Liferay, and SharePoint in Gartner's Magic Quadrant for Horizontal Portals
  10. CMS in the Fast Lane: Joomla! 1.7

CMS Report's Top Ten Stories of 2009

The level of interest in content management systems astounds me. Each year, I continue to see at CMS Report an increase of visitors looking for information on content management. Our stories tend to focus on open source CMS more than proprietary applications and evidently that's the subject matter that our readers want to read.

Below are the top ten stories of 2009 that were posted here at CMSReport.com. As you can see, stories involving Drupal, WordPress, Joomla!, Alfresco, and Nuxeo took center stage. These stories might not have been the ten I would have personally picked for this list, but I'll respect the numbers behind their ranking.

  1. Mollom: A solution for comment spam
  2. 2009 Best Open Source PHP CMS: Drupal wins, Wordpress and Joomla! not far behind
  3. Serving a home for my Drupal site
  4. WordPress leads the Packt as 2009 Overall Best Open Source CMS
  5. Allen Ellis: Why the Packt CMS Competition is Broken, and How to Fix It
  6. Google PageRank
  7. Alfresco Module Obtains U.S. DoD 5015.02 Records Management Certification
  8. Using Wordpress city saves $19,000
  9. Cheryl McKinnon, Nuxeo, and Open Source
  10. Drupal Gardens preview video by Acquia

The interest in Nuxeo took me by surprise and I'll be adding the CMS to my top 30 CMS Focus page as time allows. As always, our thanks to all those who continue to return to this site to read the stories, join in on the conversation, and even submit articles. As I've said before, I'm not sure we would be doing this if it wasn't for the interest shown by others visiting the site.

Google PageRank

CMS Wire's Barb Mosher reported about a forum posting by a Google Employee explaining why PageRank has been dropped from the Google Webmaster Tools. Barb writes:

Do you constantly watch the Google toolbar in your browser to see if your Google PageRank has changed? Do you worry constantly about why your rank is less than that of a competitor? Well, there may not be any reason to worry any longer.

Google has dropped PageRank data from Webmaster Tools.

Google has for some time discussed that PageRank is a very small factor among many factors that they look at for placing a particular indexed page on a search results page. Dropping PageRank from the Webmaster Tools appears to be just one more step in moving PageRank away from everyone's attention.

We've been telling people for a long time that they shouldn't focus on PageRank so much; many site owners seem to think it's the most important metric for them to track, which is simply not true. We removed it because we felt it was silly to tell people not to think about it, but then to show them the data, implying that they should look at it. :-)

I have observed that indeed PageRank doesn't matter for placement on Google's search pages. I've seen CMSReport.com's front page ranked from as low as "3" to as high as "7" over the years. Although the page rank has varied over time, the placement of my web pages on the search pages have stayed about the same. Relevancy of the page to the search terms being used seems to have a much greater impact on how well your site ranks with the search engine. Additional details on why Google doesn't see PageRank as a good measurement for a site can be found on one of their Webmaster FAQ.

Opening up with SharePoint and Google Sites

Barb Mosher has written a great summary at CMS Wire on Google's new Sites API which allows content owners to move content in and out Google Sites. As Mosher points out, this new API and some additional tools will allow content owners to "pull stuff out of SharePoint and place it into Google Sites" which is sure to bring "real heat between Redmond and Mountain View" in their quest for customers.

Until now, content and data inside Google Sites stayed inside Google Sites. And there was no easy way to migrate additional content and data into it. With the introduction of the Google Sites Data API, that has changed.

The API support almost all of the functionality currently available within Google Sites including:

  • Retrieve, create, modify, and delete pages and content.
  • Upload/download attachments.
  • Review the revision history across a site.
  • Display recent user activity.

Which brings us to the point. With these new capabilities, you can now not only move data out of Google Sites, but you can move data into Google Sites and possibly out of other similar applications, like SharePoint.

Whether Google Sites and the new API will be a threat to Microsoft and SharePoint is questionable. But, once again I think these type of events emphasize that those content management systems that get the most attention from us these days are those applications that open up and work with other third party applications.

There is a reason why such topics as CMIS, open source, and API are in the spotlight with folks interested in content management. No one really wants to be stuck with a vendor that doesn't play well with others. It just strategically isn't a good idea to have your content controlled by a single vendor, so why do it? I suppose I'm rhetorically asking that question to both customers and vendors. 

Google for the Next Generation

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.