# Google Core Update: What It Is and How to Tell It Hit You

> A Google core update is one of six causes behind a ranking drop. See Google's own definition, cadence, and how to tell which one hit your site.

- URL: https://missiongrowth.io/blog/google-core-update
- Published: 2026-07-11 · Updated: 2026-09-24
- Author: Ömer Furkan Aktaş, Founder, Mission Growth
- Publisher: Mission Growth. Company facts: https://missiongrowth.io/llms.txt

Your traffic dropped, someone mentioned a "Google core update," and now you're trying to work out if that's actually what happened. It might be. It might also be one of five other things Google names for exactly this situation, each with a different fix.

A Google core update is only one of six causes Google itself lists for a ranking or traffic drop: an algorithmic update, a technical issue, a security issue, a spam issue, seasonality, or a site move.

Ahead: Google's own definition, its real recent cadence, the six-cause diagnostic, and what to do once you've confirmed which cause actually hit you.

In this guide:
- What is a Google core update, and what it isn't
- How often Google actually ships them, checked against a live dashboard
- The six-cause diagnostic for a ranking drop
- Why an empty Manual Actions report doesn't clear you
- What to do next if it is a core update

## What a Google core update actually is

Google describes a core update as a wide-reaching adjustment to its ranking systems, arriving several times a year alongside smaller updates that ship on a rolling basis, unannounced.

So what is a Google core update, in Google's own words? Its documentation calls these changes "broad in nature," adding that they "don't target specific sites or individual web pages." The re-scoring touches a wide slice of the web at once.

Google's algorithms are the full set of ranking systems behind Search, running continuously in the background; a core update is one specific, broad change made to that system. Three related terms get used loosely, and they mean different things:

- **The algorithm.** The whole system of ranking systems Google Search uses to rank pages, running continuously.
- **An update.** Any change to that system, announced or not, big or small.
- **A core update.** A named, broad update to the ranking systems, big enough that Google posts it to its ranking-updates list.

The named, dated updates on record aren't the full picture, either. Google added a section to its own core-updates page in December 2025 confirming it also ships smaller core updates continually, and never announces them "because they aren't widely noticeable."

That matters for a simple reason: if your traffic graph doesn't line up with any dated update on record, the drop can still trace back to one of these smaller, unlogged core updates.

If the technical side of a drop is what you're chasing, [a full seo audit checklist](https://missiongrowth.io/blog/how-to-do-seo-audit) covers crawl and index errors in more depth.

## How often Google ships core updates, and how to find out about the next one

Google shipped four named core updates in 2023, four in 2024 and three in 2025, the answer to how often does Google update its algorithm.

The latest Google core update, as of September 2026, is the May 2026 core update: it started May 21, 2026 and ran 11 days, 21 hours. A newer one, if it is rolling out right now, appears at the top of the Search Status Dashboard with its own start date and duration, which beats any forecast built on last year's pattern.

::dataset{key="core-updates-per-year" name="Named Google core updates by year, 2023-2025 (Search Status Dashboard, checked September 2026)"}

| Year | Named core updates |
|---|---|
| 2023 | 4 |
| 2024 | 4 |
| 2025 | 3 |

::figure{src="/blog/figures/google-core-update-1.svg" alt="Named Google core updates per year from 2023 to 2025, based on the Search Status Dashboard: 4, 4, then 3." caption="Named core updates per year, 2023-2025, per Google's own Search Status Dashboard." width="720" height="222"}

That's checkable against the Google Search Status Dashboard, one live source, rather than a single vendor's tally. Google's own phrasing, "several times a year," is a hedge; this table turns it into a number you can verify yourself, any time.

The Google core updates in 2026 so far are two: March's, which started March 27, and May's, which started May 21. Google posts each named one to its ranking-updates list, so that list is where the next one this year will appear.

Don't read 2025's count of 3 as a new normal; the three-year table gives the checkable range, and the dashboard is the place to confirm whichever count 2026 ends up at.

## The six causes of a ranking drop, and which one is a core update

A drop in traffic or rankings traces to one of six causes Google names: an algorithmic update, a technical issue, a security issue, a spam issue, seasonality, or a site move. A core update is only one of them, so match what you see against the list below before you change anything on the site.

Google's own debugging documentation splits the question into six distinguishable causes, each with its own signal and its own fix, rather than one vague "was it the update" bucket.

::figure{src="/blog/figures/google-core-update-2.svg" alt="The six causes Google names for a search traffic drop, each with its Search Console signal and next step." caption="The six causes Google names for a search traffic drop, and how to check for each one." width="720" height="569"}

| Cause | Signal you'll see | How to verify | Typical next step |
|---|---|---|---|
| Algorithmic update (core update) | Broad, gradual shift across many pages and query types; no message in Search Console | Check whether the timing lines up with an entry on the dashboard | Run the self-assessment below before touching code |
| Technical issue | Pages drop out of the index, or crawl and render errors climb | Check the Indexing report and your server logs | Fix the crawl or render error, then request indexing |
| Security issue | Search Console flags hacked content, malware or injected spam | Check the Security Issues report | Clean the site, then request a review |
| Spam issue | A manual action shows up against the site | Check the Manual Actions report and the message center | File a reconsideration request once the violation is fixed |
| Seasonality | The drop tracks the same calendar window as last year | Compare year-over-year traffic for the same dates | Wait it out, or plan seasonal content ahead of time |
| Site move | The drop starts right after a domain, URL or protocol change | Check your redirect map and the Change of Address tool | Verify every redirect is 1:1, then resubmit sitemaps |

Work the table in order when more than one row seems to match. Rule out a manual action and a security issue first, since Google notifies you of both directly in Search Console. Then check for a technical cause, then seasonality and a site move. Treat an algorithmic core update as the explanation only once the other five don't fit.

Because this list is page-type agnostic, a blog post, a product page and a local landing page all get checked against the same six causes. Google's own definition says as much: the changes are broad, and don't target specific sites or individual pages.

The core web vitals core update question comes up often, and it deserves a straight answer.

A claim in some SEO write-ups says Google "raised" its Core Web Vitals thresholds in a recent update. Google itself doesn't say that. Its page-experience FAQ states: "There is no single signal. Our core ranking systems look at a variety of signals that align with overall page experience," and separately, "Core Web Vitals are used by our ranking systems."

Nothing in that wording ties a threshold change to a specific update. Reading Core Web Vitals as a continuous input rather than something one update flips is our own inference from that FAQ wording.

> Some vendor write-ups have claimed a specific core update "raised" Core Web Vitals thresholds, sourcing that claim only to a third party's analysis and never to Google. Treat any such claim the same way: with skepticism, unless Google's own documentation says it.

AI Overviews and AI Mode run on Google's same ranking systems rather than a separate scoring layer. Treat a change in how often your pages surface there as one more case for this same six-cause check. A full breakdown of AI visibility is a separate topic.

## Is it a core update or a manual action?

A core update is algorithmic and never produces a Manual Actions report entry, so an empty report doesn't rule out an algorithmic drop. It only rules out a manual action.

Google issues a manual action "when a human reviewer at Google has determined that pages on the site are not compliant with Google's spam policies."

That's the core update vs manual action distinction in one line: a core update runs automatically across many sites, with no human reviewer involved. A manual action is the opposite, one person at Google looking at your specific site and deciding it violates a specific policy.

The two also notify you differently. A manual action shows up in the Manual Actions report and in the Search Console message center. A core update shows up nowhere by name; you only see its effect in your traffic and rankings.

Run this quick checklist before you assume either way:

- **Check the Manual Actions report first.** If it's empty, that rules out a manual action. It says nothing about an algorithmic drop.
- **Check the timing against the Search Status Dashboard.** If your drop lines up with a listed update, algorithmic causes move up your list.
- **Don't file a reconsideration request for a core-update drop.** Reconsideration requests only apply to manual actions, and most reconsideration reviews take "several days or weeks," according to Google's own Search Console help page. Filing one for a core update wastes that review cycle on the wrong problem.

## What to do if a core update hit your site

If it is a core update, Google's own self-assessment questions and a fixed comparison-window method are the evidence-based response instead of a quick technical fix.

Google groups its self-assessment questions into two categories: content-and-quality questions ("Does the content provide original information, reporting, research, or analysis?") and expertise questions ("Is this content written or reviewed by an expert or enthusiast who demonstrably knows the topic well?"). These come straight from Google's own [eeat self-assessment questions](https://missiongrowth.io/blog/eeat), applied here specifically to pages that dropped.

Size matters before you react. Google's own examples: a small drop looks like position 2 to 4; a large drop looks like position 4 to 29. Neither size comes with a promise of google core update recovery. Google says it plainly: "There's no guarantee that changes you make to your website will result in noticeable impact in search results."

Recovering from a core update, the May 2026 one or any other, follows the same method: the self-assessment questions on the pages that dropped, then the comparison window below. To measure the impact of the last core update on your own site, read your Search Console performance report across that update's window, with the Search Status Dashboard confirming which update it was and when it ran.

Here's the comparison-window method, generalized so it still works on whichever update just finished:

1. **Confirm the update has actually finished**, using its start date and duration from the Search Status Dashboard.
2. **Wait roughly a week** after that finish date before drawing conclusions; rankings keep settling for a few days after rollout ends.
3. **Compare two equal-length windows**, one from just before the update started and one from after your one-week wait, using the same days of the week on both sides.

The December 2025 core update makes a clean, already-finished example. It started December 11, 2025 and ran 18 days, 2 hours, putting its finish around December 29 or 30 (the dashboard gives no clock time, so the exact hour is approximate).

Applying the method here: confirm that finish date, wait about a week past it, then compare two equal-length windows, one from just before December 11 and one starting after your wait, using the same weekdays on both sides.

::figure{src="/blog/figures/google-core-update-3.svg" alt="Timeline of the December 2025 update starting December 11 and finishing around December 29 or 30, followed by a one-week wait before comparing traffic windows." caption="The December 2025 core update's rollout window, and the comparison window Google recommends waiting for afterward." width="720" height="184"}

A Google core update is one of six named causes behind a ranking drop: the one that's broad, unannounced in detail, and never shows up in your Manual Actions report.

Confirm which of the six actually explains your drop before you touch a single page. If it's the core update, run the self-assessment questions and the comparison window first, and save site changes for whichever of the other five causes turns out to be real.

## FAQ

### Which types of pages get affected by a core update?

Any of them. Google's own definition says core updates are broad and "don't target specific sites or individual web pages," so blog posts, product pages and local landing pages are all in scope equally. There's no page type a core update skips.

### Do Core Web Vitals really affect rankings in a core update?

Google's own page-experience FAQ says "there is no single signal" and that Core Web Vitals "are used by our ranking systems" generally. Google never ties a threshold change to any specific core update, so a claim about a "raised" threshold, sourced only to a third party, isn't confirmed.

### Can I file a reconsideration request for a core update?

No. Reconsideration requests only apply to manual actions. A core update is algorithmic, with no human reviewer and no Manual Actions report entry attached to it.

### Does Google penalize AI-generated content?

That's a narrower, deeper question, answered in full on [does google penalize ai content](https://missiongrowth.io/blog/is-ai-content-bad-for-seo).

### Will my rankings recover automatically after a core update?

A core update resets the recovery clock in a specific way. See [how long does seo take to recover from a core update](https://missiongrowth.io/blog/how-long-does-seo-take) for the full answer.