Google Jagger Update (October 2005): What It Targeted and What It Means Today

The Google Jagger update was a series of three separate webspam changes that began appearing at Google data centres around 16 October 2005 and finished spreading around 18 November 2005. It went after link manipulation (reciprocal link schemes, link farms and paid links) along with scraper and made-for-AdSense directory sites and hidden text tricks. The takeaway: Jagger was Google’s first big, openly discussed strike against bought and swapped links, seven years before Penguin.

You can see where Jagger sits among the others in my full list of Google algorithm updates. What makes it stand out historically is that Matt Cutts documented the rollout on his own blog, data centre by data centre, which Google had rarely done before.

Detail	Information
Update name	Google Jagger Update (Jagger 1, Jagger 2 and Jagger 3)
Type	Link spam and webspam
Rollout started	Around 16 October 2005 (Jagger 1 visible at most data centres, per Matt Cutts)
Rollout finished	Around 18 November 2005 (approximate, per Search Engine Land)
Rollout length	About one month across three changes
Confirmed by Google	Yes: Matt Cutts tracked all three parts on his blog
Official source	Matt Cutts: Jagger winding down

What the Jagger update changed

Jagger was not one change. Cutts was explicit: “Recall that all of Jagger1/2/3 are separate changes.” Taken together, they targeted the main ways people were faking popularity and relevance in 2005:

• Reciprocal link schemes: “you link to me, I link to you” arrangements done at scale, often through link exchange pages with hundreds of unrelated sites.
• Link farms: networks of sites that exist mainly to link to each other.
• Paid links: links bought to pass PageRank.
• Scraper and AdSense directory sites: pages built from copied content or thin directory listings, there to earn ad clicks rather than help anyone.
• Hidden text and CSS tricks: keywords or links hidden from visitors but visible to Googlebot.

Cutts also asked webmasters to report remaining spam through Google’s spam report form using the keyword “jagger3”, so Google could use that feedback while the last stage spread.

Timeline

The dates below come from Matt Cutts’s own posts about which data centres were showing each change. Note that Wikipedia and some other histories say Jagger began in September 2005; Cutts’s data centre dates start in mid-October.

Version	First seen	What happened
Jagger 1	16 October 2005	Visible at most data centres around 16 October; a refreshed version was at all data centres by 7 November.
Jagger 2	27 October 2005	Visible at one data centre around 27 October; at all data centres by 6 November.
Jagger 3	4 November 2005	Visible at one data centre around 4 November; still spreading when Cutts posted on 10 November. Search Engine Land puts the end around 18 November.

Who was affected

The sites reported to have lost visibility were those relying on reciprocal links, link farms and paid links, plus scraper and made-for-AdSense directory sites. Because the three changes rolled out at different speeds in different data centres, many site owners at the time saw rankings bounce up and down for weeks, which added to the confusion on forums.

How to tell if the Jagger update hit your site

A 2005 drop cannot be checked in Search Console now. But Jagger’s targets are the same things I look for when a site has a link problem today, so here is how the pattern shows itself in modern data:

• Check Manual actions first. In Search Console, go to Security and Manual Actions, then Manual actions. An “Unnatural links to your site” notice means a person at Google has reviewed your links. That is a different situation from an algorithmic drop and has a different fix.
• Export your links. Use the Links report in Search Console and sort referring sites. Look for clusters: dozens of directories, sites in other languages with no connection to you, or blog networks all published in the same month.
• Look for anchor text that reads like a keyword list. Natural links mostly use your brand name or URL. A profile dominated by exact commercial phrases usually means links were placed, not earned.
• Match dates. If rankings fell during a confirmed link spam update and the losses are on the pages that received the most placed links, the connection is likely.

How to recover from the Jagger update

The advice from the time, recorded in the update histories, was simple: stop the practices Jagger targeted. Sites that had been wrongly penalised could request reinclusion, as Cutts noted. I would put it in this order today:

1. Stop buying links that pass PageRank. If a link is paid or sponsored, it should be marked rel=”sponsored” or rel=”nofollow”.
2. Leave link exchanges and networks. Remove your links page of swapped partners and ask to be removed from link farms where possible.
3. Remove hidden text, hidden links and deceptive CSS from your templates. Check old themes and footers; these often survive site redesigns.
4. Replace thin or scraped pages with pages that have original information, or remove them.
5. Use a reconsideration request only if you have a manual action. Algorithmic drops do not have a request form; recovery comes as Google recrawls and reassesses the site, which can take months.
6. Earn links the slow way: useful resources, local and industry relationships, and coverage that a journalist would actually choose to give.

Links remain the area where shortcuts cause the most damage. If you want help working out which links are worth keeping and how to build better ones, see my off-page SEO services.

Is it still relevant today?

Jagger itself is historical. Its targets were later dealt with much more systematically by Penguin in 2012 and by Google’s ongoing link spam systems. The point that matters for a site owner now is that Jagger shows how long Google has been working on this. Paid and swapped links have been a known risk for twenty years, and each new system has been better at ignoring or penalising them.

Frequently asked questions

When did the Google Jagger update happen?

Jagger 1 was visible at most Google data centres around 16 October 2005, Jagger 2 from 27 October and Jagger 3 from 4 November. Search Engine Land puts the end at around 18 November 2005. Some sources say it began in September 2005.

What did the Jagger update target?

Low-quality links (reciprocal link schemes, link farms and paid links), scraper and made-for-AdSense directory sites, and hidden text or CSS tricks.

Was Jagger one update or three?

Three. Matt Cutts said Jagger 1, 2 and 3 were separate changes that happened to roll out close together.

Is Jagger the same as Penguin?

No. They targeted similar link practices, but Penguin was a separate system launched in 2012. Jagger is best seen as an early forerunner.

Sources

• Matt Cutts: Jagger winding down
• Search Engine Land: Google algorithm updates
• Bruce Clay: Google updates, a history of SEO from 2000 to 2010
• Wikipedia: Timeline of Google Search

If your traffic dropped after link building you are not sure about, request a free audit. My SEO audit service reviews your link profile, checks for manual actions and gives you a clear list of what to remove and what to keep.