Google May 2026 Core Update: What We're Seeing and What to Do Now

Google confirmed the May 2026 core update on May 21st — just six weeks after March finished. Here's the early pattern: brand-owned content is rising, aggregators are falling further, and the 'original data' signal is now compounding. Here's what SMBs need to know.

Google confirmed the May 2026 core update is rolling out — and the timing alone tells you something important. Only six weeks passed between the March 2026 core update completing on April 8th and this one launching on May 21st. That is the shortest gap between two core updates in recent memory. It is, perhaps, the clearest signal yet that Google is not waiting for the industry to catch up.

If your traffic dropped in late May 2026 and you're trying to figure out whether it's this update, the March update still settling, or something else entirely — you are asking the right question, and this piece will help you answer it.

The rollout timeline and what the faster cadence means

Google announced the update simply: "Released the May 2026 core update. The rollout may take up to two weeks to complete." No companion blog post. No specific guidance. That is typical for core updates, which Google has consistently declined to describe at the level of "this update targeted X."

The two-week timeline puts full rollout around June 4–6, 2026. Anything before that date is early-phase data — patterns are visible but rankings will continue moving. Evaluating your final position before mid-June would be premature.

What the faster cadence means in practice: sites that were still digesting March are now in a compounding situation. A site that lost 20 percent visibility in March and hadn't yet recovered now faces a second evaluation before those recovery signals had time to register. If you are in this position, the priority is structural improvement — changes that affect the March window and the May window simultaneously — rather than quick fixes.

What the early data suggests

We cannot pull live Search Console data for third-party sites, and we are deliberately not citing third-party SERP volatility tools as primary evidence — they measure instability, not confirmed update signals. What we can do is describe the structural patterns consistent with the known March 2026 winner/loser profile, which the May update appears to be continuing.

Continuing to rise: Sites with brand-owned, proprietary content. In the March 2026 analysis, the clearest winners were brands that produced information nobody else could have — original surveys, real client case studies with specific numbers, technical documentation from practitioners with verifiable credentials. That pattern appears to be deepening.

Continuing to fall: Aggregator and comparison pages without independent testing methodology. Travel aggregators, finance comparison sites, and multi-brand review sites were already hit hard in March. Sites that haven't added a methodology layer — explaining how comparisons were conducted, on what timeline, with what criteria — are exposed again.

Newly at risk (early signal only): Generic informational guides in competitive niches. The "how to rank on [platform]" format, "best practices for [category]" format, and similar guides that compile existing knowledge without adding original observation are showing early negative movement in our observation of the space. This is consistent with what Google's systems would do if they are indeed measuring informational novelty at scale.

Why SMBs are in a better position than they might think

This is the part that most of the update coverage gets wrong. The sites losing traffic in the March and May 2026 updates are, disproportionately, large content-at-scale operations. Sites that built traffic by publishing thousands of optimized pages are precisely the sites whose content tends to look the same — because it is the same approach, repeated thousands of times.

Small businesses, on the other hand, have something those sites cannot replicate: genuine first-hand experience. A plumber who writes about the five types of pipe failures he sees most often in Vancouver houses during wet winters has something a content mill cannot invent. A local accountant who publishes the real tax questions her clients bring every February has something no scaled platform can fabricate.

The problem is that most small businesses have not been publishing this content, because they did not know it had value. They were told to blog about generic topics. The advice was often wrong, and the May 2026 update is — slowly, imperfectly, in ways that take months to stabilize — correcting toward the content that actually deserves to rank.

This is the moment for SMBs to start building the content that genuine expertise produces. Not because it will help immediately — it will not. Core update recovery takes cycles, not weeks. But because what you build in the next 60 days positions you for the update after this one.

What to do right now — the honest version

There is a version of this advice that sounds decisive and actionable and is actually useless: "audit all your content, fix your E-E-A-T signals, build author pages, create original research." All of that is true. None of it can be done in a weekend.

Here is what is actually actionable in the next two weeks:

First, do not make reactive changes during an active rollout. The update will be running through early June. If you start changing title tags and restructuring pages now, you will not be able to separate what the update did from what your changes did. Make your list of improvements. Start them after June 6th.

Second, look at your GSC data with honesty. Compare your click and impression data from May 22–28 against the equivalent period ending May 13 (before pre-rollout volatility began). If you have a meaningful drop and it aligns with this window — and you ruled out other technical changes on your end — you are likely in update territory.

Third, identify your best content. What are the pages on your site that contain information nobody else has? Those are your anchors. The goal in the next cycle is to build more content in that direction, not to fix the pages that were always generic.

Fourth, if you have case studies or client results, make sure they are public and detailed. Anonymized results with vague percentages do not do the work that named case studies with specific numbers do. If you have permission to name clients and publish real before/after data, this is the moment to do it. That content is exactly what these updates are rewarding.

On the indexation question

Something worth noting for any site that launched in the past 12–18 months: core update impact can be difficult to separate from indexation debt. Google does not index sites instantly, and a large sitemap that was submitted recently may have far fewer indexed pages than the URL count suggests. Before attributing a traffic shortfall to an algorithm demotion, check your GSC Index Coverage report. If you have 500 pages in your sitemap and 50 are indexed, the primary problem is not the update.

We saw this pattern in our own work on newly launched sites in early 2026. The site:domain search returning only a handful of pages for a site with hundreds of URLs is a sign of indexation debt, not necessarily quality demotion. The fix is different: submit URLs for indexing, build internal links to new pages, and give Google time to process the crawl queue.

The bigger picture: two updates in six weeks

The six-week gap between March and May is worth sitting with for a moment. Google has historically run four to six core updates per year, spaced roughly every two to four months. Two in six weeks is fast.

One interpretation: Google is moving more quickly because the gap between what their systems can detect (low-quality content) and what they were surfacing had grown too wide, and they wanted to correct faster. That is the charitable reading.

Another interpretation: the model-based evaluation tools Google is deploying — the Gemini-based semantic analysis that was first deployed broadly in March — are faster to run and cheaper to iterate on than prior algorithmic approaches. When the evaluation infrastructure is automated, update cadence is no longer limited by engineering capacity. That implies more frequent updates going forward, not fewer.

If that is true — and we think it is at least partially true — the "wait for the next update to recover" strategy becomes less reliable. The gap between updates is narrowing. The window to make changes and have them evaluated is compressing. Sites that are continuously improving have an advantage over sites that react to updates after they happen.

This is, in essence, what licheo's AI SEO specialist was designed to do: make continuous, incremental improvements so that when an update evaluates a site, the improvements are already in place. Not because we knew the May 2026 update was coming on May 21st — nobody did. But because a site that is consistently getting better is not dependent on predicting when the next evaluation happens.

We'll update this analysis as the rollout completes. If you are tracking specific verticals or seeing patterns in your own data, we would be interested to hear about it. The more data points the SEO community shares, the better we all understand what these updates actually measure.

Frequently asked questions

When did the May 2026 Google Core Update start?

The May 2026 core update began rolling out on May 21, 2026. Google said the rollout may take up to two weeks to complete, meaning full impact won't be visible until early June 2026.

What types of sites are most at risk from the May 2026 core update?

Comparison and aggregator sites, generic informational guides without first-hand experience, and template-heavy content clusters are most at risk. Brand-owned, original-data content is showing early positive movement.

How is the May 2026 update different from the March 2026 core update?

The key difference is cadence — only six weeks separated March completion from May launch, leaving many sites no recovery window. The May update appears to be deepening the same signals March introduced: original data, brand-owned sources, and verified expertise.

Should I delete my AI-generated content because of this update?

No. The question is not whether content was AI-generated — it's whether it adds information that couldn't be found elsewhere. AI content built from original data, case studies, or proprietary methodology is not at risk. Generic AI content paraphrasing other sources is.

How long does it take to recover from a Google core update?

Recovery typically takes one to two full core update cycles — meaning the next major update after the one that hit you, which could be 3–6 months away. Structural improvements (original data, author signals, content differentiation) started now position the site for the next cycle.

Put it into practice

Ready to apply this to your own site?

licheo deploys AI specialists that implement exactly the kind of optimisations covered in this article — technical fixes, schema markup, content improvements, and AI search visibility — directly to your website, around the clock. No agency retainer, no manual work on your part.