The google fred update is an unofficial, community-assigned name for a set of ranking changes widely observed across the web in March 2017. Google never confirmed a formal update called “Fred,” and to date has not published details of a discrete algorithm change under that name. The name itself came about somewhat as a joke: when asked directly on Twitter what to call an update Google wouldn’t officially name, Google’s then-Webmaster Trends Analyst Gary Illyes suggested that, going forward, every unnamed update could just be called “Fred” — a comment SEO commentators, led by Search Engine Land’s Barry Schwartz, then ran with and applied specifically to the significant ranking volatility observed that March. Because of this origin, “Fred” is best understood less as one specific, well-defined algorithm change and more as a label the industry attached to a period of noticeable volatility with a fairly consistent pattern across affected sites.
What was actually observed in March 2017
Rank tracking tools and SEO forums picked up significant ranking fluctuations starting around March 7-8, 2017, affecting a large number of sites across different niches. Because Google didn’t name or detail the change, the SEO community’s understanding of what “Fred” targeted comes from aggregated observation across many affected and unaffected sites rather than an official factor list. That observed pattern was reasonably consistent: sites that lost visibility tended to share a cluster of traits related to being built primarily to generate ad revenue or affiliate income rather than to serve genuine user needs.
What kind of sites were affected
Analysis from multiple independent SEO researchers in the weeks following the update converged on a fairly similar profile of impacted sites, even without Google’s confirmation of specifics.
| Common trait | Why it’s a quality red flag |
|---|---|
| Heavy ad density | Pages where advertising units dominate the layout relative to actual content degrade user experience and can obscure the content someone came for |
| Thin, low-value content | Articles written primarily as a vehicle for ad placement or affiliate links, without genuinely useful depth |
| Aggressive affiliate monetisation | Content structured around pushing affiliate clicks rather than genuinely helping the reader choose or understand something |
| Content built for search engines, not readers | Articles that read as if optimised purely for keyword targeting rather than written for a human audience |
| Low originality | Content that closely mirrors what’s already available elsewhere, adding little distinct value |
Sites hit tended to combine several of these traits at once, rather than any single trait in isolation being decisive — which lines up with how Google has generally described its quality systems working: assessing overall page and site quality rather than penalising one narrow tactic.
Why “Fred” is best treated as a pattern, not a single event
It’s worth being direct about the uncertainty here: because Google never confirmed a specific “Fred” algorithm or detailed what changed, much of what’s attributed to it is inference from correlated data rather than confirmed fact. Some SEO analysts have since suggested the March 2017 volatility may have reflected general quality algorithm refinements — possibly related to Google’s long-running efforts around content quality and its Panda-descended systems — rather than one single, isolated new update. Treating “Fred” as shorthand for “a webspam- and quality-adjacent update the community couldn’t get an official name for” is more accurate than treating it as a discrete, well-documented event with a fixed checklist of causes.
How Fred connects to Google’s broader quality direction
Whatever specifically changed in March 2017, the pattern of sites affected fits squarely within Google’s long-stated, consistently reiterated guidance: content should be created primarily to help users, not primarily to rank or to generate ad revenue. This is the same underlying principle behind Google’s original 2011 Panda update targeting thin and low-quality content, and it’s a theme that resurfaces in Google’s help documentation and public statements around every major core update since. Fred, in that sense, wasn’t a new philosophy — it looked like a reinforcement of an existing one, applied with enough visible force that the community felt it needed its own name.
How to recover from or avoid a Fred-pattern impact
Because there’s no official Fred penalty to reverse, recovery guidance mirrors general content-quality best practice rather than a specific technical fix — and that’s consistent with how Google frames recovery from broad quality-related ranking changes generally.
- Reduce ad density relative to content. If advertising overwhelms the visible content on a typical page, that ratio is worth revisiting, particularly above the fold.
- Audit content for genuine usefulness. Ask honestly whether an article would still be worth publishing if it earned zero ad or affiliate revenue — if the honest answer is no, that’s a signal worth acting on.
- Consolidate or remove thin pages. A large volume of low-value, near-duplicate content built around monetisation rather than substance is generally a liability, not an asset.
- Rebuild affiliate content around genuine comparison and expertise. Reviews and recommendations that reflect real testing, use, or research read very differently — to both users and quality systems — from templated affiliate copy.
- Prioritise the reader’s actual goal. Content structured around what someone came to learn or decide, with monetisation secondary to that goal, tends to hold up far better across updates generally, not just this one.
How Fred differs from a manual action
It’s worth distinguishing what “Fred” describes from a manual action, since the two are sometimes confused. A manual action is a penalty applied by a human reviewer at Google against a specific site for a specific documented violation, and it shows up explicitly in Google Search Console‘s Manual Actions report with a stated reason. What’s attributed to Fred was, by contrast, an algorithmic ranking shift — sites weren’t individually reviewed and flagged one by one; broad automated quality assessment simply weighted things differently, and visibility moved accordingly. This distinction matters practically: a site affected by Fred-pattern volatility has nothing to “appeal” or submit a reconsideration request for, because there was never a penalty notice to begin with. The only real lever is improving the underlying content and monetisation balance and waiting for that improvement to be reflected the next time relevant systems reassess the site.
The evergreen lesson
Fred is a useful historical case study precisely because it illustrates a recurring pattern in Google’s approach: the company frequently doesn’t name or detail specific updates, yet the sites that suffer in unnamed volatility events tend to share the same underlying traits — content built to serve monetisation or search engines first, and readers second. Chasing a name or a specific “Fred fix” misses the point; the durable response is the same whether or not any particular update ever gets an official or unofficial label. Sites built around genuinely useful, well-researched content with monetisation as a byproduct rather than the primary design goal have consistently proven more resilient across years of Google’s ongoing quality-focused changes.
Spotting an unhealthy ad-to-content ratio or a cluster of thin, monetisation-first pages across a large site is difficult to do manually at scale. SEO Rocket’s chat-first platform can run a content audit and flag exactly this kind of pattern — asking something like “which pages on my site look thin or overly monetised” surfaces the pages worth revisiting before the next quality-related update finds them first. Free plan to start, paid plans from $49/month: app.seorocket.ai.
