Pigeon, Possum, Fred and Medic: Google Updates With Unofficial Names, and What They Really Were

Some of the best-known names in SEO history were invented by people outside Google, usually within days of seeing rankings move.

Names are useful shorthand, but they also create stories, and some of those stories have outlived the facts by years. Knowing what each update actually was matters because the same naming habit still shapes how people diagnose drops today.

Confirmed, unconfirmed and named

• Confirmed by Google means Google announced the change or a Google employee acknowledged it on the record. The name may still have come from the industry.
• Unconfirmed means the update is known only from tracking tools and site owners’ reports.
• Industry-named means a publication, analyst or community chose the label, often based on which sites seemed most affected.

The distinction matters in practice. A confirmed update has a start and end date you can measure against, and you can wait for the next one to judge your work. An unconfirmed change has neither, so a recovery plan built on it has no clear point at which to check whether anything worked. Treat unconfirmed names as a hypothesis, never as a diagnosis.

The four at a glance

Name	Date	Area	Google confirmed?	What it really was
Pigeon	24 July 2014	Local search	Yes	A new local algorithm tied more closely to web ranking signals
Possum	About 1 September 2016	Local search	No	Changes to how local results were filtered
Fred	7 to 8 March 2017	Web search	No	An unannounced update that seemed to hit low-value, ad-heavy pages
Medic	1 August 2018	Web search	Yes, as a broad core update	A core update affecting all searches, not health alone

Pigeon, 2014

On 24 July 2014 Google confirmed a new local search algorithm for US English results in Search and Maps. It tied local rankings more closely to traditional web search signals and improved how distance and location were used. Search Engine Land named it Pigeon. It later reached the United Kingdom, Canada and Australia.

Pigeon is a rare case of a nickname attached to a change Google openly acknowledged. Its lasting lesson for local businesses was that the website matters to local rankings, not only the business listing.

Possum, 2016

Around 1 September 2016, local results shifted sharply, and many businesses seemed to vanish from the map pack. In most cases they had not been removed. They had been filtered, often because another nearby listing in the same category or at the same address was shown instead.

That is where the name came from: listings appeared dead but were only playing possum. Google never confirmed it, and what is known comes from local specialists who studied the changes.

Fred, 2017

In early March 2017, many sites reported sharp drops. Asked what to call the change, Google’s Gary Illyes joked that from then on every update should be called Fred. The joke stuck as the name of this one.

Google gave no details. Sites that reported losses were often thin, heavily monetised pages built mainly for ad or affiliate revenue, which is why Fred became shorthand for an update against low-value content. That description comes from observation, not from Google.

Medic, 2018

On 1 August 2018 Google’s Search Liaison announced a broad core algorithm update. Health and wellness sites appeared heavily affected, and the industry quickly named it Medic.

The name stuck, but Google disagreed with what it implied. Within two weeks Google said it was a broad core update involving all searches, not something targeting health sites. Health sites moved more because Google’s quality systems already held them to a higher standard, which is exactly the idea behind YMYL.

That higher standard is explained in what is YMYL, and recovery for those sites in YMYL site recovery.

Other unofficial names you may hear

• Florida, November 2003. One of the first updates widely named by the industry, remembered for hitting many commercial sites just before the holiday shopping season.
• Vince, 2009. A change that seemed to favour big brands. Google described it as a minor change and said it was named after the Google engineer who worked on it.
• Phantom, 2015. Named because Google said nothing at first; Google later acknowledged a change to how its core systems assess quality.
• Maccabees, December 2017. Named by the industry after reports of heavy movement; Google said only that several minor improvements had been made that week.

The pattern is the same each time. Rankings move, the industry names the change after what it thinks happened, and the name outlives the evidence.

Why Google started naming updates itself

The confusion around names pushed Google toward a simple convention. From 2019 it began giving core updates plain, dated names such as the March 2019 core update, so that the industry would not invent misleading ones.

• Dated names describe when, not who was affected.
• The Search Status Dashboard now lists confirmed ranking updates with start and end dates.
• Unconfirmed changes stay unnamed by Google, however much volatility tools show.

Every confirmed update since 2020 is on the update tracker, and the earlier history in Google algorithm update history.

What Pigeon and Possum mean for local businesses now

• Your website matters to local rankings. Pigeon tied local results to the same signals as web search, so a weak site holds back a strong listing.
• Disappearing is often filtering. If another business in the same category shares your address or sits very close, one of you may be filtered out of the map pack for some searches.
• Location changes everything. Local results depend heavily on where the searcher is, so check from several places before concluding you have dropped.

Local recovery is covered in local SEO recovery, and why tracking tools struggle with local results in local search volatility.

The Medic story, repeated

Imagine a personal finance blog that loses a third of its traffic during a 2026 core update. A forum thread calls it the finance update, and the owner concludes Google is punishing finance sites.

That is the Medic mistake again. The update was broad. Finance pages moved further because they are held to a higher standard of trust. The useful response is not to wait for Google to lift a penalty that does not exist, but to strengthen what the standard rewards: real authors with checkable credentials, sources for every claim, current figures and a clear account of who runs the site.

How to name what hit you

• Use Google’s name and date if the change is on the Search Status Dashboard, such as the May 2026 core update.
• Describe the effect in your own words if it is not: a drop in one section, a fall in local visibility, a loss on one query type.
• Keep forum nicknames out of client and management reports. They suggest a cause nobody has confirmed.

Accurate names lead to accurate fixes. A report that says “core update, site-wide quality reassessment” points to a very different plan from one that says “hit by Fred”.

What these names teach for diagnosis today

• A name describes who seemed affected, not what was targeted. Medic sounded like a health penalty; it was not.
• Correlation fills the gap when Google says nothing. Fred’s description came from patterns among losing sites, not from Google.
• Local changes need local diagnosis. Pigeon and Possum moved map results, which behave differently from web results.
• Check the dashboard before the forums. If no update is listed, a popular name does not make one real.

Drops with no confirmed update are covered in rankings dropped with no Google update, and telling core from spam effects in core update vs spam update.