Many business owners believe Google's war on bad links started in 2012 with Penguin. It didn't. Seven years earlier, in the autumn of 2005, Google rolled out an update the SEO forums called Jagger, and it went after many of the same tricks: swapped links, link farms, paid links and text hidden from visitors.
Jagger is worth understanding even today. It was one of the first times Google's spam team talked openly with webmasters during an update, it came in three clearly separate parts, and it showed a pattern that would repeat for the next twenty years. Let me explain what is actually documented, what was only reported by webmasters at the time, and what you can still learn from it.
If you want to see where Jagger sits among every other change, our Google algorithm updates timeline lists them all in order.
Jagger at a glance
| Question | Answer |
|---|---|
| When | Roughly September to November 2005; the visible stages ran from mid-October to mid-November |
| Who named it | Brett Tabke of WebmasterWorld, in a post dated October 18, 2005 |
| Confirmed by Google? | Yes. Matt Cutts blogged about it and asked for feedback using the keywords "jagger1", "jagger2" and "jagger3" |
| Type | Link spam and webspam update, in three separate changes |
| Main targets (as reported) | Reciprocal links with unrelated sites, link farms, paid and sitewide links, hidden text, sneaky redirects, doorway pages, scraper and AdSense directory sites |
| Who was affected | Sites that relied on link swaps and directories for rankings; also many sites with duplicate URL versions |
| What came next | Big Daddy, an infrastructure update that began in December 2005 |
Why it was called Jagger
Google did not name this update. In those days, the WebmasterWorld forum named most big updates, a bit like storms. According to Search Engine Journal's Jagger history, Brett Tabke picked the name in a post on October 18, 2005, because Matt Cutts had recently been described as "the Mick Jagger of search."
The name stuck, and Google went along with it. Cutts even used it in his own feedback instructions. If you are curious how this naming habit grew and later changed, I cover it in who names Google updates.
One more piece of context: Jagger is often called the first truly major update since Florida in November 2003. There were named updates in between, such as Bourbon in mid-2005, but Jagger was the one that forum members treated as the next big shake-up.
How the three stages rolled out
This is the best-documented part of Jagger, because Matt Cutts wrote it down. Back then, Google served results from many data centers, each with its own IP address. A new algorithm would appear on one or two data centers first and then spread. SEOs watched specific IP addresses to see what was coming.
In his post Jagger winding down (November 10, 2005), Cutts laid out the timeline:
- Jagger1 was visible at most data centers from about October 16, 2005. A refreshed version later appeared at 66.102.7.104 and reached all data centers by November 7.
- Jagger2 showed up at 66.102.9.104 around October 27 and reached all data centers by November 6.
- Jagger3 appeared at 66.102.9.104 around November 4 and was expected to spread to the rest over time.
The most important line in that post is short:
“all of Jagger1/2/3 are separate changes.”
— Matt Cutts, Jagger winding down
That matters because forum members at the time often blamed every ranking move in October and November on "Jagger." In reality, three different changes landed close together. Each could have affected a site in a different way. This is still a common mistake when people analyze updates today.
A small timing note: some histories, including Wikipedia's timeline of Google Search, describe the stages as September, October and November. Cutts' own dates put the visible rollout in October and November. I would trust the dates from Cutts, since he was on the team doing the work.
How Google asked for feedback during Jagger
Jagger is also a milestone in how Google talked to site owners. On October 19, 2005, the day after the name appeared, Cutts published Update Jagger: Contacting Google. He listed where to send each type of feedback:
- Spam you saw in results: the spam report form, with "jagger1" in the details field.
- Other bad results: the "Dissatisfied? Help us improve" link at the bottom of the results page, again with "jagger1".
- Sites that disappeared because of hidden text or hidden links: a reinclusion request after cleaning up, with the warning that it would not help if algorithms were the cause.
- Spammy AdSense sites: the feedback link on the ad itself.
“I especially want to hear about webspam that you see in Google.”
— Matt Cutts, Update Jagger: Contacting Google
As the update progressed, the keyword changed to "jagger2" and then "jagger3." Search Engine Roundtable's review of Jagger2 (October 26, 2005) reported that Google wanted the three parts treated "as if they were one update for feedback purposes." The same trick returned in 2008, when Cutts asked for feedback tagged "dewey" during the Dewey update.
What Jagger targeted, according to people who studied it
Here is where I need to be honest. Google never published a list of what Jagger changed. What we have are the patterns webmasters reported and later summaries written by SEO publications. Search Engine Journal's history, built largely from WebmasterWorld threads, groups the reported targets into four buckets.
| Reported target | What it looked like in 2005 | How Google describes it today |
|---|---|---|
| Unnatural backlinks | Reciprocal links with unrelated sites, link farms, sitewide links, sudden spikes in links with exact-match anchor text | "Excessive link exchanges" and "Widely distributed links in the footers or templates of various sites" are listed as link spam |
| Paid links | Text links bought on high-PageRank pages purely to pass PageRank | "Buying or selling links for ranking purposes" is link spam |
| Hidden text and cloaking | CSS used to hide keyword text; delayed meta refresh redirects that showed search engines one page and people another | Hidden text abuse and cloaking are both named spam policies |
| Duplicate URLs and doorway pages | www vs non-www, trailing slashes, /index.html versions of the same page; sites with many near-identical doorway pages | Handled mainly through canonicalization; doorway abuse is a spam policy |
The right-hand column uses wording from Google's current spam policies for Google web search. What strikes me is how little the list of tricks has changed. The labels are more formal now, but the behavior Jagger went after in 2005 is still against the rules.
A 2010 history from Bruce Clay, Inc. adds that the Jagger updates aimed at scraper sites, AdSense directory sites, deceptive CSS and reciprocal linking abuse. That fits the same picture: the target was sites built to rank, not to help anyone.
Why reciprocal links were the headline
In 2005, a huge number of small business sites had a "links" or "resources" page full of swaps: "I'll link to you if you link to me." Whole directories were built just to collect reciprocal links. Since PageRank counted links as votes, this was an easy way to look popular.
Jagger did not make every reciprocal link bad. Two businesses that genuinely work together can link to each other. What was reported to lose value was the pattern: hundreds of swaps with sites in unrelated niches, often through link pages nobody visited. If you want the longer story of how Google's view of links evolved, read my piece on PageRank and link analysis after a decade of link updates.
The domain age theory
After Jagger, many forum members believed Google had turned up the weight on domain age. One WebmasterWorld member wrote that "the age dial has been turned to high," as quoted by Search Engine Journal. Some pointed to a 2005 Google patent that mentioned domain registration length. This was never confirmed, and Search Engine Journal notes that Cutts later downplayed domain age in a 2010 video. I treat it as a theory from the time, not a fact about Jagger.
Who was hit, and what an affected site looked like
There is no public data on how many queries Jagger touched. Google did not publish percentages back then. So rather than invent a number, let me describe the kind of site that the reports suggest lost the most.
Example (hypothetical): imagine a 2005 online gift shop with 400 backlinks. About 300 of them came from a reciprocal link directory and swaps with casino, pharmacy and web hosting sites. Another 60 were sitewide footer links bought on three blogs. Only 40 were real mentions from gift guides and local press. The shop's home page also had a block of keyword text in the same color as the background.
Under the rules many SEOs assumed before Jagger, that profile looked strong. After Jagger, if the swapped and paid links stopped counting, the shop was effectively ranking on 40 links, not 400. On top of that, the hidden text could trigger a separate penalty. The owner would see a drop and think one thing happened, when in fact two or three separate problems were being handled by different changes.
The reports at the time also mentioned a lot of collateral confusion. The third stage coincided with complaints about duplicate and canonical issues, where Google seemed to pick the wrong version of a URL. Many of those problems were really about how Google handled www and non-www versions, which is exactly what the next update, Big Daddy, was built to fix.
From Jagger to Big Daddy to Penguin
Jagger did not stand alone. It was the first step in a long series of changes to how Google handled links and spam.
| Update | When | What it did to links and spam |
|---|---|---|
| Florida | November 2003 | Hit keyword-stuffed and over-optimized commercial pages |
| Jagger | Autumn 2005 | Reported to devalue swapped, farmed and paid links; hit hidden text and cloaking |
| Big Daddy | December 2005 to March 2006 | New crawling and indexing infrastructure; changed canonicalization and how links were handled |
| Penguin | April 2012 | A dedicated algorithm for link spam and over-optimized anchor text |
| Penguin 4.0 | September 2016 | Penguin became real time and mostly devalued bad links instead of demoting sites |
The link from Jagger to Big Daddy is direct. Big Daddy began rolling out the month after Jagger finished and dealt with many of the canonical issues webmasters were complaining about. It also coincided with growing worries about pages landing in the supplemental index, which I cover in the post on the 2006 supplemental index changes. In a January 2007 post, Cutts even linked weak reciprocal linking to pages losing PageRank and slipping into supplemental results, as he repeated in his reply to a Forbes article on "Google hell".
The link to Penguin in 2012 is about intent. Jagger showed Google wanted to discount manufactured links. Penguin turned that into a named, repeatable system. And with Penguin 4.0, Google moved toward simply ignoring bad links, which is close to what many people believed Jagger was doing in 2005.
What Jagger still teaches about links today
Old updates are only useful if they change what you do. Here is what I take from Jagger:
- Links that exist only to rank are a liability, not an asset. They may help for a while, then lose value overnight.
- Patterns matter more than single links. One swap with a partner is normal. Hundreds of swaps with unrelated sites is a footprint.
- "One update" is often several changes. When rankings move, check dates closely before you decide what hit you.
- Hidden text never stops being a risk. It is still a named spam policy, and it is easy to create by accident with old themes or "SEO text" blocks.
- Clean URL versions save headaches. One preferred version per page, with redirects and canonical tags, avoids the duplicate problems people blamed on Jagger.
If you are new to judging links, our beginner lesson on what makes a good link and a bad one covers the basics. Here is how I would audit a site with old link-building history, in the spirit of Jagger:
- Export your links from Search Console (Links report) and one third-party tool.
- Group linking domains by type: real editorial mentions, partners, directories, link exchanges, paid or sponsored placements, and unknown.
- Look for footprints: many links from unrelated niches, identical anchor text, sitewide footer links, or a "links" page on your own site full of swaps.
- Remove or nofollow your own outgoing swap pages, and mark any paid links with rel="sponsored".
- Check your templates for hidden text and old meta refresh redirects.
- Confirm that www, non-www, HTTP and trailing slash versions all redirect to one preferred URL.
- Only consider a disavow file if you have a manual action or a large, clear pattern of paid or spammy links you cannot remove.
Questions people ask about the Jagger update
Was Jagger confirmed by Google?
Yes. Matt Cutts blogged about it, gave dates for each stage and asked for feedback tagged "jagger1," "jagger2" and "jagger3." Google did not, however, publish a list of exactly what changed.
Did Jagger penalize reciprocal links?
Webmasters reported that large-scale reciprocal linking with unrelated sites lost value. Normal links between real partners were not the problem. Google's current spam policies name "excessive link exchanges," not all link exchanges.
Was Jagger the same as Big Daddy?
No. Jagger was a set of three spam-focused changes in autumn 2005. Big Daddy was an infrastructure update that started in December 2005 and finished around March 2006. Their effects overlapped in people's minds because they came so close together.
Is Jagger relevant to my site today?
Only through its lessons. The 2005 algorithm itself is long gone, but the tricks it targeted are still against Google's spam policies, and today's systems are much better at spotting them.
Cleaning up a link profile shaped by 2005-era tactics
Jagger was the moment Google showed, in public, that it would discount links built only to game PageRank. Twenty years later, the message is the same, just enforced by much smarter systems. If your site still carries old swaps, directory links or bought footer links, it is worth cleaning them up before they become a bigger problem.
If you think a past link-building campaign is holding your site back, our team can review it with you. Take a look at our Google penalty recovery service, or request a free quote and tell us what happened.
Google updates around the same time
Before this update:
- The Gilligan Update (September 2005): The 'False' Update and PageRank Refreshes (Sep 2005)
- The Bourbon Update (May 2005): Duplicate Content and Reciprocal Links (May 2005)
After this update:
- Big Daddy (2005-2006): Google's Infrastructure Update Explained (Dec 2005)
- Google's Supplemental Index Update (2006): When Pages Fell Into the 'Supplemental Hell' (Nov 2006)
Or browse every Google update on one timeline, newest first.
Sources for this Jagger update history
- Matt Cutts: Update Jagger: Contacting Google (October 19, 2005)
- Matt Cutts: Jagger winding down (November 10, 2005)
- Search Engine Roundtable: A Review Of The Jagger 2 Update (October 26, 2005)
- Search Engine Journal: Google Jagger Update
- Bruce Clay, Inc.: Google Updates: A History of SEO from 2000-2010
- Wikipedia: Timeline of Google Search
- Google Search Central: Spam policies for Google web search
- Matt Cutts: Google Hell? (May 1, 2007)
