Google Algorithm Update Hit Your Site? The Checklist Before You Panic (2026)
Your rankings dropped and Google won't tell you why — here's how to confirm it was actually an update, sit out the volatility window, and avoid the moves that make it worse.
Google confirmed a spam update on 18 August 2026. If your traffic dipped in the last couple of days, there's a real chance that's the reason — not the blog post you skipped last month, not a competitor doing something clever, not bad luck. But most business owners never check. They see the drop in Search Console, assume the worst about their own site, and start making changes based on a guess. That's the expensive mistake. Work through this checklist first, in order, before you touch a single page.
Step 1: Check whether Google actually ran an update
Google publishes every confirmed ranking update — core updates, spam updates, the periodic Discover updates — on its own Search Status Dashboard, with the date each one started rolling out. This is the only source worth trusting. A LinkedIn post calling something "the new Google update" isn't evidence. The dashboard is.
Open your Search Console Performance report, widen the date range to cover the week either side of your drop, and find the day clicks or impressions bent downward. Then check that date against the dashboard. If they line up within a day or two, you've found your trigger, and you can stop guessing.
2026 has had a run of these. A core update started 27 March and took just over 12 days to finish rolling out. Another core update started 21 May and ran just under 12 days. A Discover update in February took 21 days 17 hours. The spam update on 18 August is still rolling out as I write this. None of these are instant — they run over one to three weeks, and rankings can shift the entire time as Google's systems finish reprocessing signals across the update. If your drop started partway through one of those windows, you're not dealing with a mystery. You're dealing with a dated, documented event.
Step 2: Rule out the boring, self-inflicted causes first
Before you assign the drop to Google, check whether you did anything. A code deployment, a plugin auto-update, an accidental noindex tag, a site migration without redirects, a page that quietly got slower — any of these can produce a drop that looks exactly like an algorithm hit but has nothing to do with one. We've written the full diagnostic for telling a site problem from an SEO problem, and it's worth ten minutes before you go further here. If nothing on that list applies and the timing lines up with a confirmed update from Step 1, keep reading.
Step 3: Understand why the first week tells you nothing
This is the part almost everyone gets wrong. Google's own guidance on core updates is explicit: confirm the update has finished rolling out, then wait at least a full week after that before drawing any conclusions from your data. Given that 2026's updates have run anywhere from 12 to 22 days, "wait a week" often means three to four weeks from the day you first noticed the dip to the day your numbers actually mean something.
Inside that window, rankings wobble. A page can drop on day two and partially recover by day nine as Google's systems keep re-evaluating signals across the rollout. Checking your position on day three and concluding "we're finished" is judging a sentence before it ends. The volatility isn't a bug in the process — it's what a staged reprocessing of billions of pages looks like from the outside.
Step 4: What not to do while it's rolling out
This is the step that costs businesses the most, because doing something feels more useful than waiting, and waiting is genuinely the correct move here.
Don't strip page elements because a forum post said they're "bad for SEO." Google's own advice is blunt on this: avoid "quick fix" changes made in reaction to a ranking drop, because they're usually based on incomplete information and can do more damage than the drop itself.
Don't commission a full rewrite of your site's content in a panic sprint. If the update turns out not to be the cause, you've spent money and disrupted pages that were performing fine.
Don't mass-disavow backlinks because someone told you toxic links tank rankings. Disavowing is a blunt instrument Google recommends using rarely, and doing it reactively during an update window makes it harder to tell what actually caused what.
Don't switch agencies, platforms, or your entire content plan off three days of noisy data. Keep operating the business normally. Keep publishing on your usual schedule. The sites that come out of an update window worse off are often the ones that went dark or started thrashing, not the ones that held steady.
Step 5: What to actually do while you wait
Waiting doesn't mean doing nothing. It means collecting the right evidence instead of the wrong one.
Screenshot or export your Search Console Performance report now, filtered to the queries and pages that dropped, so you have a clean baseline to compare against once the update finishes. Note whether the drop is broad — most pages, most queries, roughly the same percentage down — or narrow, hitting a handful of specific pages while the rest of the site holds steady. Broad movement usually means Google re-weighted how it values your site as a whole. Narrow movement usually means a quality issue on specific pages, which is a much smaller, more targeted fix.
Check the split between impressions and clicks in the same report. If impressions held steady while clicks fell, the problem is more likely your titles and snippets losing the click, not the ranking itself. If impressions dropped, Google is showing your site less often, which is the harder problem to fix quickly.
Step 6: When the window closes and the drop is still there
If a full week has passed since the update finished rolling out and your rankings haven't recovered, that's the point where it stops being noise and starts being signal. Per Google's own framing of core updates, a sustained drop usually means the update surfaced something real about content quality, expertise, or usefulness relative to what's now ranking above you — not a technical trick you can patch in an afternoon. Google is equally clear that recovery, where it happens, isn't guaranteed at the next update; some changes take effect in days, others take months for their systems to re-learn and trust the improvement.
This is also where the platform underneath your site starts to matter. A business running on a heavy page-builder platform tends to carry more of the baggage that quality-focused updates target — slow mobile pages, templated content that reads the same as thousands of other sites, technical debt nobody's had time to clean up. We've written about what that actually costs over the life of a site if that's a live question for you. For most businesses it isn't the reason for this particular drop, but for sites that have been limping along on the same platform for years, an update like this one is often the moment the ceiling becomes visible.
The short version
Check the Search Status Dashboard before you blame yourself or the algorithm. Rule out the causes that are actually your fault. Give any confirmed update the full rollout window plus a week before you judge anything. Don't make reactive changes in the meantime. Collect your Search Console data properly so you have something real to compare once the dust settles. And if the drop is still there after all that, treat it as a genuine quality signal worth fixing properly, not a glitch to wait out again.
If you've worked through the checklist and you're still not sure whether you're looking at a passing update or a real site problem, run the free audit. It checks your mobile speed, Core Web Vitals, and on-page issues in under a minute and tells you whether the platform underneath you is part of the story.