Google Core Updates in 2026: What Changed and How to Recover

Which Google Updates Have Been Confirmed in 2025 and 2026?

As of 6 November 2026, the confirmed Google core updates 2026 list has two broad core updates (March and May), one Discover core update and four spam updates. In 2025 Google confirmed three core updates and one spam update.

Every date below comes from the ranking update history on the Google Search Status Dashboard. I cross-checked each one against SEO news coverage of the rollout.

You will see blog posts about a “November 2026 core update”. At the time of writing, there is no such entry on the dashboard. My rule is simple: if an update isn’t listed there, I treat it as unconfirmed.

What Changed in the 2026 Updates?

Google gave very little detail. It described both 2026 core updates as regular updates meant to show relevant, satisfying content from all types of sites. There was no new guidance.

March 2026 Core Update

• Started 27 March, three days after the March spam update finished.
• Google said it could take up to two weeks. It finished on 8 April.
• No blog post came with it, and no specific goals were announced.

May 2026 Core Update

• Started 21 May and finished 2 June, just under 12 days. My May 2026 core update review covers what changed.
• Same short “regular update” statement as March.
• It landed only seven weeks after March, so many sites saw two rounds of movement close together. Keep the two windows separate when you analyse your data. For the rollout itself, see my coverage of the May 2026 core update.

February 2026 Discover Core Update

This one was different. It changed Google Discover (the feed of suggested articles in the Google app), not web search rankings. It launched first for English-language users in the US.

In its Search Central blog post, Google said it wanted to show more content from sites in the user’s own country, cut sensational content and clickbait, and favour in-depth, original, timely content from sites with real expertise. Google said it would expand to more countries and languages later, but gave no timeline. My coverage of the Discover core update rollout and what the Discover update changed once complete has the details.

The 2026 Spam Updates

• All four applied worldwide and to all languages.
• March, June and August were short, lasting from under a day to about three days. My June 2026 spam update coverage has the details.
• September was the odd one out. Google warned it could take up to two weeks, and it ran almost exactly that long. My September 2026 spam update completion report has the details.
• Google didn’t name specific spam types for any of them.

What Is a Google Core Update?

A core update is a broad change to Google’s main ranking systems. It isn’t aimed at any single site, page or type of spam. It changes how Google judges relevance and quality across its whole index.

Google’s core updates documentation makes a few points I always keep in mind:

• Core updates happen several times a year. The big ones are listed on the Search Status Dashboard.
• A drop doesn’t mean your site is “bad”. Other pages may simply be judged a better match now.
• Google also runs smaller core updates that it doesn’t announce. In the UK, the CMA now requires Google to give notice before material ranking changes, which I covered in the CMA fair ranking order. Sites can gain from these between the big ones.
• Most sites won’t notice a core update at all.

How Are Core Updates Different From Spam Updates?

Core updates re-weigh quality and relevance. Spam updates improve the systems that spot content breaking Google’s spam policies. The fix for each is very different.

If a drop lines up with a spam update, read Google’s spam policies first. Common problems include scaled content abuse (mass-produced pages), site reputation abuse, expired domain abuse and link spam.

How Do You Tell If an Update Hit Your Site?

Match your traffic changes to the exact update window. Then compare clean before-and-after periods in Search Console. Google says to wait at least a week after an update finishes before you judge the impact.

1. Confirm the dates. Open the Search Status Dashboard and note the start and end dates of the update you suspect.
2. Wait a week after it ends. Rankings move around during a rollout, so data from the middle of one can mislead you.
3. Open the Performance report. In Search Console, go to Performance, then Search results. Google’s Performance report help page explains each metric.
4. Compare two periods. Use the date filter’s Compare tab. Set the week before the update started against a full week after it finished. Match weekdays.
5. Check the search type. Switch between Web, Image, Video and News. Look at the Discover report on its own too.
6. Sort by change. In the Pages and Queries tabs, sort by clicks difference to find the biggest losers.
7. Look at position, not just clicks. If clicks fall but positions stay steady, the cause is likely demand, season or changes on the results page, not a ranking loss.
8. Check Manual actions and Security issues. Rule these out before you blame an algorithm.

Rule Out the Usual Suspects

Before I blame any update, I check these first:

• Seasonal demand (compare year on year).
• Tracking or analytics changes.
• Site migrations, redirects, robots.txt or noindex mistakes.
• New AI Overviews or other results-page features taking clicks on your queries.
• Server errors or slow responses during the rollout.

If any of these look likely, go through my technical SEO audit checklist before you touch your content.

How Bad Is Your Drop?

Google splits drops into small and large, and treats them differently. A small slip usually needs no action. A big fall calls for a proper review of your content.

Small Drops

Google’s example is a page moving from position 2 to 4. Its advice is not to make big changes, especially to content that is still doing well.

Large Drops

Google’s example is a page falling from position 4 to 29. That’s a sign the page, or the site, is now judged less helpful than other options. It needs a closer look.

Site-Wide or Page-Level?

• A few pages fell: compare those pages with what now ranks for their queries.
• A whole section fell: ask whether that section was built mainly to attract search traffic.
• Everything fell: look at site-wide quality signals, such as thin pages, heavy ads or a gap between your topics and your expertise.

What Does Google Say About Recovery?

Google says recovery is possible but not guaranteed, and it can take months. Real improvements to helpfulness matter more than quick technical tweaks. My guide to how long core update recovery takes covers Google’s estimate.

• Some changes can show results within days. A site-wide reassessment can take months.
• If nothing improves after several months, you may need to wait for the next core update.
• You don’t always need to wait for a named update. Smaller, unannounced core updates can also lift sites that have improved.
• Making changes doesn’t guarantee a recovery. Rankings are never fixed, because user needs and the web keep changing.
• Deleting content should be a last resort, not a default fix.

Google’s guide to creating helpful, people-first content is the main self-check tool it points to. Use its questions on your whole site, not just one page.

A Practical Core Update Recovery Plan

Recovery is a content and trust project, not a quick fix. Work through these steps in order, and expect results over months, not days.

1. Build a loss list. Export the pages and queries that lost the most clicks and positions between your two comparison weeks.
2. Study the new winners. For your top 20 lost queries, look at who ranks now. Note what they offer that you don’t: first-hand experience, depth, fresher data, clearer answers or a better format.
3. Score each page honestly. Use Google’s helpful content questions. Ask a colleague or someone outside the business to score them too. In my experience, outside eyes are far more honest.
4. Decide per page. Improve, merge, or (as a last resort) remove. Merge near-duplicate articles into one strong page and redirect the rest.
5. Add real expertise. Show who wrote each page and why they’re qualified. Add original photos, tests, data or examples from your own work.
6. Fix the experience. Cut annoying ads and pop-ups, speed up slow templates and make the main answer easy to find.
7. Tighten your focus. If you drifted into topics you have no authority on, think about pruning or improving those sections.
8. Earn real mentions. Reputation helps. See my guide to link building that still works for ways that don’t break spam policies.
9. Log every change. Write down what you changed and when, so you can tie later gains to specific work.
10. Review after each update. Run your Search Console comparison again after every confirmed core update.

If a Spam Update Hit You

• Find the policy you broke. Typical causes are mass-produced pages, third-party content hosted for ranking value, or paid links.
• Remove or fix it fully. Partial clean-ups rarely work.
• If you have a manual action, fix the issue and send a reconsideration request in Search Console.
• Expect a delay. Automated systems need time to see that the problem is gone.

What Not to Do After a Core Update

The worst responses are panicked, surface-level or rushed. Most of them waste time, and some make things worse. I see the first three on this list far too often.

• Don’t change things mid-rollout. You can’t measure anything until the update has settled.
• Don’t chase rumours. Google warns against stripping page elements because someone said they hurt SEO.
• Don’t mass-delete content. Removing whole sections can look like you built them for search engines, not people.
• Don’t just change dates. Updating a timestamp without improving the page doesn’t make it fresher.
• Don’t rewrite pages that still rank well. A small slip doesn’t need a rewrite.
• Don’t buy links or churn out AI pages to “make up” traffic. That risks a spam problem on top of a quality one.
• Don’t disavow links out of habit. A core update drop is not a link penalty.
• Don’t ignore other channels. If search traffic fell, protect revenue with email, social and local visibility.

How Core Updates Connect to AI Search

Google’s ranking systems also feed its AI features. So the quality signals that help in classic results matter there too. Pages that lose rankings may also lose AI visibility.

• Clear, well-sourced, expert pages tend to do well in both places.
• Check whether a traffic drop came from rankings or from AI Overviews answering the query on the results page.
• For local businesses, a strong profile can balance out organic swings. My Google Business Profile checklist covers the basics.

For more on earning visibility in AI answers, read my guide to getting cited in AI Overviews, AI Mode and ChatGPT search.

Next Steps

1. Bookmark the Search Status Dashboard’s ranking history and check it whenever traffic moves.
2. Run a week-before versus week-after comparison in Search Console for the March and May 2026 core updates separately.
3. Sort your losses into small and large drops, and leave the small ones alone.
4. Score your biggest losers against Google’s helpful content questions and plan improvements page by page.
5. Check your site against the spam policies, especially if you lost traffic in late September or early October 2026.
6. Log every change and review the results after the next confirmed core update.

If I had to pick one habit from all this, it would be patience. With Google core updates 2026 coming close together, careful measurement beats quick reactions every time.