When people look at Google's update history, they often assume Google has always announced its changes, named them and told site owners what to fix. It hasn't. For the first few years, Google changed its results quietly, and it was the SEO community, mostly on one busy forum, that noticed, argued and gave the changes names.
The Boston update of February 2003 is where that naming habit started. It is usually listed as the first named Google update, and it sits at the very top of most update histories, including our timeline of every Google algorithm update. But very little was written down about what it actually changed.
So let me explain it simply: what is known, what was only reported at the time, how the monthly “Google Dance” worked back then, and which lessons from Boston still help a business owner in 2026.
The Boston update at a glance
Here is the short version, with an honest note on how solid each fact is.
| Question | Answer | How solid is it? |
|---|---|---|
| When | February 2003 | Month only; listed in the SEOmoz update history quoted by Search Engine Roundtable and Search Engine Land |
| Type | Monthly index update with algorithm changes | Reported, not documented by Google |
| Confirmed by Google? | Reportedly announced at the SES Boston conference | Per Wikipedia; no primary source found |
| What it targeted | No specific target is on record | Unknown |
| Who was affected | Sites across Google's index, as with every monthly update of the time | General, not measured |
| Why it is remembered | First Google update the community named | Widely agreed across histories |
If you only remember one thing, remember the last row. Boston matters less for what it did and more for what it started.
How the Google Dance worked in early 2003
To understand Boston, you first need to understand how Google refreshed its results back then. Today, Google updates its index all the time. In 2003, it didn't.
Matt Cutts, who joined Google as a software engineer in January 2000 according to his Wikipedia biography and later led its webspam team, described the old system in a 2006 blog post:
“From the summer of 2000 to the summer of 2003, index updates tended to happen about once a month.”
— Matt Cutts, Matt Cutts: Explaining algorithm updates and data refreshes (December 23, 2006)
He explained that each update took 6 to 8 days, because each of Google's data centers had to be taken out of rotation and loaded with a completely new index, one at a time. During that week, the same search could show different results depending on which data center answered you. Rankings jumped around, settled, then jumped again. Webmasters called this the Google Dance.
Cutts later joked about how unpredictable the timing felt from the outside:
“People used to use the phase of the moon to predict timing of the next “Google Dance.””
— Matt Cutts, Matt Cutts: Minty fresh indexing (August 7, 2007)
Deep crawl, fresh crawl and the monthly cycle
Forum threads from early 2003 show how webmasters understood the cycle. In simple terms, there were two kinds of crawling:
- The deep crawl (people called the crawler “Deepbot” or “Deepcrawler”). It visited the web broadly, roughly once a month, and its data built the next full index, including PageRank and backlink counts.
- The fresh crawl (“Freshbot”). It revisited frequently changing pages between updates, so new content could appear quickly, sometimes with a date next to the result.
In a March 2003 WebmasterWorld thread, a respected member summed up the difference: “The main difference now is that PageRank (and backlinks) change at the full update.” In other words, fresh crawling could move a page a little, but the big shifts in link value only happened at the monthly dance.
In a January 2003 thread, members were already noticing that Freshbot let them see the effect of on-page changes within days, which hints at the faster model that would arrive later that year.
Why forum members started naming Google's monthly updates
In 2003, Google had no blog for site owners, no Search Console and no status dashboard. The main place where webmasters compared notes was WebmasterWorld, a forum where each monthly update got its own long discussion thread. A Google employee posting as “GoogleGuy” sometimes answered questions there.
When you have a new thread every month about “the update,” you need a way to tell them apart. According to Bruce Clay’s history of SEO from 2000 to 2010, people at WebmasterWorld began naming the updates in 2003, in the way hurricanes are named. You can see the alphabetical pattern in the list itself:
| Name | Month (2003) | What it is remembered for |
|---|---|---|
| Boston | February | First named update; reportedly announced at SES Boston |
| Cassandra | April | Hidden text, hidden links and links between co-owned sites |
| Dominic | May | Changes to how backlinks were counted; new crawler behavior |
| Esmeralda | June | The last of the regular monthly updates |
| Fritz | July | Move to incremental, near-daily index updates |
| Florida | November | The big shake-up that ended many old-school tactics |
Notice that there is no “A.” The list starts at B with Boston, which fits the story that the first name came from the conference city and the alphabet took over from there. I have covered the full story of who names updates, from these forum days to today, in who names Google updates.
What the Boston update actually changed, and what nobody can prove
This is where I have to be honest with you. Most articles about Boston repeat the same one or two lines, and those lines trace back to very thin sources.
The Wikipedia timeline of Google Search says Google announced the Boston update at SES Boston and that it “saw major algorithmic changes and the promise of frequent index updates.” That is about all the detail there is. The update lists compared by Search Engine Roundtable and Search Engine Land give only the name and the month. Bruce Clay's history names it but describes nothing.
So here is how I would sort the claims:
- Reasonably safe: it happened in February 2003, it was a monthly index update, and it was the first one the community named.
- Reported, not verified: that Google announced it at SES Boston, and that it brought “major” algorithm changes.
- Interesting but vague: the “promise of frequent index updates.” If that is accurate, it was an early signal of where Google was heading. By summer 2003, the Fritz update really did replace the monthly cycle.
- Not supported by anything I found: claims that Boston penalized a specific tactic, or that it hit a particular industry.
I treat Boston as a marker in time, not a lesson in tactics. If someone tells you exactly what Boston rewarded, ask them for the source.
What a webmaster's month looked like under the monthly cycle
Numbers make this clearer. Here is a hypothetical example of how a small site owner in early 2003 would have experienced the cycle, based on the timing members described on WebmasterWorld.
- March 5: a relevant site links to your page. Nothing changes in Google.
- Early April: the deep crawler visits the linking page and records the link. Still nothing visible.
- Mid to late April: the monthly update rolls out across data centers over about a week. Your page moves from position 14 to position 9 on some data centers, then on all of them.
- May: the new position mostly holds, with small moves from fresh crawling, until the next dance.
That matches the advice one member gave in a March 2003 WebmasterWorld thread: “If the links came this month, you won't really have a chance to see them until NEXT month.” He suggested waiting 40 to 60 days after getting a link before judging it.
Compare that with today. Google can crawl and index a new page within hours or days, and rankings move a little almost every day. The patience lesson is the same, but the reason is different. Now it is about Google needing time to understand and trust a change, not about waiting for a once-a-month data push.
Lessons from the Boston era that still apply in 2026
Boston itself won't help or hurt your site today. But the way people reacted to it teaches a few things I still repeat to clients:
- Don't judge a change in one day. In 2003, results differed by data center for a week. Today, results differ by location, device and personalization. Look at trends over weeks, which is why I suggest reading our guide to tracking keyword rankings accurately.
- Separate what Google said from what people guessed. Forum theories about Boston spread fast and were rarely checked. The same happens on social media after every core update today.
- Name things so you can measure them. The forum named updates so it could compare notes. Do the same in your own reporting: annotate your analytics with dates of known updates and site changes.
- Understand how Google finds and stores pages. If crawling and indexing are new to you, our free lesson on how search engines work explains them in plain words.
From forum nicknames to confirmed updates on a status dashboard
The naming habit that started with Boston never really stopped. It just changed hands. Here is how the picture has shifted since 2003:
| 2003 (Boston era) | 2026 | |
|---|---|---|
| Who announces updates | Nobody formally; forum threads and an occasional Google employee post | Google, on its Search Status Dashboard and Search Central channels, for major updates |
| Who names them | WebmasterWorld members | Google uses plain names (for example, “March 2026 core update”); the industry still nicknames unconfirmed changes |
| How often the index changes | About once a month, over 6 to 8 days | Continuously |
| How you check your site | Search different data centers by hand | Search Console performance and indexing reports |
That difference between official and unofficial matters more than most people think. I explain why in confirmed vs unconfirmed Google updates, and our lesson on Google algorithm updates covers the basics if you are new to this.
Questions people ask about the Boston update
Did Google officially confirm the Boston update?
Not in the way Google confirms updates today. Wikipedia's timeline says it was announced at the SES Boston conference, but I could not find a primary record of that announcement. There was no Google blog post or status dashboard in 2003, so treat Boston as reported rather than formally confirmed.
Why was it called “Boston”?
The name is tied to the SES Boston search conference, where the update was reportedly announced. The updates that followed in 2003 ran in alphabetical order (Cassandra, Dominic, Esmeralda, Fritz), in the style of hurricane names, which is why Boston is usually treated as the start of the naming habit.
Was Boston a penalty or a spam update?
There is no reliable evidence that it targeted a specific kind of spam. The only description in the record is “major algorithmic changes” plus a promise of frequent index updates. Anyone who gives you a detailed list of what Boston penalized is guessing.
Can a 2003 update still affect my site today?
No. Google's index and ranking systems have been rebuilt many times since then, including the move to continuous indexing and the Caffeine index in 2010. What still matters is the lesson: rankings move when Google's data and systems change, so you judge your site on trends, not on one day's position.
Where to go after the Boston update
In brief: Boston was the first Google update with a name, it came in February 2003 during the monthly Google Dance era, and almost nothing reliable was recorded about what it changed. Its real legacy is the habit of naming, tracking and debating updates, which is still how the SEO world works today.
If you want to follow the story forward, read about the Cassandra update, which came two months later and had a much clearer target. And if your own rankings have moved and you are not sure whether an update is to blame, get in touch with our team. We will look at your data with you and tell you plainly what we see, or you can learn more about our SEO services.
Google updates around the same time
After this update:
- The Cassandra Update (April 2003): Google's Early Crackdown on Hidden Text and Link Swaps (Apr 2003)
- The Dominic Update (May 2003): When Google Changed How Backlinks Counted (May 2003)
Or browse every Google update on one timeline, newest first.
Sources for this Boston update history
- Timeline of Google Search (Wikipedia)
- Search Engine Roundtable: comparing Google update lists
- Search Engine Land: Major Google Updates Documented
- Bruce Clay: Google Updates, A History of SEO From 2000-2010 (December 2, 2010)
- Matt Cutts: Explaining algorithm updates and data refreshes (December 23, 2006)
- Matt Cutts: Minty fresh indexing (August 7, 2007)
- Matt Cutts (Wikipedia)
- WebmasterWorld: “Are updates based on deepbot or freshbot crawls or both?” (March 2003)
- WebmasterWorld: “Strange Google crawl cycle” (January 17, 2003)
- WebmasterWorld: “What the update does and doesn't do?” (March 1, 2003)
- Google Search Status Dashboard
