The May 2026 Google Core Update: What Changed and What to Do If You Got Hit

The May 2026 Google core update finished rolling out in early June with significant volatility. Here's how to diagnose impact and recover.

The May 2026 Google Core Update: What Changed and What to Do If You Got Hit

The May 2026 Google core update started rolling out on May 21 and finished in early June. Volatility was significant across most verticals. Four signals carried more weight than in previous core updates: E-E-A-T was applied more aggressively, Core Web Vitals now require passing all three thresholds for a ranking boost, original-source content was rewarded more strongly, and product schema gained additional weight in commercial queries. If your site lost traffic, the recovery playbook starts with diagnosis, then content, technical, schema, and originality work in that order.

What Google actually changed

Google's official communication described the May 2026 update as a "broad core update," the term they use for ranking system overhauls that aren't tied to a specific feature like reviews or helpful content. Reading between the lines of the announcement and the volatility patterns reported by major rank trackers, four themes emerge.

E-E-A-T weighted more heavily

Experience, expertise, authoritativeness, and trust have been part of Google's quality framework since 2014. The May 2026 update appears to weight them more aggressively, especially for YMYL queries (your money or your life: finance, health, legal, safety) but also extending into commerce and services.

The practical signal: sites with thin author credentials, missing about pages, no editorial process, or weak corporate signals lost ground. Sites with strong author bylines, named editorial teams, and clear corporate ownership held or gained.

Holistic Core Web Vitals scoring

Core Web Vitals have been a ranking factor since 2021, but the historical scoring let you pass with two out of three thresholds. After May 2026, all three thresholds must be met for the ranking boost: LCP under 2.5 seconds, INP under 200ms, and CLS under 0.1.

Sites that previously squeaked by with strong LCP and CLS but weak INP lost the boost. Sites that pass all three gained.

Original-source content rewarded more

Google has been increasingly explicit about preferring original sources over aggregators, syndication, and AI-rewritten content. The May 2026 update sharpened that preference.

Original reporting, original research, original product photography, original case studies, and first-hand expertise are gaining ground. Reformatted summaries of other sites' content are losing.

Product schema rewarded

For commercial queries, sites with comprehensive, accurate product schema gained visibility in both standard results and AI Overviews citations. Sites missing product schema or with incomplete data lost shelf space.

How to diagnose if you were hit

Look at three sources in order.

Google Search Console

Open GSC and pull traffic data for the four weeks before May 21 and the four weeks after June 7 (the rollout window). Compare:

Total clicks. A drop of 15% or more is meaningful. Under 10% is likely noise.
Total impressions. Impressions falling indicates lost rankings. Clicks falling while impressions hold steady indicates a CTR issue (often AI Overviews, not core updates).
Average position. Position drops on key queries are the clearest signal of a core update hit.

Filter by query and page to find the heaviest losers. Pages that dropped 5+ positions on multiple commercial queries are your priority list.

Third-party rank trackers

Pull data from Semrush, Ahrefs, or a similar tool. Compare keyword ranking distributions before and after. Look for:

The number of keywords in positions 1 to 3
The number of keywords in positions 4 to 10
Total estimated organic traffic value

Third-party tools often catch ranking changes faster than GSC, which has a delay.

Traffic patterns

Open GA4 and compare organic sessions, conversion rate, and revenue from organic for the same windows. If sessions dropped but conversion rate held, you lost informational traffic but kept commercial intent. If conversion rate dropped too, the loss is across the funnel.

The recovery playbook, in order

Recovery from a core update isn't a single fix. It's a sustained effort across multiple dimensions, prioritized by what the update appears to reward.

Priority 1: Content audit

Start with the pages that lost the most traffic. For each:

Is the content original, or does it summarize other sources? Rewrite to add first-hand perspective, original research, original data, or original commentary.
Is the author credible? Add a real byline. Link to an author bio with credentials, experience, and contact info.
Is the content current? Update statistics, examples, and references to current standards.
Does the page answer the query better than competitors? Pull the top 3 ranking pages and ask honestly whether yours is more useful, more specific, or more thoroughly researched.

Don't rewrite for the sake of rewriting. Identify the gap and close it.

Priority 2: Technical performance

Run the Core Web Vitals report in GSC. Identify the pages that fail any of the three thresholds. Prioritize fixes in this order:

1. INP fixes (because it's the threshold most sites fail). Audit JavaScript-heavy interactions, third-party scripts, and event handlers.

2. LCP fixes. Optimize hero images, preload critical resources, audit server response time.

3. CLS fixes. Reserve space for ads and embeds, set explicit dimensions on images.

Test on real mobile devices, not just Lighthouse. Field data in GSC is the authoritative signal Google uses.

Priority 3: Schema and structured data

For commercial pages, audit product schema. Required fields for the May 2026 standard:

name, image, description, sku, brand, offers (with price, priceCurrency, availability)
aggregateRating and review (where applicable)
shippingDetails and returnPolicy (newly weighted higher in 2026)

For non-commercial pages, audit Article and Organization schema. Make sure author, publisher, datePublished, and dateModified are present and accurate.

Validate everything in the Rich Results Test before declaring it done.

Priority 4: Originality signals

For pages that compete in informational queries:

Add original photography (phone-shot from your office is better than stock)
Include original quotes from named experts (your team counts if they have real expertise)
Publish original data: surveys, internal research, customer studies
Cite your sources with named experts, named publications, and dates

Google's systems can detect original-source patterns. Sites that consistently produce them gain trust over time.

How long recovery takes

Core update recovery typically takes one of three shapes:

Partial recovery in the next update. If you fix the obvious issues quickly and the next core update lands within 3 to 6 months, you'll see partial recovery. Full recovery usually takes one or two more cycles.
Slow recovery between updates. If your fixes are content and quality focused, you may see gradual recovery as Google reassesses pages on regular crawl cycles. This is slower but more durable.
No recovery. If the underlying site quality is fundamentally weak (thin content, scaled production, low expertise, weak technical health), no amount of patching will restore the rankings. The work is a rebuild, not a recovery.

Plan for 6 to 12 months of sustained work, not a 30-day fix.

What not to do

Don't redirect away losing pages to other pages. If you redirect a hit page to a healthy page, you transfer the negative signal too.
Don't disavow your way out. Disavow files are for spammy inbound links, not core update recovery.
Don't pile on more AI-generated content. If thin content was part of the diagnosis, more thin content makes it worse.
Don't change everything at once. Make focused changes, measure impact over 4 to 6 weeks, and learn from the result.

Frequently asked questions

When did the May 2026 core update finish rolling out?

Google announced the start on May 21, 2026, and reported completion in early June, with most volatility settling by June 7.

How do I know if my traffic loss is from the core update or something else?

Check whether the drop aligns with the rollout window (May 21 to June 7). Drops outside that window are likely caused by something else: AI Overviews expansion, seasonal patterns, technical issues, or a different algorithm update. Within the window, the core update is the most likely cause.

Will my rankings recover automatically?

Sometimes, but rarely fully. Most recoveries require active work on content quality, technical performance, and originality. Sites that wait passively typically don't recover, because the underlying issues haven't changed.

How long should I wait before making changes?

Don't wait. Start the audit immediately, prioritize the heaviest losers, and ship the highest-impact fixes within 30 days. Recovery takes time, but the clock doesn't start until you make real changes.

Are Core Web Vitals really a ranking factor now?

Yes, and the May 2026 update tightened the scoring so that all three thresholds (LCP, INP, CLS) must pass for the ranking boost. Sites that previously passed two of three lost the boost.

What if my site wasn't affected by the May 2026 update?

If you held steady or gained, you're doing the right things. The audit work above is still worth doing as preventive maintenance, because the same signals will matter in the next core update.

Bottom line

The May 2026 core update rewarded E-E-A-T, holistic Core Web Vitals, original-source content, and product schema. If you got hit, run the diagnosis through GSC and rank trackers, then work the recovery playbook in order: content audit, technical performance, schema, originality. Plan for 6 to 12 months of sustained work, not a quick fix.

*Want help diagnosing core update impact and planning recovery? Book a call with us.*

The May 2026 Google Core Update: What Changed and What to Do If You Got Hit