Google's August 2024 core update guidance
Alongside its August 2024 core update, Google revised its guidance to give website owners more detailed advice on assessing search performance changes.
The main changes
The revised document added and reworked sections about diagnosing traffic changes, reviewing content and setting expectations for recovery.
New sections
Two additions focused on checking for a traffic drop in Search Console and assessing a substantial fall in rankings.
Check for a traffic drop in Search Console
This section describes how to use Search Console to investigate whether performance changes coincide with a core update.
The process includes:
- Check the Search Status Dashboard to confirm that the update has finished.
- Wait at least a full week after completion before analysing the comparison in Search Console.
- Compare performance before and after the update to investigate ranking changes.
- Review search types separately, such as web, image, video and news results.
Assess a substantial ranking drop
For a large decline, Google recommends reviewing content against its quality guidance, paying particular attention to affected pages. Coinciding timing alone does not explain every cause of lost traffic.
Other additions
The revised guidance also discusses changes to make, prioritising substantive improvements useful to readers over quick fixes aimed only at search performance.
Advice on changing content
Google recommends treating deletion as a last resort. Removing content may be appropriate where it cannot be improved, but content should first be assessed for its purpose and usefulness rather than deleted automatically after a ranking drop.
How quickly can changes appear?
The guidance explains that effects can take days to several months to become clear, depending on the change and Google's reassessment. Some improvements may take until a later core update. There is no guaranteed recovery date.
Material removed or reworked
The August 2024 revision removed or changed parts of the earlier explanation, including wording about affected pages not violating spam policies and an analogy about updating a list of films. Those editorial changes should not be read as a finding that every affected site violated policy.
The change list included these additions:
- 'Check for a traffic drop in Search Console': steps for examining performance changes.
- 'Assessing a large drop in position': advice on reviewing substantially affected pages.
- 'Things to keep in mind when making changes': substantive improvements and deletion as a last resort.
- 'How long does it take to see an effect in Search results': expectations about reassessment timing.
Removed or reworked:
- A paragraph explaining that pages affected by a core update had not violated spam policies.
- The comparison with updating a list of favourite films.
- The earlier 'Assessing your own content' discussion was replaced by more specific advice about a substantial ranking drop.
- Earlier wording about update and recovery timing was revised.
The revised structure gives website owners a more practical sequence for investigating performance and planning changes. Check the current documentation before applying historical guidance to a new update.