Google Core Update: Diagnose, Respond, Recover

A Google core update is a significant, broad change to Google’s ranking systems, announced several times a year on the Search Status Dashboard. It doesn’t target specific sites. It reassesses how all content is ranked, so traffic can drop without anything on your site being broken or penalized. Rollouts usually take about two weeks, and Google’s own advice is to wait, measure carefully, and fix the site as a whole rather than chasing single pages.

This guide is for owners and marketers who saw traffic move around an update and need to know whether it was the update, what to check, and what to leave alone. It charts every core update since 2023 from Google’s dashboard and follows Google’s documented diagnosis steps.

On this page

• What is a Google core update?
• How often do core updates happen, and how long do they take?
• How to tell if a core update hit your site
• Small drop or large drop: what Google says to do
• What not to do after a core update
• How long does recovery take?
• Core updates since the helpful content system merged
• Tracking the next Google core update

What is a Google core update?

A core update is Google adjusting its core ranking systems as a whole. Google’s core updates documentation describes them as “significant, broad changes to our search algorithms and systems” that are “designed to ensure that overall, we’re delivering on our mission to present helpful and reliable results.” Two sentences in that document matter most if you lost traffic:

• Core updates “don’t target specific sites or individual web pages.”
• Pages that fall “aren’t necessarily ‘bad’,” in the words of Google’s analogy; others simply earned a place above them.

Google explains this with a restaurant analogy: a friend asks for your top 20 restaurants, and since you last wrote the list, new places have opened and your view of old ones has changed. The list changes even though nobody’s cooking got worse. A core update is the list being rewritten.

That framing separates core updates from the other things that can hit a site. A manual action is a human penalty, reported in Search Console. A spam update targets policy violations. A technical failure, such as a noindex left on a template, is your own doing. A core update is none of those: it is relative ranking changing around you.

How often do core updates happen, and how long do they take?

Google says “several times a year,” and the record matches. Google’s Search Status Dashboard ranking history lists 13 core updates from March 2023 to May 2026: four in 2023, four in 2024, three in 2025 and two so far in 2026. The chart shows how long each took to finish rolling out.

Scroll the diagram sideways to see all of it.

Two patterns are useful. Eight of the 13 finished in 11 to 19 days, so “about two weeks” is a fair planning number. And the outliers are real: March 2024 took 45 days, while December 2024 took just over six. Do not declare victory or defeat on day three.

The dashboard lists spam updates in the same table, sometimes days apart from a core update, as in March 2026 (spam update on March 24, core update on March 27). If your drop starts during an overlap, you cannot cleanly attribute it to either one from dates alone.

How to tell if a core update hit your site

Line up your traffic change with the update window, then compare the right weeks. Google’s documentation gives a four-step check in Search Console:

1. Confirm the update has finished. Note the start and end dates on the Search Status Dashboard.
2. Wait at least a full week after it ends, then compare the week after completion with the week before the update started.
3. Review top pages and queries. Look at how each ranked before and after, and judge whether the drop is small or large.
4. Analyze search types separately. Web, Images, Video and News can move independently.

Before blaming the update, rule out the alternatives, starting with the technical SEO issues that cause sudden drops on their own. A drop that started before the rollout, a drop on one template only, or a drop in impressions with stable positions (often a SERP feature change) points elsewhere. Our Search Console guide shows how to set up the date comparison and filter to affected pages, and the SEO audit guide covers the technical checks worth running in parallel.

The decision tree below condenses Google’s steps.

Scroll the diagram sideways to see all of it.

Small drop or large drop: what Google says to do

The size of the drop decides the response. Google gives two examples: a move from position 2 to 4 is small, and for those “there’s no need to take drastic action (in fact, we recommend avoiding making changes to content that’s already performing well).” A move from 4 to 29 is large and calls for a deeper assessment.

For a large, sustained drop, Google points to its self-assessment questions for helpful content and asks you to judge “your site overall (not just individual pages).” The questions are specific. A few that catch the most sites:

• Does the content provide original information, reporting, research, or analysis?
• Does it provide substantial value when compared to other pages in search results?
• Does the main heading or page title avoid exaggerating or being shocking?
• Is the content mass-produced or spread across many creators so that individual pages don’t get much care?

Google also suggests asking people you trust, but who are unaffiliated with your site, to run the assessment. That is the part most teams skip, and it is the most useful. An outside reader will tell you which pages exist for search engines rather than for people. Our guide to E-E-A-T covers the experience and trust side of the same questions.

What not to do after a core update

Most damage after a core update is self-inflicted. Google’s guidance, plus what we see in audits, adds up to a short list of things to avoid:

On deletion, Google adds an uncomfortable point: if you are considering deleting whole sections, “that’s likely a sign those sections were created for search engines first, and not people.” In that case removing them can help the rest of the site. It is a diagnosis, not a quick win.

How long does recovery take?

Recovery takes as long as it takes Google’s systems to re-evaluate the site, which Google puts anywhere from days to months. Its documentation says “some changes can take effect in a few days, but it could take several months for our systems to learn and confirm that the site as a whole is now producing helpful, reliable, people-first content.”

Two more details set expectations. First, “if it’s been a few months and you still haven’t seen any effect, that could mean waiting until the next core update.” Second, you are not locked to the announced schedule: Google makes “smaller core updates” that are “not announced because they aren’t widely noticeable,” and those can also lift a site that has improved. Google is also candid that there is “no guarantee” changes will produce a noticeable impact.

Scroll the diagram sideways to see all of it.

Core updates since the helpful content system merged

Core updates now carry more weight than they did before 2024, because the helpful content system is inside them. Google’s ranking systems guide says the helpful content system, announced in 2022, “evolved and became part of our core ranking systems” in March 2024. That was the 45-day update in the chart. Since then there has been no separate helpful content update to blame; content quality issues surface through core updates.

Two other changes affect how you read a drop today:

• AI features share the same data. Google’s AI features documentation says appearances in AI Overviews and AI Mode are counted in the Search Console Performance report within the Web search type. A traffic drop can come from an AI Overview answering the query above you, not from a ranking change. Our analysis of AI Overviews and zero-click search covers the size of that effect.
• Content effort is stored. The 2024 Content Warehouse leak, first analyzed by iPullRank, showed an attribute called QualityNsrPQData.contentEffort, described as an “LLM-based effort estimation for article pages.” Google stores this attribute; the leak does not show how much it is weighted, or whether core updates use it. Our Google leak explainer puts it in context.

Tracking the next Google core update

Set up the tracking before the next update, not during it. A simple routine:

1. Subscribe to the Search Status Dashboard’s RSS feed so you know the start and end dates the day they are posted.
2. Keep an annotated log of your own site changes (launches, migrations, template edits) so you can separate your changes from Google’s.
3. Save a Search Console comparison view of your top 50 pages and queries, ready to run one week after an update completes.
4. Run the helpful content self-assessment on your weakest section once a quarter, with someone outside the team.
5. Track AI visibility alongside rankings, since AI answers now sit in the same traffic numbers.

If a core update has already moved your traffic and you want an outside read on which pages fell and why, our AI visibility audit covers rankings, Search Console data and AI citations together, in the order Google’s own documentation suggests.