June 2025 core update

The 147-day wait that followed

This is the single most useful fact about the June 2025 update, and it has nothing to do with what the update targeted. A site demoted on 30 June had no mechanism for re-evaluation until 11 December. Nearly five months, during which nothing anyone did to their site could produce a ranking recovery.

That is the widest documented gap in the recent record, and it sits at one end of a range that runs from 7 days to 147. Quoting the 82-day average without that range is how recovery projects end up feeling like failures at month four.

What happened during the wait

Two things, and both caused misdiagnosis. Google confirmed the August 2025 spam update, which many core-affected sites wrongly hoped would reassess them, and in mid-September Google removed the ability to load 100 search results per page. That change caused widespread Search Console impression drops that had nothing to do with rankings.

• A spam update does not reassess a core demotion. Different systems, different standards. The August 2025 run changed nothing for sites demoted in June.
• The September impression drop was a reporting artefact. Impressions fell while clicks and positions held. If your graph shows that signature, nothing happened to your rankings.
• October 2025 volatility was unconfirmed. Three waves of measured turbulence with no announcement, which the volatility sensor records even where Google does not.

If you dropped on 30 June 2025

The reassessment happened in December 2025. If the site recovered then, the work was right. If it did not, the cause survived the work, and the next window is whichever core update comes after. Planning that wait properly is what the timeline planner is for.

Source: Google ranking updates list