Here is a recap of what happened in the search forums today, through the eyes of the Search Engine Roundtable and other search forums on the web.
Here is a recap of what happened in the search forums today, through the eyes of the Search Engine Roundtable and other search forums on the web.
Friday, I reported that there was a possible Google update taking place. Truth be told, it was actually webmasters hitting on the data center which showed the Google Caffeine results.
Matt Cutts of Google confirmed that Caffeine was going live on 209.85.225.103, at least for 50% of the users hitting that data center. He also said that I was totally off in reporting that Google is doing a major update - they are not. What people are seeing is the Caffeine results on that single data center.
Google did tell us that they would not fully launch Caffeine until after the holiday season. In fact, they promised to launch Caffeine on a single data center, and this is what they did.
So the update is not a full update, just a Caffeine update on a single Google data center that should not have a huge impact on online retailers during this holiday season.
I should clarify that my post on Friday did actually say that this can be that Caffeine was live on a single data center and those reporting the update was indeed only looking at the data center. In any event, Caffeine is now live on that single data center (at least 50% of the time), so check it out at 209.85.225.103.
Forum discussion at DigitalPoint Forums, Google Webmaster Help and WebmasterWorld.
If you are a patent junky, then you may like this relatively new one. A patent application submitted November 19th by Google named artificial anchor for a document may shed some light on the jump down Google snippets or anchor based Google Sitelinks we have seen creep into the Google search results in August and September.
As always, Bill Slawski converts the patent into English for all of us to read. But here is the abstract:
Methods, systems, and apparatus, including computer program products, for linking to an intra-document portion of a target document includes receiving an address for a target document identified by a search engine in response to a query, the target document including query-relevant text that identifies an intra-document portion of the target document, the intra-document portion including the query relevant text. An artificial anchor is generated, the artificial anchor corresponding to the intra-document portion. The artificial anchor is appended the address.
Currently, I am way too tired to look into this right now, so just hit the thread at WebmasterWorld to dig deeper.
Forum discussion at WebmasterWorld.