Google's AP and AP Yandex

The current end of the month of March will be marked by two events: that's about to happen. Google up. and is likely to occur simultaneously with. TIC Yandex up.
And the first and the second event with the hope of thousands of people waiting for dealing with. SEO. and. earnings on the Internet. The same Apostle google is not so often, about 4 times a year, making this event quite welcome. In anticipation of his many contests SEOshniki ustarivayut guess who his date and t. n.
I also participated in one such contest but was able to guess just an issue of Yandex 24. 03 This update extradition remember many webmasters, the number of pages in the index and the position of the grant changed every few minutes, driving very far down the top issue, and vice versa in the top rising from the depths. It looked very specific and I think many SEO shnik his nails otgryzli watching it. In the talk. maul, it was the most discussed and the big topic of the day. Generally, as rumored guru, Yandex recently seeking work as well as Google gradually increasing the time between apami. there are the beginnings of processing in real time. That's the last issue of peretrubatsii reminded many. Google dance. (. Google Dance. ).

For those who do not know. Google Dance. - This is the chaotic change of PR pages, usually starting a few days before. Google's apa. The essence of the whole issue and ana a:.
Search engines are a complex of data centers. responsible for certain elements of the PS. On some servers, live Bystroboty who find current information and prepare notes for common bots that come with a full indexation after. There is also a subsystem is responsible for indexing previously indexed pages and update the cache subsystem is responsible for puzomerki.
During the issuance of these subsystems are ground. terabytes of information. While there is indexing across multiple servers appear different SAR values ​​puzomerok. That's what we see as. Google dance. or as it is now possible to call. Yandex -dance. :). By the end of issue all the values ​​of the information is synchronized on all servers and all resources will receive their portion of the new high or low puzomerok.