Is the May 2026 core update finished yet?
Not quite, but it is close. Google launched the May 2026 broad core update on May 21 at 08:40 PDT under incident wdAXJk6LRRihEjpzEeWE. The guidance said up to two weeks, which points to completion around June 4. As of today, May 29, trackers show volatility settling, so the picture is nearly final.
What pages got hit hardest in this update?
Thin content pages and pages with weak author signals moved most. During the March 2026 core update, SE Ranking found 79.5% of top-three URLs shifted positions, up from 66.8% in December 2025. The same pattern is repeating now. Pillar pages with shallow answers and product pages with generic copy are the usual casualties.
Why does schema matter for recovery?
Schema does not directly lift rankings, but it clarifies what your page is to both Google and AI engines. Valid Article schema confirms author, publish date, and topic. During a core update, clean structured data helps Google re-evaluate your page accurately instead of guessing. It is a trust signal, not a ranking hack, and it is fast to fix.
How long should I wait before acting?
Wait at least one full week after Google confirms completion. Google Search Central says this directly. Acting mid-rollout means you cannot tell whether a change helped or whether the algorithm simply settled. For the May 2026 update, that means holding edits until roughly June 11, then reading the data against a clean baseline.
What is the right comparison window for the data?
Compare the two weeks before launch against the two weeks after completion. For this update, that means May 7 to May 20 versus the period after June 4. Pull Search Console clicks and impressions for your top 20 commercial pages only. A page-by-page read beats a sitewide average, which hides the actual winners and losers.
Which schema fields should I check first?
Start with four on every blog post: headline, image, datePublished, and author. Google recommends all four for Article rich-result eligibility. Then verify dateModified reflects real edits and that the author is a Person with a URL, not a plain string. These five fields cover most of what Google and AI engines read for trust.
Should I edit pages during the rollout?
No. Google's John Mueller has repeated this for years: changes made mid-rollout get attributed to algorithm noise, not your work. The exception is fixing a genuine technical break, like a broken canonical or a 404. For content quality, wait. Panic-editing during a rollout usually makes diagnosis harder, not recovery faster.
Where do I confirm the update is actually complete?
Check the Google Search Status Dashboard directly. The incident page for the May 2026 core update updates when the rollout finishes. Search Engine Roundtable and Search Engine Land also post confirmation within hours. Do not trust a single ranking tracker's read. Wait for Google's own dashboard to mark the incident resolved before you start your analysis.
Can I recover before the next core update lands?
Often yes, if the fix is genuine. This was the second core update of 2026, roughly 43 days after March completed. That cadence is tight. Recovery work that improves real content quality can take hold between updates, but cosmetic edits will not. Focus on depth, sourcing, and author credibility, then let the next refresh re-score you.
Will AI Mode change how recovery works?
It already has. AI Mode passed 1 billion monthly users at Google I/O on May 19, and AI Overviews now reach 2.5 billion. Recovery is no longer only about blue-link rankings. You also need answer-first passages and clean schema so AI surfaces cite you. The two goals overlap, which means good recovery work helps both at once.
For the next cycle, my response plan on how Webflow sites should respond to a Google June 2026 algorithm update extends this checklist with the 48-hour wait discipline and recovery signals I now use.
Watching your rankings settle and planning your audit? Pair this with the Day 8 tracking from yesterday, the Day 7 volatility data, and the FAQ schema tutorial for the structured-data side. Let's chat.
Get found, cited and the back office automated
Let's make your site the source AI engines quote and wire up the systems behind it.
Read more blogs
Let's get your website found and cited by AI
Tell me what you're working on, whether AI search is skipping your product, your back office is buried in manual work, or you need a build that does both.