Welcome to the google dance

 

How to start

 

 

THE FIRST THINK YOU SHOULD DO

 

THE FIRST THINK YOU SHOULD DO

PICKING A DOMAIN NAME

I belive the first think is to pick the right domain to fit your chosen subject

Ok so you want to sell hosting well if you dont have a domain name do a search on sedo or some other forums or godady and see if there any that have expired as thes might still have traffic, When you find one and you will as there allways lots due to laze webmasters or people just for get.

Ok now you have a domain name ((hugehosting)) Now to make your web site it is best when makeing your web site not to use flash or do both one in flash and one in static as the spiders dont like flash that much and 50% of web surfers dont like it as well so that will mean lost traffic and lost sales.Now when laying out you site think how the robot will search your site(( from the top left and down so if possible add a site map link(( invisable to the surfers if you like)) and then the rest of your links try to keep dif keywords for each page so say 5 per page to start with and add so good content with those keywords in your title and in the discription of your site and on your index page (( get some good content with the keywords))

Ok now you have done your site now you can check how your site look by the bots((GOHERE))

Now you have done all this dont pay to submit any search engines you dont need to. go to google ((here)) and use this programe you will see your site will be index soon then some submitting to there google now go to this site and download there ((free tool))

Now you submit to 100s of engines and find link parnters that are in the field as you the best way to get links to have some think that other webmasters want to link to you with out you asking. Now go to stumble anda few othe socal networks and join and submit your site all so search for blogs about hosting and post some topic that fits with in the blog and post your link. add you sig in to your forum post and then go to of inline ads in mag and papers or do some flyers and pay some to post them for you.

Now you should be getting some nice traffic dont worry about alaxa rank as there only about 10 mill that have the tool insataled and is more of a guide all so dont worry about pr rank as it does not meany anythink if your site has pr 1 but get trafic then thats what you want not a pr 5 and no traffic ever now and then do a search for your keywords in in google and see where you come in the listing now when picking you keywords make sure the term that you use is not a high yeld ((seehere)) your see about 225,000,000 that alot and you prob wont get here the top so try some think like this ((seehere)) 2,170,000 now that better dont you think.

now the seo dance the google way yes there is a google dance it new but not dance the google way learn the steps be come a master of the google dance

The name "Google Dance" is often used to describe the index update of the Google search engine. Google's index update occurs on average once per month. It can be identified by significant movement in search results and especially by Google's cache of all indexed pages reflecting the status of Google's last spidering. But the update does not proceed as a switch from one index to another at one point in time. In fact, it takes several days to complete the index update. During this period, the old and the new index alternate on www.google.com. At an early stage, the results from the new index occur sporadically. But later on, they appear more frequently. Google dances.

Not only Google's index is spread over more than 10,000 servers, but also these servers are, as of now, placed in eight different data centers. These data centers are mainly located in the US (i.e. Santa Clara, California and Herndon, Virginia), indeed, in June 2002 Google's first European data center in Zurich, Switzerland went online. Very likely, there are more data centers to come, which will perhaps be spread over the whole world. However, in January and April 2003 Google has put two data centers on stream which are again located in the US.

In order to direct traffic to all these data centers, Google could thoeretically record all queries centrally and then send them to the data centers. But this would obviously be inefficient. In fact, each data center has its own IP address (numerical address on the internet) and the way these IP addresses are accessed is managed by the Domain Name System.

Basically, the DNS works like this: On the Internet, data transfers always take place in-between IP addresses. The information about which domain resolves to which IP address is provided by the name servers of the DNS. When a user enters a domain into his browser, a locally configured name server gets him the IP address for that domain by contacting the name server which is responsible for that domain. (The DNS is structured hierarchically. Illustrating the whole process would go beyond the scope of this paper.) The IP address is then cached by the name server, so that it is not necessary to contact the responsible name server each time a connection is built up to a domain.

The records for a domain at the responsible name server constitute for how long the record may be cached by a caching name server. This is the Time To Live (TTL) of a domain. As soon as the TTL expires, the caching name server has to fetch the record for a domain again from the responsible name server. Quite often, the TTL is set to one or more days. In contrast, the Time To Live of the domain www.google.com is only five minutes. So, a name server may only cache Google's IP address for five minutes and has then to look up the IP address again.

Each time, Google's name server is contacted, it sends back the IP address of only one data center. In this way, Google queries are always directed to different data centers by changing DNS records. On the one hand, the DNS records may be based on the load of the single data centers. In this way, Google would conduct a simple form of load balancing by its use of the DNS. On the other hand, the geographical location of a caching name server may influence how often it receives the single data centers' IP addresses. So, the distance for data transmissions can be reduced. In order to show the DNS records of the domain www.google.com, we present them here by the example of one caching name server.

How data centers, DNS and Google Dance are related, is easily answered. During the Google Dance, the data centers do not receive the new index at the same time. In fact, the new index is transferred to one data center after the other. When a user queries Google during the Google Dance, he may get the results from a data center which still has the old index at one point im time and from a data center which has the new index a few minutes later. From the users perspective, the index update took place within some minutes. But of course, this procedure may reverse, so that Google switches seemingly between the old and the new index.

The Google Dance Test Domains www2 & www3

The beginning of a Google Dance can always be watched at the test domains www2.google.com and www3.google.com. Those domains normally have stable DNS records which make the domains resolve to only one (often the same) IP address. Before the Google Dance begins, at least one of the test domains is assigned the IP address of the data center that receives the new index first.

Building up a completely new index once per month can cause quite some trouble. After all, Google has to spider some billion documents an then to process many TeraBytes of data. Therefore, testing the new index is inevitable. Of course, the folks at Google don't need the test domains themselves. Most certainly, they have many options to check a new index internally, but they do not have a lot of time to conduct the tests.

So, the reason for having www2 and www3 is rather to show the new index to webmasters which are interested in their upcoming rankings. Many of these webmasters discuss the new index at the Google forums out on the web. These discussions can be observed by Google employees. At that time, the general public cannot see the new index yet, because the DNS records for www.google.com normally do not point to the IP address of the data center that is updated first when the update begins.

As soon as Google's test community of forums members does not find any severe malfunctions caused by the new index, Google's DNS records are ready to make www.google.com resolve the the data center that is updated first. This is the time when the Google Dance begins. But if severe malfunctions become obvious during this test phase, there is still the possibility to cancel the update at the other data centers. The domain www.google.com would not resolve to the data center which has the flawed index and the general public could not take any notice about it. In this case, the index could be rebuilt or the web could be spidered again.

So, the search results which are to be seen on www2.google.com and www3.google.com will always appear on www.google.com later on, as long as there is a regular index update. However, there may be minor fluctuations. On the one hand, the index at one data center never absolutely equals the index at another data center. We can easily check this by watching the number of results for the same query at the data center domains listed above, which often differ from each other. On the other hand, it is often assumed that the iterative PageRank calculation is not finished yet, when the Google Dance begins so that preliminary values exert influence on rankings at that point in time.