developers.google.com
Google Search's core updates and your website
Google's official guidance: confirm the rollout window, compare pre- and post-update date ranges in Search Console, and what to do with a large drop in position.
The one GSC action most indie devs skip when a core update hits
When Google's May 2026 core update cut traffic in half overnight, most solo developers immediately started rewriting pages. The real first step is a 15-minute GSC baseline snapshot — without it, you'll spend weeks guessing at root causes.
Google's May 2026 core update started rolling out on May 21 — and within 48 hours, r/seogrowth was full of developers watching traffic cut in half overnight. The usual panic response: rewrite every page, delete thin posts, add breadcrumbs.
None of that helps if you don't know what actually dropped — and by how much, before the algorithm volatility started obscuring the numbers.
The single highest-leverage action for a solo developer hit by a core update isn't a content fix. It's pulling a clean pre-update baseline from Google Search Console before rollout noise makes the data unreadable.
Why the baseline snapshot matters more than you think
Google's Search Console data lags by 48–72 hours and continues fluctuating for the entire rollout window — up to 14 days for major updates. 1
If you wait until "things settle" before opening GSC, the clean signal is already gone. Every day you wait, the pre-update numbers get pushed further back and harder to isolate.
The Digital Applied team, who published a 14-day recovery playbook timed to this exact update, put it bluntly in their Day 1 guidance: 2
"A pre-triage GSC and GA4 snapshot taken on Day 1 is your only clean reference point before algorithmic fluctuation obscures the true drop."
For a solo developer running five or ten pages, this takes 15 minutes. Skipping it costs weeks of guessing at root causes.
Exactly what to pull, and how
Step 1 — Set the comparison window correctly.
In GSC → Performance → Search results, set the date range to the 7 days before May 14 (the pre-rollout spike date, confirmed by 12+ rank-tracking tools). 2 This window predates both the pre-rollout volatility (May 13–14) and the official launch (May 21). Export it.
Then pull the post-update 7-day window (May 14–21), switch to comparison view, and sort Pages by delta in clicks.
Step 2 — Tag every URL that dropped more than 30%.
Pages with a 30%+ click decline are your recovery priorities. For a small site, this list might be 5–15 URLs — workable in a single afternoon. For each one, assign a single issue tag:
- Thin content — under ~500 words, low information gain relative to what ranks above you
- Outdated — stats or guidance older than 18 months
- Weak E-E-A-T — no named author, no primary-source citations, no first-hand experience
- Cannibalization — two of your own pages targeting overlapping keywords
Step 3 — Screenshot your rank positions independently.
GSC's position data lags. Before ranks drift further, take a rank-tracker screenshot of your top-20 keyword positions. A free tool like Google Search itself (in an incognito window) works for this. This gives you a same-day reference that GSC alone won't provide during an active rollout.
リンクプレビューを読み込んでいます…
What to do with the tagged list
The baseline is diagnostic, not corrective. Once you have the tagged list, the fix depends on the tag.
The March 2026 core update — the closest comparable precedent — showed a consistent pattern in Lily Ray's 2,076-domain SISTRIX analysis: 79.5% of top-three URLs shifted positions, and 24% of top-10 pages dropped below rank 100. 3 May 2026 early signals are tracking the same direction.
リンクプレビューを読み込んでいます…
Thin content or outdated pages are the most common cause of core-update drops for indie dev sites with documentation pages or old tutorial posts. 2 Google's own guidance says deleting content is a last resort — but if a page was written for search engines rather than readers, removing it from crawl (via
noindex) can actually help your other pages rank by stopping authority from leaking to dead weight. 1Weak E-E-A-T is where the May 2026 update is hitting hardest in the first 24–48 hours of signals. The pattern from March 2026 — confirmed by Lily Ray's SISTRIX analysis of 2,076 domains at Amsive — was consistent: sites with named expert authorship and first-party experience signals held or gained. 3 For a solo developer, this doesn't require hiring a medical board. It means: put your name on the page, link your GitHub, and add one or two concrete first-hand observations from your own project rather than restating what other guides say.
Cannibalization is often invisible until you run a URL-level comparison. Two posts covering the same topic with 60% keyword overlap will split your click-share. Pick the stronger page and 301-redirect the weaker one to it.
One thing not to do
Google's official guidance on the May 2026 update was brief: 4
"There's nothing new or special that creators need to do for this update as long as they've been making satisfying content meant for people."
That sounds dismissive, but the underlying point is real. Making surface-level changes — adding a publication date where none existed, inserting a word count badge, or swapping the author byline to "Staff Editor" — doesn't fix thin content. Google's systems are looking for accumulated evidence of quality improvement, not individual signals you can flip in five minutes. 1
The baseline snapshot doesn't require you to immediately fix anything. It just ensures that when you do make changes over the next 30–90 days, you know exactly which pages you're recovering — and by how much.
This week's action: Open GSC now, pull the week before May 14 as your baseline, and export the drop list sorted by click delta. Tag each URL with one issue type. The list itself is the work product — the fixes come later.
このコンテンツについて、さらに観点や背景を補足しましょう。