Did your rankings start moving on Thursday 21 May? You’re not imagining it. Google began rolling out the May 2026 core update that morning, and it is still going. Rankings will keep shifting for up to two weeks. So the most useful things you can do right now are to set a clean baseline, watch calmly, and hold off on changes.
This guide covers what Google has confirmed and why the timing makes this update harder to read than usual. It also covers what it means if you’re still recovering from March, and exactly how I’d watch and judge it.
What Google Has Confirmed About the May 2026 Core Update
The facts so far are short, which is normal for a core update.
- Start: Google’s Search Status Dashboard entry for the May 2026 core update says it was released on 21 May 2026. The entry was posted at 08:43 US Pacific time.
- Expected length: the dashboard says “the rollout may take up to 2 weeks to complete.” If it runs the full two weeks, it would finish in early June.
- Announcement: Google Search Central posted “Today we released the May 2026 core update”. It said it would update its ranking release history once the rollout is complete.
- Guidance: there is no blog post with it and no new advice. The dashboard links to Google’s standing documentation on core updates.
It’s the second broad core update of 2026, after the March 2026 core update. The dashboard lists no other ranking updates between the end of March’s rollout on 8 April and the start of this one.
Like every core update, this is not a penalty. Google is looking again at how its systems judge content across the web. Nothing will show in your Manual actions report, and there is no reconsideration request to file.
Why the Timing Makes This Update Harder to Read
Two things sit close to this rollout. Both can twist what you see in your data.
It Landed Two Days After Google I/O
At Google I/O on 19 May, Google announced several Search changes that went live right away. These included a new search box that accepts longer queries and files. They also included the option to ask follow-up questions from an AI Overview and carry on in AI Mode, and a new default Gemini model in AI Mode. Our roundup of every Search change announced at Google I/O 2026 covers the full list.
Those changes affect how people search and click, not how Google ranks pages. But in your reports they can look alike. Say more people carry on a chat in AI Mode instead of clicking a blue link. Your clicks can fall even when your rankings hold. Our guide to measuring zero-click search covers this.
That’s why I use the week before I/O as the baseline here, not the week before the core update.
It Came About Six Weeks After March Finished
The March 2026 core update ran from 27 March to 8 April. This one started 43 days later. That’s a short gap. It means many sites are still reacting to March when things shift again. Back-to-back updates are not new. In 2023, Google ran three core updates in three months, ending with the November 2023 core update.
If you missed the March coverage, our articles on the March 2026 core update rollout and what changed once it finished explain the earlier timeline and how to judge it. This article focuses on what’s different now.
What the May 2026 Core Update Means If You’re Still Recovering From March
Google’s own guidance says that after a site makes real improvements, its systems can take several months to notice them. It also says that if nothing changes after a few months, you may need to wait for the next core update. For sites hit in March, this is that next core update. It just arrived sooner than many expected.
What that means depends on where you stand.
If You Made Substantial Improvements in April and May
This update may reflect some of that work, but don’t count on it. In my view, six weeks is a short time for changes to be crawled, processed and judged across a whole site.
- If you win back some ground, take it as a sign you’re on the right track, not as a finished job.
- If nothing changes, that doesn’t prove your improvements failed. Google may simply not have judged them yet.
- Keep a list of which pages you changed and when. You’ll need it to read the results properly.
If You Lost Traffic in March and Haven’t Changed Anything
Don’t expect an automatic bounce back. Core updates sometimes soften the effect of an earlier one, but you shouldn’t plan around that.
The rollout period is a bad time to start a big rewrite. Use the next two weeks for the research instead. Export your March losers, compare them honestly with what now ranks, and plan improvements you can make once the update settles. This is exactly how I’d spend the waiting time.
If You Gained in March
Gains from one core update are not locked in. Google looks at every site again each time, so March winners can give some ground back in May. Keep doing what earned the gain. Don’t make big changes to pages that are doing well.
If You’re Mid-Way Through a Site Migration or Redesign
If a big launch is planned for the next two weeks and you can move it, think about waiting until the rollout is done. A site move during a core update makes it almost impossible to tell which one caused a change. If the launch can’t move, write down the exact date so you can separate the two later.
How to Monitor the May 2026 Core Update While It Rolls Out
Watching during a rollout is about collecting good data, not reacting to it. Here’s the simple routine I follow.
1. Lock in Your Baseline Today
In the Search Console Performance report, export data for 12–18 May 2026. That’s the seven days before Google I/O. So it’s free of both the I/O changes and the core update.
- Open Performance, then Search results.
- Set a custom date range of 12–18 May 2026.
- Turn on clicks, impressions, CTR and average position.
- Export the Pages and Queries tabs.
- Repeat for the Discover report if Discover sends you real traffic.
Also export 9–15 April 2026, the first full week after March finished. That gives you a second reference point. It matters if you’re tracking recovery.
2. Annotate Every Date That Matters
Keep a simple log in a spreadsheet or your analytics notes:
- 19 May: Google I/O Search changes go live.
- 21 May: May 2026 core update begins.
- Any site changes you make, including publishing, redirects, template edits and plugin updates.
- The completion date, once Google posts it.
When you review results in June, this log will stop you blaming the update for something you did yourself. I’ve found this log is the one habit people skip and later wish they hadn’t.
3. Check a Few Numbers Every Two or Three Days
Checking every day is tempting, but it mostly just makes you anxious. Two or three check-ins a week are enough. Focus on:
- Average position for your top 20 queries. This is the closest signal to a ranking change.
- Impressions trend. A drop in impressions together with a drop in position suggests ranking movement.
- Clicks by search type. Use the search type filter to view Web, Image, Video and News on their own. A change in one can hide inside the total.
- Organic landing pages in GA4. This shows whether traffic changes are reaching your site, and which sections are affected.
Remember that Search Console data runs a couple of days behind, and the latest days are always incomplete. Don’t read a dip on the latest date as a trend.
4. Separate Ranking Changes From Click Changes
This step matters more than usual because of the I/O changes. Look at position and CTR together.
- Position falls, clicks fall: likely the core update.
- Position stable, CTR falls: more likely a change in how people use the results page, like more AI Overview follow-ups.
- Position stable, impressions fall: could be lower demand, the season, or searches moving to different features.
It also helps to watch visits from AI assistants next to organic search. Our guide to tracking ChatGPT, Perplexity and Gemini visits in GA4 shows how to set that up if you haven’t already.
5. Treat Rank Tracker Swings With Caution
Third-party volatility tools will show spikes over the coming days. They help confirm that something is happening across the web. But they say little about your own site. Big swings in the first week are often partly reversed later in the rollout.
What Not to Do During the Rollout
The biggest mistakes during a core update come from acting on half-finished data. Until Google confirms it is complete, avoid these:
- Rewriting or deleting pages that dropped. Their position may come back before the rollout ends, and you’ll have changed a page for no reason.
- Undoing the improvements you made after March. A dip in the first days of May doesn’t mean your April work was wrong.
- Editing title tags and meta descriptions in bulk. This muddies your data and rarely fixes a core update loss.
- Adding redirects, merging content or changing URL structures. Save structural changes for after you’ve studied the results.
- Disavowing links or buying new ones. Core updates are not link penalties, and paid links risk breaking Google’s spam policies.
- Blocking crawlers or changing robots.txt in a panic. Google needs to keep crawling your site as normal.
- Filing a reconsideration request. There is no manual action to reconsider.
What you should keep doing is business as usual. Publish what you planned to publish. Keep content up to date for real reasons. And fix real technical problems, like broken pages or server errors, right away. Those fixes help users no matter what the update does.
How to Evaluate the Results Once the Rollout Is Complete
When Google marks the rollout complete on the Search Status Dashboard, the real analysis can begin. For that analysis, see our May 2026 core update review. Google recommends waiting at least a full week after it finishes before reviewing Search Console.
Compare the Right Periods
Google’s standard advice is to compare the week after the update with the week before it began. This time, I’d adjust that a little:
- Use 12–18 May as your “before” week, to keep the I/O changes out.
- Use the first full seven days after it finishes as your “after” week.
- Match the days of the week where you can, so weekday and weekend patterns line up.
- Compare the result with 9–15 April as well, so you can see the trend across both 2026 core updates.
Read the Three-Point Pattern
For sites affected by March, the most useful view has three points: before March, after March and after May. Here’s how to read the common patterns.
| After March | After May | What it likely means |
|---|---|---|
| Down | Partly or fully recovered | Your improvements, or a broader reassessment, are being reflected. Keep going. |
| Down | Flat | No change yet. Improvements may need more time or a later core update. |
| Down | Down again | A sustained signal. Google’s systems are consistently preferring other content for your queries. |
| Up | Held | Your gains survived a second reassessment. Avoid major changes to winning pages. |
| Up | Down | Some March gains reversed. Check which pages gave ground and what replaced them. |
| Flat | Moved | This update affected you directly. Analyse it on its own terms. |
Go Page by Page and Query by Query
Totals for the whole site hide the story. Sort your pages by change in clicks and export the biggest movers in both directions. Then group them by type, like product pages, guides, category pages or news.
For each losing page, open the queries behind it and check how big the position change is. Google’s guidance is clear that a small drop, like moving from position 2 to 4, doesn’t call for drastic action. A fall from the top three to page two does.
Then search those queries yourself and look honestly at what now ranks. Do those pages answer the question better? Do they show more first-hand experience? Or are they just more up to date? I always do this part by hand, because tools can’t answer those questions for you.
Use Google’s Self-Assessment for Large, Sustained Drops
Have you dropped a lot in both March and May? Then it’s time for a review of the whole site, not small page tweaks. Google’s helpful content guidance and its self-check questions are the right place to start.
Be fair and honest. It often helps to ask someone outside your team to review your most affected pages next to the ones that rank above them. Focus on lasting improvements to content and usefulness. Treat deleting content as a last resort.
Set Realistic Expectations for Recovery
Some changes can show results within days. A broader reassessment can take months. Google also runs smaller, unannounced core updates between the big ones, and these can reward improvements quietly.
So keep tracking the pages you’ve improved as a group, and review them every month. Don’t just sit and wait for the next named update to judge your work.
Final Thoughts on the May 2026 Core Update
The May 2026 core update is still rolling out, and anything you see this week is not final. Lock in your 12–18 May baseline now and log every change. Separate ranking moves from click moves caused by the I/O changes. And leave your content alone until Google confirms it is complete.
Once it’s done, wait a week and compare against both your May and April baselines. Then decide what to improve based on clear patterns, not early noise. For a refresher on how to study a finished update step by step, go back to our March 2026 core update completion guide and use the same method for May.
