Why do rankings recover for some pages after an update and not others?
- Published November 6, 2026
- Linked from 2 answers
- In a cluster of 77
Pages that recover may have changed in a way Google’s systems later rate higher, or were never the problem in the first place, or gained because a competitor fell; the reason is hard to see from outside, and pages that stay down either did not change what was being assessed or were overtaken by content that is simply better. Time is part of it too. Google’s core updates page says “If it’s been a few months and you still haven’t seen any effect, that could mean waiting until the next core update.” Recovery can take months, and for some pages it does not come.
Four reasons the outcomes split
| Page that recovers | Page that does not |
|---|---|
| Improved the content itself: more complete, more accurate, more useful than what replaced it | Changed the surface only: a new date, reordered paragraphs, a new image |
| Lost ground because of a fixable fault that has since been fixed | Lost ground because better pages now exist for its queries, and still trails them |
| Had its improvement picked up by one of the smaller core updates Google makes between announced ones | Is waiting for a reassessment while nothing about it has changed |
| Was hit by a spam signal it has since removed | Lost value from links that a link spam update stopped counting |
The third row matters because recovery is not tied to the next announced update. Google says you do not necessarily have to wait for a major core update, since it also makes smaller core updates that are not announced. The last row has a specific caveat on Google’s spam updates page: after a link spam update, “making changes might not generate an improvement”, because the value those links passed is not coming back.
Not every drop has a defect behind it
A page can fall after a core update without anything wrong on it, because other pages were judged more useful for the same queries. For that page, “recovery” means becoming the better result again, not repairing a fault. That is why waiting alone fails: the reassessment looks at the same page and reaches the same conclusion. To know what that reassessment weighs, read what a core update actually re-evaluates.
Before you expect a recovery
Compare the page with the results that replaced it, query by query, and write down what they do that yours does not. If the list is empty, the page may already be competitive and the drop may reverse with the next reassessment; if the list is long, that list is the recovery plan, and the timeline for its effect is in how long a fixed page takes to return. A page that changed nothing is relying on the rest of the results to change instead.
Add a comment