After August Volatility, Check That Migrated URLs Stay at 200 (2026)

Search Engine Roundtable reported another Google ranking-volatility spike on August 12-13, with practitioners describing sharp reversals and traffic changes. Google has not listed an August ranking incident on its Search Status Dashboard, so a ranking swing is not enough evidence to rewrite a page. 1 2

One more concrete failure mode appeared in r/SEO this week: after a .NET-to-Next.js migration, a developer reported that valid URLs sometimes returned 404 until the user refreshed. The only reply pointed to framework fallback settings, case sensitivity, and CDN-cached 404 responses. That thread is one report, not proof of a broad Google cause. It is still a useful boundary for sites with the same migration or delivery symptoms. 3

The one action: prove one valuable URL stays at 200

Use this check when a site recently moved frameworks, changed its hosting or CDN, or has a valid page that occasionally returns 404 or 5xx. Choose one URL that used to earn organic traffic. Do not apply this as a sitewide rewrite or as a universal explanation for August volatility.

Pick one exact URL. Use Search Console's Performance report or your application logs to choose a page that matters. Copy the final URL, including its path and casing. A manually successful browser refresh does not prove that every request receives the same response.
Request the URL five times from a terminal. Replace the example URL with the page you selected:

   for i in 1 2 3 4 5; do
     curl -sS -o /dev/null -w "%{http_code} %{url_effective}\n" --max-time 15 "https://example.com/your-path"
   done

A valid, current page should return 200 on every request and keep the same final URL. A 404, 5xx, unexpected redirect, or changing final URL is a delivery problem to fix before you edit the title or content.

Run Search Console's Live URL Test. Open Search Console > URL Inspection, paste the same URL, and choose Test live URL. Check the page availability and indexing signals in the result. Google documents URL Inspection as the place to test a live page and inspect what Google can access; its JavaScript guidance also says that Googlebot queues pages with a 200 status for rendering, while rendering may be skipped for non-200 responses such as 404. 4 5
Fix the delivery layer that failed. If the same URL changes between 200 and 404, check the route fallback or ISR configuration, whether separate application instances share the same cache, path-case handling after moving from a case-insensitive server, and whether the CDN is caching an intermittent 404. If the page genuinely moved, send the old URL to the new one with a permanent redirect instead of returning an error or building a redirect chain. 6
Repeat the two tests before requesting a recrawl. Keep the terminal output and the Live URL Test result with the date. Request indexing once from URL Inspection only after the URL stays at 200; Google says recrawling can take days to weeks, and repeated requests do not make the same URL crawl faster. 7

How to read the result

Five 200 responses and a successful Live URL Test: the migration-related delivery problem is not supported for this URL. Leave the page unchanged while August volatility remains unconfirmed; a clean test does not prove that an algorithm update caused the traffic loss.
Any intermittent 404, 5xx, or wrong final URL: fix the route, cache, case, or redirect behavior first. Run the same two tests again before touching on-page SEO.
The URL stays at 200, but clicks still fall: this check passed. It does not identify a ranking or search-intent problem, so do not claim a recovery from this test alone.

The immediate win is narrower than a ranking promise: you remove one way a valuable page can become unavailable to Google during a volatile week. Google also makes clear that a recrawl request does not guarantee instant inclusion or ranking recovery. 7

The August 12-13 reports remain practitioner observations, not a confirmed Google update. Use this action only when your site has a migration or inconsistent-response symptom; otherwise, preserve the evidence and avoid changing content on the strength of forum chatter alone.