body { -ms-overflow-style: scrollbar; overflow-y: scroll; overscroll-behavior-y: none; } .errorContainer { background-color: #FFF; color: #0F1419; max-width: 600px; margin: 0 auto; padding: 10%; font-family: Helvetica, sans-serif; font-size: 16px; } .errorButton { margin: 3em 0; } .errorButton a { background: #1DA1F2; border-radius: 2.5em; color: white; padding: 1em 2em; text-decoration: none; } .errorButton a:hover, .errorButton a:focus { background: rgb(26, 145, 218); } .errorFooter { color: #657786; font-size: 80%; line-height: 1.5; padding: 1em 0; } .errorFooter a, .errorFooter a:visited { color: #657786; text-decoration: none; padding-right: 1em; } .errorFooter a:hover, .errorFooter a:active { text-decoration: underline; } #placeholder, #react-root { display: none !important; } body { background-color: #FFF !important; }

JavaScript is not available.

We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using twitter.com. You can see a list of supported browsers in our Help Center.

Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2023 Twitter, Inc.

Conversation

Via

: Major impact from an algo update wouldn't be from *recent* changes. For larger sites, it can take Google's algorithms a longer time to adjust to site changes. It could take several months to recrawl, reindex, & reprocess the site changes: glennga.be/2FTWz71

Embedded video

GIF

1:05 PM · May 8, 2018

Replying to

and

Snap, thanks for pulling this snippet from the hangout. I've always assumed this, but it's great to hear it from Mr Mu.

1

3

Replying to

and

Yes, very important for site owners to understand this. Your last release a week ago didn't cause a 40% drop from yesterday's algo update. It was the months and months of problems leading up to that update. :)

5

Muthuraj Varadharaj

@MuthurajVaradh1

Replying to

and

Really!!!