May 2026 core update at a glance
The first move after a Google core update: compare dates in GSC before rewriting anything
The May 2026 core update is rolling out now. Before rewriting a single page, open GSC Performance, switch to Compare mode, and build the triage list that tells you which pages actually moved — and by how much.
The May 2026 core update started rolling out on 21 May 2026 1. The rollout takes up to two weeks, which means the dust may not settle until early June.
If your traffic dropped, the reflex is to start rewriting. Resist it — at least for now. Google's own recovery documentation 2 is explicit: wait until the rollout is confirmed complete, then look at the data before you touch anything. The single most actionable thing you can do this week is set up a date comparison in Google Search Console that shows you exactly which pages and queries were affected — and by how much.
Why the comparison view matters
Most developers check their GSC traffic graph and see a dip. That tells you something happened, but nothing about where to focus.
The Performance report's Compare mode lets you set two date windows side by side — for example, the 7 days before the update started (14–20 May) versus the 7 days after (21–27 May). The result is a table sorted by change in clicks, impressions, average position, or CTR. You get a ranked list: page 1 dropped from position 3 to position 18; page 2 is untouched; page 3 actually gained.
That list is the real starting point. Without it, you're guessing which content to fix.
Google's own introduction to Search Console covers the fundamentals of the Performance report:
コンテンツカードを読み込んでいます…
How to set it up
- Open Google Search Console and select your property.
- Click Performance → Search results in the left sidebar.
- In the date picker at the top, switch from the default view to Compare. Set the first period to the 7 days before the update began and the second period to the 7 days after. 3
- In the metrics row, enable Average position in addition to Clicks (it's off by default).
- Switch the table dimension to Pages. Sort by "Difference" on the position column — largest drops to the top.
- Once you have the pages, switch the dimension to Queries and filter by each affected page to see which search terms drove the traffic before, and which ones stopped.
This gives you two concrete lists: the pages that moved and the queries that stopped converting. That's the triage foundation.
What to do with the triage list
Google distinguishes between two types of drops 2:
| Drop size | What it usually means |
|---|---|
| Small (e.g. position 2 → 4) | Normal fluctuation during rollout. Don't change anything yet. |
| Large (e.g. position 4 → 29+) | A signal worth investigating with the content self-assessment below. |
For pages with large drops, Google recommends running the content through their self-assessment questions 4. The ones that catch most indie dev sites:
- Does the page provide information that goes beyond what's obvious, or does it mostly summarize other sources?
- After reading the page, would the user need to search again to get a complete answer?
- Is the content written primarily to attract search traffic, or because you (or your users) genuinely needed it?
The last question has the most predictive power. Pages that existed primarily to capture a search term — not because they represented real first-hand knowledge or a genuine use case — are the ones most likely to take large drops in core updates.
統計カードを読み込んでいます…
One constraint: wait for the rollout to finish
This comparison only produces reliable signal once the update finishes rolling out 2. While the rollout is active, rankings are still shifting. Running the comparison mid-rollout may show you temporary volatility rather than the final settled state.
Recent core updates have rolled out between 12 and 45 days 5. Most finish within 2 weeks:
チャートを読み込んでいます…
What not to do in the meantime
Google's guidance explicitly warns against "quick fixes based on speculation" — removing structured data, rewriting titles wholesale, adding word count, or any other change based on rumors about what the algorithm prioritizes 2. Those changes add noise to your site's signal and make it harder to attribute improvement or continued decline to anything specific.
The one thing worth doing right now is setting up the comparison view so you're ready to analyze once the rollout ends. Everything else can wait a week.
Next week: once you have the triage list, how to use GSC's Query report to spot the difference between "I lost rankings" and "I lost clicks because of zero-click search features."
このコンテンツについて、さらに観点や背景を補足しましょう。