Google began rolling out its May 2026 core update on 21 May, less than two months after the March 2026 core update finished. The announcement says the rollout may take up to 2 weeks to complete, so for Arabic and bilingual sites the practical advice is the same as always: note the date, keep working normally and leave the analysis until the rollout is over.
What happened
On Thursday 21 May 2026 at 08:43 Pacific time, Google posted a new entry on its Search Status Dashboard announcing the May 2026 core update. The dashboard is Google’s official status page for Search, and it is where the completion note will appear too.
It follows the March 2026 core update, which was released on 27 March and completed on 8 April, according to its own dashboard entry. So some sites will be reading two sets of changes in a short span, which makes careful date tracking more useful than usual.
As I write this on 22 May, the update is still rolling out and Google has not posted a completion note.
What Google said
The announcement is brief:
“Released the May 2026 core update. The rollout may take up to 2 weeks to complete.”
As with every core update, the real guidance lives on Google’s documentation page about core updates. Three statements from it matter most this week.
- Not aimed at particular sites. Google writes that “these changes are broad in nature, and don’t target specific sites or individual web pages.” Nothing in the announcement mentions a language, a country or a type of site, so there is no basis for reading this as an update about Arabic content or any single niche.
- Wait before judging. Google advises “waiting at least a full week after a core update completes before analyzing.” That means your review starts one full week after the completion note, not during the rollout.
- No guaranteed fix. The page also says “there’s no guarantee that changes you make to your website will result in noticeable impact in search results.”
What caught my attention is how close together the two updates landed. The stated window of up to two weeks tells us nothing about the size of the change; it only tells us when to start looking.
By the numbers
| Item | Detail | Source |
|---|---|---|
| Announcement date | 21 May 2026 | Search Status Dashboard, May 2026 entry |
| Announcement time | 08:43 PDT | Search Status Dashboard, May 2026 entry |
| Expected rollout length | Up to 2 weeks | Search Status Dashboard, May 2026 entry |
| Status at publication | Rolling out, no completion note yet | Search Status Dashboard, May 2026 entry |
| Previous core update released | 27 March 2026 | Search Status Dashboard, March 2026 entry |
| Previous core update completed | 8 April 2026 | Search Status Dashboard, March 2026 entry |
| Wait before analyzing | At least one full week after completion | Google core updates documentation |
| Targeting | Broad, not aimed at specific sites or pages | Google core updates documentation |
What site owners should do
My view: a core update is a good time to be boring. Here is a short plan that avoids the usual panic.
- Mark three periods in your reports. Before 27 March, between 8 April and 21 May, and after the May rollout completes. With two core updates close together, clean period boundaries are what make any later comparison meaningful.
- Leave daily swings alone. Movement during the rollout is not a result. Wait for the completion note, then give it at least a full week, as Google advises.
- Split Arabic and English. In the Search Console Performance report, filter by page path, for example /ar/ and /en/, and look at each section on its own. The two can move differently for reasons that have nothing to do with language.
- Look at pages and queries, not only totals. When the time comes, find which pages gained or lost the most. A change concentrated on a few outdated posts calls for a different response than a change across the whole site.
- Review content on its merits. Google’s core updates page points site owners back to its guidance on helpful, reliable, people-first content. Use it to judge your most important pages honestly.
- Keep publishing. Planned articles, fixes and updates can go ahead. Avoid big structural changes, such as redesigns or URL changes, until you can read the data cleanly.
- Skip winner and loser lists. Lists that circulate during a rollout are built from third-party tools and early data. They say little about your site, and Google itself describes the update as broad.
What to watch
The one date to watch is the completion note on the May 2026 dashboard entry. Google says the rollout may take up to two weeks from 21 May, which puts the latest expected completion in early June. Once the note appears, count one full week, then start your comparison using the periods above.
Keep an eye as well on the core updates documentation page. It is the page Google updates when it changes its advice on assessing traffic changes, and it applies to this update as much as to March’s.
We will update this article when Google confirms the rollout is complete.
Sources
- Google Search Status Dashboard, “Released the May 2026 core update” incident entry, 21 May 2026, https://status.search.google.com/incidents/wdAXJk6LRRihEjpzEeWE
- Google Search Status Dashboard, March 2026 core update incident entry, 27 March 2026, https://status.search.google.com/incidents/7eTbAa2jWdToLkraZj5y
- Google Search Central, documentation page on core updates and how to assess them, consulted 22 May 2026, https://developers.google.com/search/docs/appearance/core-updates