Large post-core-update drops not assessed with Google's documented method (core updates)

Google documents a specific assessment method for core updates and says large drops warrant a deeper, site-wide review, while quick fixes and changes to well-performing content should be avoided. The check measures exposure and response; it cannot see what any core update changed.

Use the dashboard dates, compare equal one-week windows in Search Console, separate small from large drops, then review the most affected pages and the site as a whole against the helpful, reliable, people-first questions. Improve or consolidate, and treat deletion as a last resort.

1. Take start and end dates for recent core updates from the Google Search Status Dashboard ranking history.
2. In Search Console, compare the week before each rollout started with a week beginning at least seven days after it completed, by page and by query, for each search type separately.
3. Classify position changes on the top pages as small (for example 2 to 4) or large (for example 4 to 29), following Google's examples.
4. For pages with large, sustained drops, check the change log for quick fixes made in between, and score each page against the self-assessment questions.
5. Report large-drop pages with no assessment, and well-performing pages that were changed without cause.

Written for the Core updates page (evidence: Confirmed).

Indirect. Estimate only: a correct diagnosis avoids damaging changes to pages that were fine, and focuses effort where drops are large and sustained.

Google Search Central documentation on core updates and on creating helpful, reliable, people-first content; Google Search Status Dashboard ranking history.