What is a Google core update?

A Google core update is a broad change to Google’s main ranking systems, rolled out a few times a year and announced in advance. Google’s own core updates documentation describes them as significant, broad changes designed to make sure Google is presenting helpful and reliable results overall.

Two things follow from “broad”. A core update is not a penalty, and it does not target individual pages or sites; there is nothing specific to fix in the manual-action sense. And because it reassesses everything at once, a page that loses ground has not necessarily done anything wrong. Other pages have been judged more helpful for the same queries, and the reassessment has moved them up.

This guide covers what a core update reassesses, how to confirm one caused your drop rather than something else, what a core update dip looks like next to the other kinds of hit, and what recovery honestly takes. The full timeline of named updates lives in our pillar Google algorithm updates guide.

The most recent core updates

From Google’s ranking updates list, checked on 12 September 2026:

  • May 2026 core update. Started 21 May, completed in 11 days and 21 hours.
  • March 2026 core update. Started 27 March, completed in 12 days and 4 hours.
  • December 2025 core update. Started 11 December, completed in 18 days and 2 hours.
  • June 2025 core update. Started 30 June, completed in 16 days and 18 hours.
  • March 2025 core update. Started 13 March, completed in 13 days and 21 hours.

The gaps between them have been two to three months, with spam updates in between. At the time of writing no September 2026 core update had been announced, which by that cadence means the next one is due. If you are reading this later, confirm the latest entry on Google’s page; the pillar guide is where we keep the running list.

What a core update dip looks like, and what it does not

The drop that follows a core update has a shape, and it is worth knowing because the other common kind of hit, a spam update, has a different shape and a different fix.

A core update dip is broad and shallow. Many pages lose a few positions across many queries. Average position for the site worsens by a point or two. Impressions and clicks fall together, roughly in proportion. Very little disappears outright.

Here is one from our own Search Console. In the 28 days after the May 2026 core update completed, compared with the 28 days before it started, site impressions went from 1,077 to 608 and average position from 8.7 to 10.9. Most of that sat on one page, a guide that had been carrying the most traffic, which went from 537 impressions to 118 with its average position moving from 7.6 to 8.9. It slid; it did not vanish.

A spam update hit is the opposite: narrow and deep. Specific pages drop out of the results for their main terms and keep only a few long-tail impressions, while the rest of the site holds. Around the August 2026 spam update, three short guides of ours went from hundreds of impressions a day to zero across two days, still indexed, with head terms gone rather than demoted. That is a content reassessment of those pages, and the fix is the pages themselves.

If your loss is broad and shallow on the dates of a core update, this guide applies. If it is narrow and deep, the penalty recovery guide covers spam-update recovery alongside manual actions.

How to confirm a core update caused your drop

The method is the same one we use for any update, and it needs only Google Search Console.

  1. Rule out a manual action. Security and Manual Actions, then Manual actions. If the report lists an issue, that is your problem and it has its own procedure. If it says no issues were detected, continue.
  2. Take the rollout dates from Google’s list. Start date, plus the recorded duration, gives you the completion date.
  3. Compare 28 days before the start with 28 days after the completion, in the Performance report, for clicks, impressions, and average position.
  4. Add the page dimension and sort by the largest drop. A core update dip is usually spread across many pages with a few carrying most of the loss.
  5. Switch to a daily view over the rollout. Movement during a core update tends to build over the rollout window rather than happening on one day, and it settles after the completion date. A single-day cliff points at a spam update or a technical fault instead.

The result of this check is a list of the pages that lost, with dates. That list is the work plan for the next section.

What core updates reassess

Google does not publish a checklist for core updates, but it does publish the questions it suggests asking about your content, in its guidance on creating helpful, reliable, people-first content. Read against a page that lost, they are useful.

Does the page provide original information, reporting, research, or analysis, or does it restate what is already available? Does it demonstrate first-hand experience of the topic? Is it written by someone with evident expertise, and does the page say who? Are claims supported by evidence a reader can check? Does the page fully answer the question a searcher had, or does it stop short and leave them searching again? Would a reader trust this page for a decision that matters to them?

Those questions are the practical form of E-E-A-T: experience, expertise, authoritativeness, and trust. A core update is, in effect, a re-scoring of how convincingly your pages answer them relative to the other pages competing for the same queries. Our helpful content guide goes deeper on what the systems reward.

What to change in the window before the next update

Google’s guidance on what to do after a core update is honest about timing: improvement may not appear until the next core update runs. That makes the months in between the whole opportunity, and the order of work matters.

  • Start with the pages that lost the most. They are the ones the reassessment judged, and improving them is where the next reassessment will look first.
  • Choose depth over volume. A page that covers a topic in outline loses to a page that answers it. Rebuild the outline into the answer, with detail only someone who has done the work would know.
  • Consolidate thin pages on one intent. Several short pages competing for one question dilute each other and read as scale rather than substance. One thorough page beats four sketches.
  • Put a real author on it. A named person with credentials the reader can check, a date that is true, and sources that are linked. Our SEO content writing guide covers the craft side.
  • Remove or rebuild content produced at scale with little added value. If it would not exist except to rank, the reassessment has already noticed.
  • Do not touch what did not lose. Pages that held or gained were judged well; changing them for the sake of activity risks the wrong direction.

What recovery realistically takes

Plan on this: a core update reassessment runs on the core update cycle, so the pages you improve are re-judged when the next one rolls out. That has been every two to three months recently. Between updates, pages are still re-crawled and small movements do happen, but the broad re-evaluation waits.

Two things can be measured in the meantime, and both are worth tracking so that waiting does not turn into hoping. First, the crawl date on each improved page, from URL Inspection; a page that has not been re-crawled since you changed it has not been re-read, and no reassessment can count it yet. Second, impressions on the improved pages, which often begin to recover on long-tail queries before the head terms move.

If the next core update passes and the pages that lost have not moved, the reassessment reached the same conclusion, and the honest reading is that the changes did not go far enough. That is not a reason to give up; it is a reason to go deeper on fewer pages.

Common core update mistakes

  • Chasing individual rankings. A core update moves the site’s standing for a topic; one page’s position is a symptom.
  • Mass deletions. Removing every page that lost throws away what was still working on them without replacing the value.
  • Rewriting titles and meta descriptions only. The reassessment is about the substance of the page, not its label.
  • Waiting without changing anything. The next reassessment reads the same pages and reaches the same result.
  • Publishing more thin content to make up the loss. That is the pattern being discounted, and it compounds the problem at the next spam update.
  • Judging a recovery before the fixed pages have been re-crawled.

When to get help

If the drop is costing you real revenue and you need the cause established quickly, or if the pages that lost are the pages your business depends on, the work above is worth doing with someone who has done it before. Our Google penalty and core update recovery service starts with the dated diagnosis from your own Search Console data, so you know whether you are dealing with a core update, a spam update, or something else before any recovery work is scoped.

Frequently asked questions

What was the last Google core update?
As of 12 September 2026, the most recent core update on Google’s ranking updates list is the May 2026 core update, which started on 21 May and completed in 11 days and 21 hours. Check Google’s page for anything newer.

How long does a core update take to roll out?
Recent core updates have taken between roughly 12 and 18 days to complete. Google records the exact duration of each on its ranking updates page once the rollout finishes.

What should I do after a Google core update?
Confirm the update is the cause, list the pages that lost, and improve those pages against Google’s helpful content questions: original information, first-hand experience, evident expertise, checkable evidence, and a complete answer. Expect the reassessment to arrive with a later core update.

Do core updates penalize sites?
No. Core updates do not target or penalize individual pages or sites. They broadly re-evaluate content, so a drop usually means other content is being rewarded more for the same queries, not that you were singled out.

Can you recover from a core update?
Yes, but not by chasing rankings and not overnight. Recovery means improving the pages that lost to the standard the reassessment applies, and being re-judged when the next core update runs. Sites do recover, and some come back stronger than before the dip.

Should I make changes during a core update?
Small, sensible improvements are fine at any time. Avoid drastic changes while a rollout is in progress, because you cannot yet see the final effect of the update and you risk reacting to movement that would have settled on its own.

How long does it take to recover from a core update?
Often until the next core update, which has been two to three months away in 2025 and 2026. Some improvement on long-tail queries can appear sooner as improved pages are re-crawled. The key is making real improvements in the meantime rather than waiting passively.

Why did my competitor gain when I lost?
Because a core update is relative. The same queries are re-judged, and the pages that answer them more convincingly move up. Looking at what the gaining page does that yours does not is one of the most useful exercises after a core update.

Part of our Google algorithm updates guide.

Hit by a core update and want the cause confirmed from your own data? Our SEO recovery service starts with a dated diagnosis. Never ranked well in the first place? Start with a free SEO audit.