This is the Link Report for August 11th through August 12th:
Please feel free to post your thoughts in the comment section below
- The Top 12 Options for Web Content Management – ReadWriteEnterprise – This annual report identifies the leaders in the industry of Web Content Management.
- Interactive online Google tutorial and references – Google Guide – Google Guide is an online interactive tutorial and reference for experienced users, novices, and everyone in between.
- Official Google Webmaster Central Blog: New tools for Google Services for Websites – A good way to add Google services to your site
- Official Google Webmaster Central Blog: Optimize your crawling & indexing – Google slideshow and post about how to optimize your url structure for optimal indexing
- Facebook Search vs Twitter Search – Side by Side Comparison | Ignite Social Media – As most fellow geeks are aware of Facebook announced the purchase of real time microblogging platform Friendfeed yesterday. Without any delay they then announced later that night that users will now be able to search across peoples profiles and wall postings, something that has never been possible before. This opens up a whole new can of worms and it remains to be seen how well this search feature is adopted and what changes Facebook continues to make to the underlying platform that they have now integrated from Friendfeed.
- How will your site rank with Google Caffeine? | Blog | Econsultancy – When Google updates, SEOs around the world hold their breath. For websites that rely heavily on their Google SERPs for traffic, an algorithm change can sometimes mean the difference between profitability and the poorhouse.
- Official Google Webmaster Central Blog: Help test some next-generation infrastructure – 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.
- Caffeine: It’s Google On Red Bull, Or Something – washingtonpost.com – But today, the company has begun testing a new engine for its search product that's a big enough change that it felt compelled to let the world know about it. Codenamed "Caffeine", it promises to "push the envelope on size, indexing speed, accuracy, comprehensiveness and other dimensions."
The test, available here: https://www2.sandbox.google.com/, really doesn't look any different at first glance. And Google notes as much, saying that these changes are primarily under the hood. When you hear that, most people will probably assume this means speed in showing results.
- Caffeine: Google’s New Search Index – Google has just unveiled a “secret project” of “next-generation architecture for Google’s web search“. This new architecture appears to include crawling, indexing, and ranking changes. For the first time, Google isn’t simply incorporating these changes into their existing infrastructure or replacing it. Instead, they’re providing a developer preview and are asking webmasters and power searchers to try it out and give them feedback. Unlike Google’s now-defunct SearchMash, which was intended for search experiments that wouldn’t necessarily be incorporated into Google’s main web search, the caffeine index seems to be an entirely new search infrastructure that will repace what exists now.
- More info on the Caffeine Update – Google recently opened up a preview of our new Caffeine update, and I wanted to give a little more background on this change. At the Real-Time CrunchUp a few weeks ago, I joked that the half-life of code at Google is about six months. That means that you can write some code and when you circle back around in six months, about half of that code has been replaced with better abstractions or cleaner infrastructure. Six months is an exaggeration, but Google is quite serious about scrutinizing our codebase regularly and rewriting the parts that don’t scale well to make them more robust, more elegant, or faster.