The May 2026 Core Update officially concluded on June 2. If you're still seeing erratic ranking swings in the weeks that followed, you're not misreading the data - that instability is real, widespread, and expected. Search Engine Roundtable described the week of June 8-12 as "superheated" in terms of SERP volatility. This is not a new update. It's the normal post-rollout behavior after a major Core Update.
Here's the technical reason it happens, what the data shows, and what you should - and should not - do right now.
Why SERP Volatility Continues After a Core Update Ends
When Google declares a Core Update complete, it signals the end of the algorithmic change rollout - not the end of reindexing and rescoring. The two are distinct processes.
During a Core Update, Google modifies how it weights quality signals across the entire index. Applying those new weights to billions of pages doesn't happen instantaneously. Googlebot continues crawling and reprocessing pages for weeks after the official end date. Some pages receive their new quality scores within days of the update ending; others take four to six weeks.
There's also a secondary mechanism: post-update correction. If a Core Update inadvertently over-promoted or over-demoted certain site types beyond what the algorithm intended, Google runs micro-adjustments in the following weeks. These corrections are what generate the "noise" in ranking data after the official end date.
The combination - continued rescoring plus micro-corrections - produces the volatility pattern consistently seen after every major Core Update since 2018.
What the Data Shows for May 2026
Third-party SERP tracking tools recorded unusual activity patterns after the May 2026 Core Update concluded:
Week of June 2-7: Initial post-rollout turbulence. Algoroo and Semrush Sensor registered elevated volatility as Google applied the final batch of new quality scores across domains that hadn't yet been rescored.
Week of June 8-12: Described by Search Engine Roundtable as among the most volatile periods since the update started. This pattern - a volatility spike 1-2 weeks after the official end - appears in post-update data for March 2024 Core Update, September 2023 Core Update, and August 2023 Core Update.
Expected stabilization for May 2026: End of June 2026, with full stabilization by mid-July 2026 based on historical timelines.
Which Sites Are Seeing the Most Instability
Not all ranking fluctuations after a Core Update reflect the same underlying cause:
Sites with mixed-quality content libraries. If your domain has a mix of high-quality and thin or outdated pages, Google takes longer to assign stable domain-level authority signals. Pages on these sites tend to swing more during the post-update period.
Aggregator and UGC-heavy sites. These were among the most impacted categories in May 2026. If your site aggregates content from external sources or relies heavily on user-generated material, the rescoring process continues for longer.
Sites that publish high volumes of time-sensitive content. News sites and event-driven publishers have more URLs to rescore. Individual article rankings may shift independently of domain-wide trends.
Sites that recently made significant content changes. If you published a large volume of new content or restructured site architecture close to the Core Update rollout, Google is processing multiple signals simultaneously, which extends the instability window.
The Right Response: What to Do and What to Avoid
Do: Compare pre-update and post-update performance in GSC.
Open Google Search Console → Performance → set comparison dates: May 5 - June 2 (during update) vs June 3 - present (post-update). Look at total clicks and impressions. If the aggregate numbers are roughly stable, you're likely seeing volatility rather than a genuine ranking decline.
Do: Export your current ranking data now.
Take a snapshot of your current rankings - either through GSC or a rank-tracking tool. You'll want this baseline to compare against when volatility settles. Trying to assess Core Update impact during the volatile period produces misleading conclusions.
Do: Wait for stable data before drawing conclusions.
Any ranking change you're seeing before late June 2026 may not represent the update's true effect. Sites that appear to have recovered may still be processing. Sites that appear to have dropped may stabilize. Decisions made on volatile data are higher-risk.
Don't: Make panic content changes during the volatile period.
This is the most common post-update mistake. Rewriting titles, restructuring content, and rebuilding internal links while Google is still rescoring introduces new signals into an already unstable situation. It can extend your individual site's instability by another two to four weeks. If you believe a page needs improvement, document what you plan to change - and make those changes after late June when the data stabilizes.
Don't: Conflate volatility with update impact.
A page that moves from position 8 to position 5 to position 11 over three weeks is experiencing volatility. A page that moves from position 8 to position 19 and stays there for two weeks is experiencing real impact. The distinction matters for deciding whether action is warranted.
If Your Rankings Are Genuinely Declining - Not Just Volatile
If you've determined through GSC data that a specific page is in consistent decline (not oscillating), it's likely experiencing real Core Update impact rather than post-rollout noise.
The May 2026 Core Update specifically targeted thin content, low-E-E-A-T pages, and sites where AI-generated content wasn't backed by demonstrated expertise. If a declining page falls into any of these categories, waiting for volatility to end won't reverse the trend.
For pages showing genuine decline, the improvement framework is: identify what specific quality signal the page is weak on (depth of content, author expertise signals, accuracy of information, user intent alignment) and address that signal specifically.
For a detailed look at which site types have already recovered from the May 2026 Core Update and what changes they made, see the May 2026 Core Update recovery analysis.
FAQ
Q: The May 2026 Core Update ended June 2. Why are rankings still moving in mid-June? A: Core Update completion marks the end of the algorithmic change rollout, not the end of reindexing. Google continues rescoring pages and making micro-corrections for two to four weeks after the official end date. Volatility in June is expected and documented across previous major Core Updates.
Q: Should I make content changes while my rankings are volatile? A: No. Making significant content or structural changes during the post-update volatile period adds new signals to an already unstable situation and can extend your instability window. Wait until late June 2026 before making data-driven changes.
Q: How do I know if I'm seeing volatility or a real ranking drop? A: Look at a four-week trend in GSC. If rankings are oscillating around a similar level without a consistent downward direction, that's volatility. If a specific page has moved consistently lower for two or more consecutive weeks without recovery, that's likely real Core Update impact.
Q: Algoroo and Semrush Sensor show "extreme" volatility. What does that actually mean for my site? A: Those tools measure how frequently positions change across a tracked keyword set. "Extreme" or "superheated" means positions are changing more often than usual - not that every site is dropping. If your overall click and impression trend in GSC is stable, the tool readings reflect market-wide post-update processing, not necessarily anything specific to your site.
Q: When should I take May 2026 Core Update impact seriously and start making changes? A: After late June 2026. If specific pages are still in consistent decline at that point, the volatility period is over and you're seeing the update's actual effect. That's when diagnostic work and content improvements make sense.
