educational

The Google Dance

Monitoring the Google Dance is a useful means of determining the effectiveness of changes you’ve made, and of indicating the need for changes, in your site’s pages. Here’s a basic guide to understanding the dance and how you can monitor its progress:

What Is The Google Dance?
Approximately once a month, Google updates their index by recalculating the Pageranks of each of the Web pages that they have crawled. The period during the update is known as the Google dance.

Because of the nature of PageRank, the calculations need to be performed about 40 times, and because the index is so large, the calculations take several days to complete. During this period, the search results fluctuate; sometimes minute-by minute. It is because of these fluctuations that the term “Google Dance” was coined. This dance usually takes place sometime during the last third of each month.

Google has two other servers that can be used for searching. The search results on them also change during the monthly update and they are part of the Google dance. For the rest of the month, fluctuations sometimes occur in the search results, but they should not be confused with the actual dance. These fluctuations are due to Google’s fresh crawl, and to what is known as “Everflux.”

Checking New Rankings During The Google Dance
Google has two other searchable servers apart from www.google.com. They are www2.google.com and www3.google.com. Most of the time, the results on all three servers are the same, but during the dance, they are different.

For most of the dance, the rankings that can be seen on www2 and www3 are the new rankings that will transfer to www when the dance is over. Even though the calculations are done about 40 times, the final rankings can be seen from very early on. This is because during the first few iterations, the calculated figures merge to being close to their final figures. After these first few iterations, the search results on www2 and www3 may still change, but only slightly.

During the dance, the results from www2 and www3 will sometimes show on the www server, but only briefly, and new results on www2 and www3 can disappear for short periods. At the end of the dance, the results on www will match those on www2 and www3.

Google currently has 12 data centers, any one of which can provide the Toolbar PageRank of any page. As the dance progresses, these data centers are updated one by one. Before the dance begins, they all return the same current PageRank value for a given page, but during the dance they are updated, one by one, to the new PageRank value. Checking each of the centers during the dance reveals the new PageRank values as they gradually spread through the centers. If the PageRank isn't going to change, the centers show the same values throughout, of course.

For querying the data centers, it is necessary to have the Google Toolbar installed on your browser and the PageRank indicator on. Every time a page is received by the browser, the Toolbar requests its PageRank from one of Google’s data centers. The information is returned as a one-line text file and stored in your Web browser’s Temporary Internet Files folder.

The Toolbar’s request URL includes the URL of the page that it wants the PageRank for (the target page), and a checksum that matches the target page’s URL. A fat URL for a typical Toolbar request (all in one line) would be:

https://216.239.33.102/search?client=navclient-auto&ch=5150615727&features=Rank:FVN&q=info:http%3A%2F%2Fwww%2Eexampledomain%2Ecom%2F

If you copy and paste that fat URL into your browser, you will get Google’s “forbidden” page back, because the target page and checksum don’t match – it’s just an example of the request URL – and notice that the target page is in escaped format – some of the characters are represented by hexadecimal codes (e.g. %2F).

To get the new PageRank for a particular page, you need to make the same request that the Toolbar makes for it, i.e. you need the fat URL that the Toolbar uses. And you need to request the PageRank from all of Google’s data centers. The method is a bit long-winded but it works. Here's how to do it:

Use your browser to browse to the page. This makes sure that the page and the Toolbar's PageRank request are in your Temporary Internet Files folder. You only need to do this once, and not every time.

Open the index.dat file from the Temporary Internet Files folder into a text editor, and perform a search in it for the target page. You'll find the entire fat URL, similar to the one above, for the Toolbar’s PageRank request. Because the target page is escaped in the fat URL, search only for an unescaped part; for example, “example domain.” When you’ve found the fat URL, copy and paste it into your browser’s address box and press ‘enter’ or click ‘Go.’ If the page is in Google’s directory, the returned line includes the directory path.

The last element in the first part of the line is the Toolbar PageRank value for the target Web page. To see the page’s new PageRank spread across the centers during the dance, use the same fat URL, but replace the IP address with each of the data centers. This is also a good way to see the progress of the dance in general.

The data centers’ IP addresses are as follows:

• 216.239.33.100 :: www-ex.google.com
• 216.239.35.100 :: www-sj.google.com
• 216.239.37.100 :: www-va.google.com
• 216.239.39.100 :: www-dc.google.com
• 216.239.41.100 :: www-fi.google.com
• 216.239.51.100 :: www-ab.google.com
• 216.239.53.100 :: www-in.google.com
• 216.239.55.100 :: www-zu.google.com
• 216.239.57.100 :: www-cw.google.com
• 216.239.59.100 :: www-gv.google.com
• 66.102.11.100 :: www-kr.google.com
• 66.102.7.100 :: www-mc.google.com

If you want to check the same pages during future dances, save the fat URLs into a text document so that you don’t need to go through the process of finding them in the Temporary Internet Files folder each time.

Given the importance of Google in delivering quality search engine traffic, don’t you think it’s time YOU learned how to do the dance?

Copyright © 2024 Adnet Media. All Rights Reserved. XBIZ is a trademark of Adnet Media.
Reproduction in whole or in part in any form or medium without express written permission is prohibited.

More Articles

opinion

Best Practices for Payment Gateway Security

Securing digital payment transactions is critical for all businesses, but especially those in high-risk industries. Payment gateways are a core component of the digital payment ecosystem, and therefore must follow best practices to keep customer data safe.

Jonathan Corona ·
opinion

Ready for New Visa Acquirer Changes?

Next spring, Visa will roll out the U.S. version of its new Visa Acquirer Monitoring Program (VAMP), which goes into effect April 1, 2025. This follows Visa Europe, which rolled out VAMP back in June. VAMP charts a new path for acquirers to manage fraud and chargeback ratios.

Cathy Beardsley ·
opinion

How to Halt Hackers as Fraud Attacks Rise

For hackers, it’s often a game of trial and error. Bad actors will perform enumeration and account testing, repeating the same test on a system to look for vulnerabilities — and if you are not equipped with the proper tools, your merchant account could be the next target.

Cathy Beardsley ·
profile

VerifyMy Seeks to Provide Frictionless Online Safety, Compliance Solutions

Before founding VerifyMy, Ryan Shaw was simply looking for an age verification solution for his previous business. The ones he found, however, were too expensive, too difficult to integrate with, or failed to take into account the needs of either the businesses implementing them or the end users who would be required to interact with them.

Alejandro Freixes ·
opinion

How Adult Website Operators Can Cash in on the 'Interchange' Class Action

The Payment Card Interchange Fee Settlement resulted from a landmark antitrust lawsuit involving Visa, Mastercard and several major banks. The case centered around the interchange fees charged to merchants for processing credit and debit card transactions. These fees are set by card networks and are paid by merchants to the banks that issue the cards.

Jonathan Corona ·
opinion

It's Time to Rock the Vote and Make Your Voice Heard

When I worked to defeat California’s Proposition 60 in 2016, our opposition campaign was outspent nearly 10 to 1. Nevertheless, our community came together and garnered enough support and awareness to defeat that harmful, misguided piece of proposed legislation — by more than a million votes.

Siouxsie Q ·
opinion

Staying Compliant to Avoid the Takedown Shakedown

Dealing with complaints is an everyday part of doing business — and a crucial one, since not dealing with them properly can haunt your business in multiple ways. Card brand regulations require every merchant doing business online to have in place a complaint process for reporting content that may be illegal or that violates the card brand rules.

Cathy Beardsley ·
profile

WIA Profile: Patricia Ucros

Born in Bogota, Colombia, Ucros graduated from college with a degree in education. She spent three years teaching third grade, which she enjoyed a lot, before heeding her father’s advice and moving to South Florida.

Women In Adult ·
opinion

Creating Payment Redundancies to Maximize Payout Uptime

During the global CrowdStrike outage that took place toward the end of July, a flawed software update brought air travel and electronic commerce to a grinding halt worldwide. This dramatically underscores the importance of having a backup plan in place for critical infrastructure.

Jonathan Corona ·
opinion

The Need for Minimal Friction in Age Verification Technology

In the adult sector, robust age assurance, comprised of age verification and age estimation methods, is critical to ensuring legal compliance with ever-evolving regulations, safeguarding minors from inappropriate content and protecting the privacy of adults wishing to view adult content.

Gavin Worrall ·
Show More