LinkedIn Says They Got Hit By A Google Algorithm Update In February 2017

May 27, 2019 - 7:42 am 3 by

Linkedin Blue

It is incredibly rare for a public company to admit they got hit by an algorithmic update by Google search. But Eun-Ji Noh, the data scientist in LinkedIn's SEO department shared at SMX London that they did indeed get hit by the update and how they recovered.

They were hit by the February 7, 2017 update, which Google would not comment on but was classified by the SEO community has a phantom update. It was likely a core update, but Google did not confirm core updates back then.

Here is that slide:

click for full size

Eun-Ji Noh explained how they recovered a few months later after implementing some machine learning techniques to find their lower quality content and make improvements to those areas. I think Eun-Ji Noh will be writing an article or two at Search Engine Land about this.

The transparency from LinkedIn on this was amazing and I'd love to see more companies be open about these issues. Of course, like I wrote on Search Engine Land about Cars.com vs CarGurus.com and how they discuss these items in their earnings report and how it impacts their stock prices.

Forum discussion at Twitter.

 

Popular Categories

The Pulse of the search community

Search Video Recaps

 
- YouTube
Video Details More Videos Subscribe to Videos

Most Recent Articles

Search Forum Recap

Daily Search Forum Recap: July 18, 2025

Jul 18, 2025 - 10:00 am
Search Video Recaps

Search News Buzz Video Recap: Google June Core Update Done, Local Ranking Update, AI Mode Updates & AI Calling Businesses

Jul 18, 2025 - 8:01 am
Google Maps

New Google Business Profile Check Edit Status

Jul 18, 2025 - 7:51 am
Google Search Engine Optimization

Google: Login Service Pages Are Hard To Rank In Search

Jul 18, 2025 - 7:41 am
Google

Google AI Overviews For Movie Queries

Jul 18, 2025 - 7:31 am
Google Ads

Google Ads Rolling Out Smart Bidding Exploration To Some Advertisers

Jul 18, 2025 - 7:21 am
Previous Story: Daily Search Forum Recap: May 24, 2019