Google Jagger Update 1/2/3

Google has recently done a major algorithm update, nick named "Jagger" update series. This article gives an overview of how and why Google needs to update its website ranking algorithms periodically.

If there is one thing Search Engine Marketers and website owners fear - it is a major algorithm update, especially by Google. Well, much as we may like it not to happen, its here. Google has recently done a major algorithm update, nick named "Jagger" update series.

Google does minor algorithm updates almost on a monthly basis and once in a while, it implements a major algorithm update. The last major Google algorithm update happened in November 2003 called the Florida update, which created quite a stir with website rankings. To know more, read our article on Google Florida Algo Update.

Like the Florida update, the Jagger update has done the much feared "blender" act. It has churned the top-ranking websites and turned it into a list of unrecognizable pulp.

Google has been a hot-favorite amongst the web community searching for information. Most feel that the search results have always been highly relevant. It would be therefore safe to assume that whatever algorithm Google has, works just fine. So why does Google need to re-engineer its perfect-looking algo so drastically? Has it not heard the saying don't fix what aint broke"? From Google's standpoint, the reason is simple and valid. Well, for starters, web is ever-evolving and the algo always need to be adjusted in order to provide the best of results. Google engineered an algo, which it believes will reward good sites and rank them well for its viewers.

Google, like most other search engines, keeps this algo a closely guarded secret to prevent it from being exploited. However, the SEO community is constantly at work trying to rank their sites well. Using calculated guesswork, logical thinking, special tests and extensive trial-and-error methods, they gradually figure out what the algorithm likes and dislikes. Armed with this knowledge, it is not difficult to work on websites to rank them high in SERP (Search Engine Result Pages), irrespective of whether the site deserves to rank at the top or not. This kind of algorithm abuse results in ‘less than desirable' websites displacing good sites from the top ranks, contaminating the Google index. Consequently, following the Kaizen philosophy, Google needs to re-engineer its algorithms to keep, what it believes are bad sites, out of its top ranks. Naturally, major algorithm updates upset the current high-ranking websites & sends a lot of SEO professionals back to their work-bench in order to start all over again.

What is interesting to note is the timing of the algorithm update. When Google updated its algorithm in November 2003, there were large scale allegations by website owners that Google intentionally upset the rankings of popular websites just before the Christmas shopping season to force them into buying Google AdWords paid advertising in order to sustain the visitor traffic. While Google claims that the algo update decisions are not influenced by the AdWords team, it is difficult to understand why they would once again choose a critical timing just before Christmas shopping season to update their algorithm. The stakes are very high and its business after all. Google earned $1.57 Billion in Q3 of 2005. If 2003 pre-Christmas algorithm update effect is any indication, I estimate that Google would record revenues of over $2.05 Billion in Q4 of 2005.

Sources at Google claim that the changes we see are part of 3-phase update (Jagger1, Jagger2 & Jagger3). At the time of writing this article, we are in the completion stage of Jagger2 update. The Jagger3 update is expected to be rolled out over the next few weeks.

Jagger Update 1
The Jagger 1 update pre-shocks actually started with a string of back-link updates that began in September 2005 and continued into middle of October 2005. In mid October, Google updated its PageRank database for public view. Usually updated once a quarter, the PR update always creates a stir. While most SEO professionals heavily play-down the importance of PR in ranking, the legacy of its importance is so deep-rooted in the minds of most webmasters, that it is difficult to shake it off as an insignificant ranking parameter.

Jagger Update 2
It is believed that the Jagger 2 update is now complete and replicated to all the data centers of Google. However, you may still notice some fluctuations in the rankings as things stabilize for each update. We are now at the threshold of the 3rd phase of the Jagger update, which is expected to initiate sometime in the second week of November 2005.

From what we have studied so far, Google has re-engineered several aspects of its algorithm. Amongst other aspects we will know as things roll out, we believe it has altered the impact of the following:-

1. Value of incoming links
2. Value of anchor text in incoming links
3. Content on page of incoming links
4. Keyword repetitions in anchor text
5. Age of the incoming links
6. Nature of sites linking to you
7. Directory links
8. Speed and volume of incoming links created
9. Value of reciprocal links
10. Impact of outbound links / links page on your website
11. Sandbox effect / age of your site, domain registration date
12. Size of your site's content
13. Addition and frequency of fresh content update
14. Canonical / sub domains, sub-sub domains
15. Multiple domains on same IP numbers
16. Duplicate content on same site or on multiple domains
17. Over-optimization, excessive text markup
18. Irrational use of CSS

We are studying various aspects of the Jagger algo update and are closely monitoring the impact of changes in each of the above mentioned parameters and many more not mentioned here. We shall be discussing the impact of each of these aspects in the next parts of this article, which are likely to be written once the Jagger3 update and our study of it is complete.

In the meanwhile, we'd like to give out a word of caution – If you have suffered drop in your website rankings, do not do any drastic changes on your website until the Jagger3 update is fully implemented and stabilized. There is a delicate balance and inter-dependence of all these parameters that can bring back your ranks once the Jagger3 update is completed.

Most of the Update Jagger - Part 2 which described mostly two things;

(1) Duplicate content issues due to www. vs. non www. or /index.html or / or not and so on. Mostly canonicals issues, affecting page rankings in this update.
(2) Reciprocal linking, seems to have been spotted and discounted.

Now, at the same time, people in these threads are reporting the direct opposite results. So it is hard to no for sure, without doing my own tests - which I haven't done - nor will I until this update is over.

Jagger 3 is on its way, Matt Cutts explains that Jagger3 was visible at the 66.102.9.104 data center since November 4th. It seems some of the canonicals issues have been resolved with this Jagger 3 update, but it may be too early to say.

WebmasterWorld has a huge thread already on Part 3 of the Update Jagger. Mcdar built a nice tool to keep track of this Jagger update at http://www.mcdar.net/jaggerresults.htm. Reseller in the thread writes;

We can assume that the following DCs are showing at present Jagger3 Beta-2

66.102.11.99
66.102.11.104

66.102.9.99
66.102.9.104

While previously the following DCs had shown Jagger3 Beta-1 ;-)

216.239.53.99
216.239.57.99
66.102.7.99

Jagger1, Jagger2, and Jagger3 are mostly independent changes, but they’re occurring closely enough in time (plus they interact to some degree) that it’s clearer just to act as if they were one update for feedback purposes.

Google’s Jagger Update - Near Completion ?

What Happened?
Webmaster’s, Site Owners, Online Businesses and SEO Companies everywhere have been desperately trying to decipher the fallout from the longest and most grueling algorithm update in the history of the Internet. Webmaster and SEO Forums have been busier than ever before.

Relevancy and revenue generation are the two top goals of any SE (Search Engine). As the Internet and associated technologies mature, SE algorithms have become much more complex. This was demonstrated in Google’s 3-4 week long 3 phase “Jagger” update.

The initial response was very negative and Google received more bad press from every conceivable corner than what could have been imagined, going in. Many sites fell completely out of SERP (Search Engine Result Placement) over night, seemingly unexplainably. Some have recovered, but many haven’t, while others have improved traffic.

Compounding prognostication, Yahoo initiated a much milder index update during the latter phase of the Jagger update.

Google had several issues to deal with:

1) Scraper Sites
2) Faux AdSense Directory Sites
3) CSS Spamming Techniques
4) Growing “Generic” SERP Irrelevancy
5) Reciprocal Linking Abuse
6) Ballooning BlogSpam

Google had no choice but to act decisively and convincingly.

The following list is how we believe Google has handled these issues in the Jagger update:

1) Increased importance placed on IBL (Inbound Links) Relevancy?
2) Increased importance placed on OBL (Outbound Links) Relevancy?
3) Promotion of relevant Niche Directories (related to 1) & 2)?
4) More weïght thrown back to PR @ top domain?
5) Increased importance on AdSense placement relevancy?
6) Possible introduction of CSS Sp@m filtering?
7) Overall Blog demotions?
8) New and unresolved “canonical” issues?

Let’s look at each action separately:

1) Increased Importance Placed on IBL Relevancy

Reciprocal linking abuse was growing out of hand, even “organic” SERPs were losing relevancy because the majority of active Site administrators were link-mongering anywhere and with anyone they could, regardless of relevant value. Google created that monster throwing the weïght behind quantity over quality for a long time. It appears they simply started applying several published relevancy measurement factors (See US Patent Application #2005007174), which seem to have started becoming more noticeable during the “Bourbon” update.

2) Increased Importance Placed on OBL Relevancy?

The patent application mentioned above is ripe for OBL Relevancy algorithm application. The “Bourbon” update ushered in a marked hit on irrelevantly linked and broader based Directories, while promoting “niche” or “focused” more relevant topical based directories. It makes perfect sense to cut sp@m at its source. This move was subtle but at the same time was an engineering masterpiece because it addressed every förm of link sp@m to some degree, including CSS spammed links. Theoretically, if a link can’t be seen, it won’t be selected by visitors and no measurable time is spent there, therefore it’s “Relevancy Rating” starts to diminish immediately. Some even hypothesize that those kind of links can effect the overall “Relevancy Ranking” for the entire site and has potential to effect the page and Site PR (Page Ranking). We definitely saw a promotion of “Relevant” Directories almost across the board with Jagger.

3) Promotion of Relevant Niche Directories (related to #s 1, 2 & 5)?

We began seeing a Directory SERP shift in the “Bourbon” update and definitely saw a promotion of “Relevant” Directories almost across the board with Jagger. Based on those facts, no one can deny that there has been a significant algorithm re-emphasis in and about “Linking” issues.

4) More Weïght Thrown Back to PR @ Top Domain?

Google had seemed to stray from earlier value ascribed to PageRank for some time in quest of content, content freshness and other goals. After Jagger3, I was surprised to find PR zero pages highly placed in important Topic SERP with a great deal of code and 2 sentences of content. One example is prominent just below Matt Cutt’s Blog when doing a Google search for “Jagger Update”. This particular example is mostly javascrïpt, Adsense and intra-site links. On further inspection, the site is well done, contains a good deal of relative information and has a top domain ranking of PR6. Based on these observations one might concur that more emphasis has been placed on top domain PR. This “observed” return focus to “Authoritative” or Sites holding “Trusted” status should hold no real surprise in the quest for “relevancy” improvement.

5) Increased Importance on AdSense Placement Relevancy?

Google has declared all out war against Sp@m AdSense Sites of every kind. Many of these are/were faux directories and scrapers or other Mëga-Sites utilizing auto content and auto link generation technologies and services. Matt Cutts in his Blog openly asked for and gave specific instructions on how to report these Sites to help augment the overall effect of the alg changes targeting those raging atrocities. The war rages on against all kinds of sp@m, but you can always bet that relevancy, revenue protection and growth will be at the top of the list.

Top 10 Exposure on 105+ Search Engines
Your Keywords - No Bidding - No Pay-Per-Click!
Over 150 Million Searches Per Month
Starting at $3 to $4 or Less per Month
Sign Up Today - Receive 2 Bonuses Valued at $60

6) Possible Introduction of CSS Sp@m Filtering?

Matt Cutts issued an unusually stern warning about using CSS Sp@m techniques, coinciding with the Jagger Update (strangely enough) Oct 19, 2005: Hëre is link to the article in Threadwatch entitled: Google Engineer Hammered over CSS Sp@m Comments.

There is a great deal of controversy over this issue, but it has been a growing cancer for a long time. Some almost seem to be speculating that Google couldn’t figure out the algs to combat these issues yet outside of OBL Relevancy implementation, almost dismissing Matt’s warning as “huff and puff” to scare CSS sp@m abusers into compliance. Google always addresses serious sp@m issues eventually and this one has been on the table for around a year, that I know of! It just doesn’t make sense to ignore a warning from a top Google Engineer, does it?

7) Overall Blog Demotions?

BlogSpam became a growing problem after Blogging gained prominence in 2004. Google had to backtrack on Blog SERP prominence because many of them were not managed well, or at all, losing topical relevancy. Jagger seems to have ushered in a SERP sweep of Blogs that were not topically focused, managed with purpose, and contained adsense and link sp@m. It got to the point that it seemed that half the top SERP for almost any topic were Blog listings. Many have fallen in Jagger.

8) New and Unresolved “Canonical” Issues?

Many are complaining of incorrect indexing issues, especially for sites that were indexed for the first time during Jagger. The problem seems to stem from Google treating the abbreviated Site URL (without www) and the complete URL.

I’ll use one of my own as an example:
www.precisioncompletion.com is a new unranked launch during Jagger and comes up correctly.

Do a Google search for precisioncompletion.com and look at the cache - A PR7 and the wrong website!

Half of the listings are correct and the other half pertain to that other site. Google is aware of these canonical issues being reported, and I believe they are planning to address them as the dust settles a little more on this update. Maybe I need to do a 301 permanent redirect to the full “URL” before I löse that PR7 and see if I can get it to transfer and magically pump up that PR zero!

What to expect next?

There are a large number of sites that saw crippling SERP demotions, including clean coded, relevant, W3C validated, completely “White Hat” sites that haven’t ever even engaged in link exchange programs. I know, I had one that got hit, my first time ever in a Google update. Many of us in that position hope that effect is temporary “Collateral Damage” which will be rectified in subsequent alg tweaking as the dust continues to settle on the “Jagger” update.

I don’t see that Google has deviated off their widely expressed intentions and historical path in the Jagger update. They will continue to fight sp@m at any level that protects the footsteps in their expressed intended path: Relevancy - Market Share - Revenue Generation (Maintenance & Growth) - Fiscal and Community Responsibility.

Google's Jagger 3 Update Soft Launch Friday

I'm not telling the algoholics anything new, but for those of you not monitoring data centers Google AlgoLord Matt Cutts announced Saturday that, "starting yesterday, Jagger3 was visible at the 66.102.9.104 data center. There’s still some minor flux on that data center, but it includes Jagger1, Jagger2, and Jagger3."