Skip to main content

A Look Inside The Google Algorithm?

By July 12, 2006June 9th, 2020No Comments

Last week, Ruslan Abuzant, a web designer from Ukraine stumbled upon a server response page from Google that was not meant to be seen by any Google user. The error came up when he tried to access the cached version of a website from the search engine results pages. Google have rectified the error since then and acknowledged it is something that should not have happened. They refused to comment on the exact nature of the information revealed or shed light on any of the modules referred to in the server response page.

Google’s Server Response Page

The server response page displayed the lines of text pasted below. No one outside Google can be really sure what any of these terms mean, but one can speculate. Of special interest are the terms marked in bold text:

pacemaker-alarm-delay-in-ms-overall-sum 2341989
pacemaker-alarm-delay-in-ms-total-count 7776761
cpu-utilization 1.28
cpu-speed 2800000000
timedout-queries_total 14227
num-docinfo_total 10680907
avg-latency-ms_total 3545152552
num-docinfo_total 10680907
num-docinfo-disk_total 2200918
queries_total 1229799558
e_supplemental=150000 --pagerank_cutoff_decrease_per_round=100 --pagerank_cutoff_increase_per_round=500 --parents=12,13,14,15,16,17,18,19,20,21,22,23 --pass_country_to_leaves --phil_max_doc_activation=0.5 --port_base=32311 --production --rewrite_noncompositional_compounds --rpc_resolve_unreachable_servers --scale_prvec4_to_prvec --sections_to_retrieve=body+url+compactanchors --servlets=ascorer --supplemental_tier_section=body+url+compactanchors --threaded_logging --nouse_compressed_urls --use_domain_match --nouse_experimental_indyrank --use_experimental_spamscore --use_gwd --use_query_classifier --use_spamscore --using_borg

Watch this space for further information on what these terms might mean and information about the indyrank and query classifier systems!