Many site owners think of Google updates as big events that arrive on a set date, shake everything up and then stop. For a few years, that was almost true. Google refreshed its index about once a month, and webmasters could plan their lives around it. Then, in the summer of 2003, that rhythm ended.
The update most histories call the last of the monthly ones is Esmeralda, in June 2003. Nobody at the time knew it was the last. Only later did it become clear that it closed the chapter of the “Google Dance.” You will find it in our timeline of every Google algorithm update, right between Dominic and Fritz.
Let me explain what Esmeralda was, what really changed underneath it, how rankings behaved, and why this small, poorly documented update still helps explain how rankings move today.
Esmeralda update at a glance
| Question | Answer |
|---|---|
| When | June 2003 (month only) |
| Type | Monthly index update; infrastructure change |
| Confirmed by Google? | No statement at the time; the end of monthly updates was explained by Matt Cutts in later blog posts |
| What it changed | “Improvements to the index infrastructure,” per Moz's history (via HubSpot) |
| Why it matters | The last regular monthly index update, per Wikipedia |
| Who was affected | Broad; freshness and crawl-related ranking swings were widely discussed |
The Google Dance in one minute
If you missed the early 2000s, here is the short version. Matt Cutts wrote in a 2006 post that from summer 2000 to summer 2003, index updates happened about once a month. Each took 6 to 8 days, because Google's data centers were taken out of rotation one at a time and loaded with a whole new index. During that week, results changed depending on which data center you hit. That shuffle was the Google Dance.
The community gave each monthly update a name, starting with Boston in February 2003. I cover that story in the Boston article and in who names Google updates.
Esmeralda's timing, and why the name is spelled two ways
Esmeralda rolled out in June 2003. Wikipedia’s timeline describes it as “what will later turn out to have been the last of its regular monthly updates,” citing a Kuro5hin article from June 24, 2003. I could not open that article myself, so I rely on Wikipedia's summary of it.
You will see two spellings. The SEOmoz history quoted by Search Engine Roundtable and Search Engine Land lists it as “Esmerelda – June 2003.” Wikipedia and most later sources use “Esmeralda.” Interestingly, Barry Schwartz's own update list in that Search Engine Roundtable post doesn't include it at all, which tells you how minor it felt at the time compared with later names like Florida.
Bruce Clay’s SEO history simply lists “Boston, Cassandra, Dominic, Esmeralda” as the alphabetical run of 2003 names before Florida.
The infrastructure shift behind Esmeralda
Esmeralda is best understood as the visible edge of a change that started during Dominic in May. Here is what the sources show, in order:
- May 2003: webmasters noticed Freshbot crawling deep into sites while the usual monthly deep crawl seemed missing, and wondered if Google was moving to continuous updates.
- June 20, 2003: a detailed WebmasterWorld FAQ argued the old deep crawler had been retired and that the current Esmeralda results used backlink data from both before and after Dominic.
- June 2003: Esmeralda rolls out. Moz's history, reproduced by HubSpot, groups Esmeralda and Fritz together as “improvements to the index infrastructure.”
- Summer 2003: Google switches to incremental updates, an event people called Fritz. Matt Cutts confirmed this years later.
The June FAQ author described the old model clearly: a deep crawl that took one to two weeks, producing data about a month old by the time it went live. Under the new model, deep data was gathered over time, so pages in a new index might have been crawled days or weeks earlier. Their summary line was:
“Updates no longer bringing in data that is always 1 month old!”
— A WebmasterWorld member, June 2003, WebmasterWorld: “DeepBot 2 aka DeepFreshBot small FAQ” (June 20, 2003)
That is a forum member's reading, not a Google statement. But Matt Cutts later confirmed the direction. In his 2007 post on fresh indexing, he wrote that in summer 2003 Google “switched from a monthly batch update to an incremental update.”
How rankings behaved after Esmeralda: the “freshboost” puzzle
With fresher data flowing in, a new set of puzzles appeared. A WebmasterWorld thread called “Fresh Behavior”, started on July 1, 2003, captures the mood right after Esmeralda. The main observations were:
- The “freshboost”: several members believed new pages found by Freshbot got a temporary ranking lift.
- Drops with fresh dates: others reported the opposite, with pages falling when a fresh date appeared and recovering when it vanished. Some noted that sites above them also had fresh dates, so the pattern was inconsistent.
- Spam resurfacing: some members said spammy pages that had disappeared came back with fresh dates.
- Backlinks evening out: one member noted that data centers began “showing equal backlinks” after Esmeralda.
- Freshbot and Deepbot as one crawler: when someone asked how to block Freshbot, the thread starter warned that the two were now the same crawler, and blocking it would hurt.
None of these were confirmed by Google, and members disagreed with each other. That's the honest picture: after Esmeralda, rankings were less predictable, but more current.
Monthly vs rolling updates: what changed for site owners
| Monthly cycle (up to Esmeralda) | Rolling updates (from Fritz on) | |
|---|---|---|
| When new content counted | Mostly at the next monthly update | Within days for many pages |
| When new links counted | After the next deep crawl and update, often 40 to 60 days | Gradually, as linking pages were recrawled |
| Ranking movement | Big jumps once a month, quiet in between | Small daily changes (“everflux”) |
| How webmasters tracked it | Monthly forum update threads | Constant observation; threads like “Rolling Update Observations” in August 2003 |
| Planning | Predictable windows for changes | No “update day” to wait for |
In the August thread, one member summed up the blur by referring to “the Dominic..Esmerelda...Rolling Update thing.” That phrase says a lot. To people living through it, these weren't three separate updates. They were one long transition.
From Esmeralda to Fritz to Caffeine
Esmeralda was the end of one model, not the end of the story. Google's indexing kept moving toward “always fresh”:
| When | Change | What it meant |
|---|---|---|
| June 2003 | Esmeralda | Last regular monthly update |
| Summer 2003 | Fritz | Incremental, near-daily index updates |
| June 2010 | Caffeine | A new index updated continuously, in small portions |
When Google announced Caffeine on June 8, 2010, software engineer Carrie Grimes explained that the old index had layers, and “the main layer would update every couple of weeks.” With Caffeine, Google said it analyzed the web in small portions and updated the index continuously:
“Caffeine provides 50 percent fresher results for web searches than our last index”
— Carrie Grimes, Google, Official Google Blog: Our new search index, Caffeine (June 8, 2010)
So the path runs from monthly (until Esmeralda) to daily (Fritz) to continuous (Caffeine). Each step made rankings move more often and in smaller amounts.
A worked example: reading a ranking drop in 2003 vs today
Here is a hypothetical example to show why this history matters for how you read your own data.
June 2003: your page drops from position 4 to position 12 during the Esmeralda week. Under the monthly model, that drop would likely hold until the next update, about 30 days away. You would see it, change something, and wait a month to learn whether it helped.
October 2026: the same page drops from position 4 to position 12 on a Tuesday. By Friday it is back at 6. Nothing was announced. This is normal daily movement, because Google's index and systems update all the time. If you react to Tuesday's number, you may “fix” something that wasn't broken.
The practical difference: in 2003 you judged one big monthly change; today you judge trends over several weeks.
What Esmeralda teaches about ranking movement today
The end of the monthly dance is the reason rankings feel restless today. Here is how I suggest you handle it:
- Expect movement between announced updates. I explain the reasons in why rankings change between announced updates.
- Use weekly or 28-day averages in Search Console, not single days.
- Check crawling and indexing first when something drops. Our guide to checking crawl stats and indexing after an update shows where to look.
- Learn the basics of indexing if they are new to you, with our free lesson on getting pages indexed.
Questions people ask about the Esmeralda update
Why is Esmeralda important if nobody knows what it changed?
Because of what came after it. Esmeralda, in June 2003, turned out to be the last of Google's regular monthly index updates. From summer 2003, Google refreshed parts of its index almost every day, so Esmeralda marks the end of the Google Dance era.
Is it spelled Esmeralda or Esmerelda?
Both appear. The SEOmoz list quoted by Search Engine Roundtable and Search Engine Land uses “Esmerelda,” while Wikipedia and many later histories use “Esmeralda.” They refer to the same June 2003 update.
Did Google announce that the monthly updates were ending?
Not at the time in any formal way. Matt Cutts later explained, in 2006 and 2007 blog posts, that Google switched from a monthly batch update to an incremental one in summer 2003, an update people called Fritz.
Did Esmeralda penalize any type of site?
There is no reliable evidence of a specific target. The changes people discussed were about crawling, freshness and how link data was refreshed, not a spam crackdown like Cassandra.
What replaced the monthly Google Dance?
Incremental updates: Google refreshed a portion of its index daily or near-daily, which produced small daily ranking changes people called “everflux.” Later, in 2010, the Caffeine index moved Google to fully continuous indexing.
What the last Google Dance means for your rankings now
In brief: Esmeralda in June 2003 was the last of Google's regular monthly index updates. It came during a shift in how Google crawled and refreshed its index, and it was followed by Fritz, which made updates near-daily. Very little was documented about Esmeralda itself, but its place in history is clear: after it, there was no more waiting for the monthly dance.
If your rankings are moving and you can't tell normal movement from a real problem, get in touch with us. We will look at your data together and tell you plainly what is going on. You can also learn more about our SEO services.
Google updates around the same time
Before this update:
- The Dominic Update (May 2003): When Google Changed How Backlinks Counted (May 2003)
- The Cassandra Update (April 2003): Google's Early Crackdown on Hidden Text and Link Swaps (Apr 2003)
After this update:
- The Fritz Update (July 2003): Google Moves to Daily Index Updates (Jul 2003)
- The Florida Update (2003): The Shake-Up That Ended Old-School SEO (Nov 2003)
Or browse every Google update on one timeline, newest first.
Sources for this Esmeralda update history
- Timeline of Google Search (Wikipedia)
- Search Engine Roundtable: comparing Google update lists
- Search Engine Land: Major Google Updates Documented
- HubSpot on SlideShare: A Visual History of Google Algorithm Changes (based on Moz)
- Matt Cutts: Explaining algorithm updates and data refreshes (December 23, 2006)
- Matt Cutts: Minty fresh indexing (August 7, 2007)
- WebmasterWorld: “DeepBot 2 aka DeepFreshBot small FAQ” (June 20, 2003)
- WebmasterWorld: “Fresh Behavior” (July 1, 2003)
- WebmasterWorld: “Rolling Update Observations” (August 2003)
- Official Google Blog: Our new search index, Caffeine (June 8, 2010)
- Bruce Clay: Google Updates, A History of SEO From 2000-2010 (December 2, 2010)
