The May 2026 Core Update ended on 2 June. SERP volatility didn't. Through the second week of June, tracking tools continued reporting elevated and in some periods extreme ranking instability across all major verticals. This is not unusual - it is the documented post-rollout behaviour pattern that follows every significant Google Core Update.
This article explains the mechanics behind post-update volatility, what the data shows for May 2026 specifically, and the practical framework for distinguishing genuine ranking losses from temporary instability.
The Technical Reason Volatility Continues After a Core Update Ends
A Core Update modifies how Google weights quality signals when scoring content. The end date announced by Google marks when the algorithmic change is fully deployed - not when every page in the index has been rescored under the new weights.
Google processes hundreds of billions of indexed pages. Applying revised quality scores across that volume takes weeks, not days. Pages are rescored in crawl batches as Googlebot revisits them. A page crawled shortly before the update ended may receive its new quality score quickly. A page not due for recrawl until later may not receive its final post-update score for several more weeks.
Additionally, Google's systems detect and correct unintended effects of Core Updates. If the update over-impacted a specific content type or domain category more than intended, corrective adjustments roll out in the weeks following. These corrections produce the secondary volatility spike that tracking tools typically record one to two weeks after a Core Update's official end date.
Historical Volatility Patterns After Major Core Updates
The post-update volatility pattern is consistent across the last several Core Updates:
- March 2024 Core Update (45-day rollout): Post-completion volatility lasted three to four weeks, with a notable secondary spike in the second week after the official end.
- November 2023 Core Update: Rankings stabilised approximately four weeks after the completion date.
- August 2023 Core Update: Full stabilisation took six weeks from the end date.
For the May 2026 Core Update (completion 2 June): based on these precedents, the expected stabilisation window is late June to mid-July 2026.
Separating Volatility From Genuine Impact
The critical practical question after any Core Update is whether ranking changes represent genuine algorithmic impact or temporary volatility noise.
Indicators of post-update volatility (not genuine impact):
- Rankings oscillate across a range without a clear directional trend
- GSC shows impressions remaining broadly stable while positions fluctuate
- Multiple pages across the site show simultaneous instability
- Third-party tools show market-wide high volatility (not site-specific)
Indicators of genuine Core Update impact:
- Specific pages show consistent directional decline over two or more consecutive weeks
- GSC total clicks are meaningfully lower than the equivalent pre-update period
- The affected pages share characteristics known to be Core Update targets (thin content, low E-E-A-T, heavy AI-generated text without expert review)
If you're seeing oscillation - including upward swings - the data is not yet stable enough to draw conclusions.
What to Do Right Now
Benchmark before acting. Export current GSC Performance data for the period since 2 June. This will be your baseline for comparing pre-update versus post-update performance once volatility settles.
Identify which pages are oscillating versus declining. Create a simple tracking sheet: page URL, position on 1 June, position this week, trend direction. Update it weekly. After three weeks, you'll have clarity on which pages are actually impacted versus which are experiencing noise.
Do not make structural content changes yet. Every significant change to content, title tags, or internal linking structure during the volatile period adds new signals for Google to process. This can reset the rescoring clock on individual pages and extend instability. Document planned improvements and implement them once rankings stabilise.
Monitor the market, not just your site. If Algoroo or Semrush Sensor shows high market-wide volatility when your rankings swing, that's context that the instability is systemic, not site-specific.
For analysis of which site types have already recovered from the May 2026 Core Update and what they changed, see the May 2026 Core Update recovery overview.
FAQ
Q: Is ongoing SERP volatility after the May 2026 Core Update normal? A: Yes. Post-rollout volatility lasting two to four weeks is the standard pattern after every major Core Update. Google continues rescoring pages and making corrective micro-adjustments after the official end date. The volatility is expected to subside by end of June 2026.
Q: Should I rewrite content or change metadata while my rankings are fluctuating? A: Wait until the volatility period ends, around late June 2026. Making changes during the volatile period introduces new signals that can extend instability on individual pages. Diagnose and plan improvements now, then implement them on stable data.
Q: How long does it take to know whether a ranking change is permanent? A: Wait for two to three consecutive weeks of data showing the same directional trend. If a page consistently loses positions for three weeks without recovery, that's a genuine post-update signal. Single-week drops followed by partial recovery are volatility.
Q: What tracking tools help distinguish volatility from real changes? A: Google Search Console (actual impressions and clicks), Algoroo (market-wide volatility index), and Semrush Sensor give complementary data. GSC is the authoritative source for your site's actual performance; volatility tools give context on market conditions.
Q: When should I start making content improvements in response to May 2026 Core Update? A: After late June 2026 when rankings stabilise. Any earlier and you're optimising against temporary data. Use the time now to audit pages and plan changes, not to implement them.
