In early August 2026 a lot of site owners felt their rankings move. Search Engine Roundtable was first to flag unusually high volatility between August 1 and August 3, with Semrush Sensor, Mozcast, Ahrefs and SERPmetrics all spiking at once. One fact belongs at the top, though: Google has confirmed no algorithm update for August, and its Search Status Dashboard recorded no ranking, indexing, crawling or serving incident between August 1 and August 6. The most recent officially confirmed ranking change is still the June 2026 spam update, which began June 24 and completed June 26.

Three Unrelated Things Landed in the Same Window

Before attributing a traffic drop to "the update", rule out the interference that genuinely existed at the time: a GA4 reporting bug (the numbers themselves were wrong), disruption in Google Ad Manager, and a Discover traffic decline that started back in mid-July. All three make a dashboard look bad; none of them share a cause, and none of them share a fix. That is the whole argument for diagnosing first — different causes point in opposite directions.

Diagnostic Order: Start on Your Own Side

Order matters, because the earlier causes are the ones most often mistaken for "the algorithm hit me".

  • Step one, rule out the server: check the 5xx rate and response times for those days. One line gets you the magnitude: awk '$9 ~ /^5/ {print $9}' /var/log/nginx/access.log | sort | uniq -c. If Googlebot met 502s or 504s while crawling, the drop isn't algorithmic — it's failed crawling.
  • Step two, rule out self-inflicted blocking: expired certificate, an edited robots.txt, a firewall or WAF rule that quietly rate-limits Googlebot ranges. Use Search Console's URL Inspection with a live test to see whether Google can fetch the page right now — faster than any amount of speculation.
  • Step three, read Crawl Stats: if average response time rose sharply on those days, or crawl requests fell off a cliff, the problem is on the host.
  • Step four, and only now, look at query data: in the Performance report, compare August 1–10 against July 1–10 broken down by page and by query separately, aligning days of the week — weekend traffic has a different shape. A genuine algorithmic shift usually shows up as one class of pages moving together, not as an even decline across the site.

What Third-Party Trackers Actually Measure

A volatility index measures how much the SERPs moved for that tool's own keyword sample — not for your site. A red index tells you the results as a whole are in motion; it does not imply you were demoted. Treat it as a reading of the background noise level: when noise is high, any single data point is less trustworthy.

The Best Move During Volatility Is Restraint

Rewriting titles, merging pages and mass-deleting content while results are still unstable creates one specific problem: you lose attribution. If rankings recover a week later, you won't know whether your edits worked or the volatility simply passed. Capture a baseline instead, wait for the SERPs to settle, compare, and reserve action for the pages that genuinely stayed down. The published analyses of this round keep naming the same old weaknesses anyway: pages with weak originality, thin firsthand evidence and vague intent fell furthest, and sites leaning on scaled AI content or expired-domain redirects lost visibility fastest. Fixing that doesn't require Google to confirm anything.

Diagnosis Requires Raw Logs

Steps one through three all depend on complete access and error logs. Shared hosting often gives you a truncated stats panel instead: no filtering by User-Agent, no way to see which specific crawl returned a 504. SharkCloud instances come with full root access and raw logs, and with nodes in Japan, Singapore, Hong Kong and the US you can host close to where your visitors are — when you're troubleshooting this kind of question, data you can actually see beats any theory.