Tracing a stale cached response after a site repair
After a repair, distinguish the deployed response from a stale cached copy. Keep the old and new observations with their timestamps and cache-related headers.
Locate the stale representation
Compare the same URL in a fresh anonymous request and the affected browsing context. Record response status, body version, Date, Age and Cache-Control when present. Treat those fields as evidence to interpret with the operator, not as a complete explanation by themselves. Changing the URL with a query string creates a different request and should be labeled accordingly.
Check the publication boundary
Ask which cache layers serve the route and where the changed content is stored. Use the documented invalidation or expiry behavior for the actual deployment rather than guessing. After a targeted cache action, request the original URL again and confirm its body. A fresh preview URL does not establish that the public custom domain is serving the same version.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Can a hard refresh prove every visitor receives the repair?
No. It provides evidence for that browsing context. Check the public response and relevant caching configuration before making a broader statement.