Google Core Updates: What They Are and What to Do After One

A Google core update is a broad change to the systems Google uses to rank search results, made several times a year; after one, confirm its dates, measure what actually moved, and change your content only where an honest assessment shows it falls short.

Google explains core updates on its page Google Search's core updates and your website, last updated on 10 December 2025: "Several times a year, Google makes significant, broad changes to our search algorithms and systems." The same page says that, in general, most sites need not worry about them and may not even notice one. This post is for the times your traffic does move.

What a core update is, and what it is not

A core update is not aimed at your site. Google describes these changes as broad ones that do not single out particular sites or pages. They reassess results as a whole, because the web keeps changing.

Google's own analogy is a top-20 list of your favorite restaurants, rewritten years later. New places have opened and your opinions have shifted, so a restaurant that slips down the list is not necessarily bad; other places have simply earned a spot in your top 20. Applied to a blog, losing positions in a core update does not by itself mean your pages are bad or that you broke a rule. Other pages may now look more helpful for those searches.

Rule-breaking is handled separately. Google lists spam updates as their own entries, and a manual action against your site appears in Search Console's Manual Actions report, which Google's guide to debugging drops in Search traffic tells you to check.

How Google announces a core update

Google posts each core update, along with spam updates and other ranking incidents, on the Google Search Status Dashboard. Each entry gives the date the rollout started and how long it lasted. The posts are short. For the May 2026 core update, the first read "Released the May 2026 core update. The rollout may take up to 2 weeks to complete." The last read "The rollout was complete as of June 2, 2026."

These were the five most recent core updates in the dashboard's ranking history when we checked it on 8 October 2026:

Two things follow. A rollout runs for days or weeks, so a dip on its first day is too early to read. And the list mixes update types, so check the name: on 8 October 2026 the only active entry was the September 2026 spam update, not a core update. Google's guide to the dashboard, last updated on 10 December 2025, says of a listed ranking update: "Often, there's no action needed."

What to do after a core update

1. Wait for the rollout to finish, then a full week

Google recommends waiting at least one full week after the update finishes before analyzing your Search Console data. Then compare that week with a week from before the rollout began.

With the May 2026 dates, that works out like this:

• The rollout started on 21 May 2026 and finished on 2 June 2026.

• The earliest fair check is a week later, from 9 June.

• Compare 2 June to 8 June, the week after the rollout finished, with 14 May to 20 May, the last full week before the start.

In Search Console's Performance report, choose the Date filter, open the Compare tab and enter the two ranges. A seven-day window holds each weekday once, so weekends affect both sides equally.

2. Decide whether the drop is small or large

In that comparison, check how your most important pages and queries moved. Google draws the line with two examples:

• Small drop, such as position 2 to 4: Google says drastic action is unnecessary, and even recommends against changing pages that are already doing well.

• Large drop, such as position 4 to 29: Google calls for a deeper assessment.

Look at search types separately too. Google suggests checking where the drop happened: the News tab, Video mode, Google Images or Web Search; the Search type filter above the chart switches between them.

Before you blame the update, rule out the other usual suspects: your own site changes, indexing problems and seasonal demand. Why keyword rankings change walks through that investigation, query by query.

3. For a large, lasting drop, judge the content with Google's questions

For a large drop that persists, Google's next step is its self-assessment, applied to the site as a whole rather than only to individual pages. The questions are on Creating helpful, reliable, people-first content, last updated on 5 October 2026. For a blog, start with these five, summarized in our words:

• Does the post offer anything original, whether information, reporting, research or analysis?

• Compared with the other pages in the search results, does the post add substantial value?

• Where it relies on other sources, does it add substantial value and originality of its own instead of just copying or rewording them?

• Will readers finish the post feeling they have to search again for better information elsewhere?

• Are you covering many different topics with lots of content, hoping some of it might do well in search?

You want a yes to the first three and a no to the last two.

Start with the posts that lost the most. In the Performance report's Pages table, Google suggests sorting by Clicks Difference to put the biggest losers first. Search each post's main query and read what now ranks above it: Google notes that other pages may be serving the searcher better. Answer the questions for each post as objectively as you can. Google also suggests asking trusted people with no ties to your site to assess it.

Search Console shows only your own site. To see whether other blogs in your niche moved in the same months, look them up in SearchCub's Domain overview. Its Organic traffic chart plots six months of estimated organic visits for the region you choose. These are monthly third-party estimates, so they show a direction rather than the week of a rollout, and they cannot tell you why a site moved.

4. Make lasting improvements, not quick fixes

Google's advice is to concentrate on changes that are good for your readers and will hold up in the long run. Several common reactions run against it:

• Stripping out a page feature because someone said it hurts SEO. What Google says: avoid quick-fix changes like this one.

• Deleting weak sections in bulk. What Google says: "Deleting content is a last resort", for content you can't salvage; if whole sections were made for search engines first, Google says removing them can help your good content perform better.

• Changing post dates so they look fresh. What Google says: one of Google's warning-sign questions asks whether you update dates without making substantial changes to the content.

• Publishing or removing lots of posts to make the site seem fresh. What Google says: another warning sign; on whether it helps rankings, Google adds: "(No, it won't)".

• Padding posts to a target length. What Google says: also a warning sign if you do it because you heard Google prefers a particular word count. Its answer: "(No, we don't.)"

What Google suggests instead is improving content in ways that make a real difference, for example by rewriting or restructuring a post so it is easier to read and navigate. When the assessment points to a specific post, refresh or rewrite helps you choose the size of the update.

How long recovery takes

Google gives no fixed date. After you improve your content, some changes can show up within a few days, yet several months may pass before Google's systems have learned and confirmed that the whole site now produces helpful, reliable content over the long term. If a few months go by with no visible effect, Google says that could mean waiting for the next core update.

You will not always have to wait for a named update. Google also makes smaller core updates that go unannounced because they are not widely noticed, and they can lift improved pages too. It is also candid that nothing you change on your site is guaranteed to make a noticeable difference in search results.

So keep a dated note of what you changed and when. After the next core update finishes, repeat the comparison with the same pages and queries. Measuring a page refresh explains how to compare before and after without trusting one rank check.

Your next step

Open the dashboard's ranking history and write down the start and end dates of the latest core update. If it finished more than a week ago, set up the two comparison weeks in Search Console and note which pages fell, and by how many positions. For the wider picture of how your site is doing in search, see how to check your website's SEO performance.