A Google core update is a broad change to its main ranking systems. It is meant to better surface helpful, reliable, people-first content, and it matters because pages can lose visibility even when nothing on the site changed.
Rankings are relative. After an update, other pages may be judged more helpful or satisfying for the same query. That reassessment can reduce clicks for WordPress, Drupal, and marketing sites without any policy violation.
Table of Contents
- What does a core update change?
- Who feels the effect?
- How often do they happen and how long do they take?
- What should you do after a drop?
- What does a core update change?
- Who feels the effect?
- How often do they happen and how long do they take?
- What should you do after a drop?
What does a core update change?
Google Search Central defines broad core updates as wide changes to core ranking systems in its core update documentation. The goal is to reward pages that serve real reader needs. It is not a targeted fix for one page or site.
The same page can rank lower after reassessment. Google Search Central explains that a drop is not a penalty in its core update documentation. The page did not necessarily break rules. Competing content was judged more useful.
Who feels the effect?
Site owners and publishers feel the effect first. Traffic can fall sharply while content, design, and front-end code stay the same. Google Search Central describes this relative loss in its traffic-drop debugging guide.
Project teams feel it too. A redesign, migration, or content plan may coincide with a rollout. Teams should separate update effects from site changes before assigning blame. Equal-period comparisons by page and query help.
How often do they happen and how long do they take?
Broad core updates happen a few times per year. Recent entries include March, June, and December 2025 plus March and May 2026. They are listed separately from shorter spam updates.
Google posts notable ranking updates to the Search Status Dashboard, where the Dashboard history shows core rollouts often take one to three weeks. Examples include 18 days in December 2025 and 11 days 21 hours in May 2026. Smaller core changes can also happen without an announcement.
What should you do after a drop?
Wait until the rollout finishes. Rankings can move during the rollout, so early edits respond to incomplete data. Confirm there is no manual action in Search Console. Then compare equal periods by page and query.
Look for patterns in intent, depth, freshness, and trust signals. Focus on substantive helpful-content improvements rather than small tweaks or a reconsideration request. Large gains often appear only after later core updates reassess sustained improvements. Google does not disclose exact signals or promise recovery. Keep changes reader-centered and measurable.
- Confirm rollout end date
- Check manual actions in Search Console
- Compare traffic by page and query over equal periods
- Improve usefulness, experience, and trustworthiness of weak pages
- Keep better pages live long enough for later reassessment
What does a core update change?
Google Search Central defines broad core updates as wide changes to core ranking systems in its core update documentation. The goal is to reward pages that serve real reader needs. It is not a targeted fix for one page or site.
The same page can rank lower after reassessment. Google Search Central explains that a drop is not a penalty in a second note in its core update documentation. The page did not necessarily break rules. Competing content was judged more useful.
Who feels the effect?
Site owners and publishers feel the effect first. Traffic can fall sharply while content, design, and front-end code stay the same. Google Search Central describes this relative loss in its traffic-drop guide.
Project teams feel it too. A redesign, migration, or content plan may coincide with a rollout. Teams should separate update effects from site changes before assigning blame. Equal-period comparisons by page and query help.
How often do they happen and how long do they take?
Broad core updates happen a few times per year. Recent entries include March, June, and December 2025 plus March and May 2026. They are listed separately from shorter spam updates.
Google posts notable ranking updates to the Search Status Dashboard history, where Google shows core rollouts often take one to three weeks. Examples include 18 days in December 2025 and 11 days 21 hours in May 2026. Smaller core changes can also happen without an announcement.
What should you do after a drop?
Wait until the rollout finishes. Rankings can move during the rollout, so early edits respond to incomplete data. Confirm there is no manual action in Search Console. Then compare equal periods by page and query, as advised in its traffic-drop debugging guide.
Look for patterns in intent, depth, freshness, and trust signals. Focus on substantive helpful-content improvements rather than small tweaks or a reconsideration request. Large gains often appear only after later core updates reassess sustained improvements. Google does not disclose exact signals or promise recovery. Keep changes reader-centered and measurable.
- Confirm rollout end date
- Check manual actions in Search Console
- Compare traffic by page and query over equal periods
- Improve usefulness, experience, and trustworthiness of weak pages
- Keep better pages live long enough for later reassessment
