304 Not Modified
3xx redirect
The cached copy is still fresh according to the validators the client sent, so the server returns no body and the browser reuses its stored version.
Common causes
- The client sent If-None-Match or If-Modified-Since matching the stored ETag or date.
- A CDN revalidates a cached object with the origin.
- The resource genuinely has not changed since the validator was issued.
How to fix it
- Keep ETags stable for unchanged content and change them whenever the body changes.
- Avoid weak or reused validators that wrongly match after a deploy.
- Return 200 with a fresh body when the content really did change.
What it means for redirects and SEO
Not a relocation but a cache validation result: the browser reuses its stored copy and no bytes cross the wire. Handled correctly it speeds up crawling and improves Core Web Vitals. A misconfigured 304 that fires on changed content serves stale pages to users and bots.
Trace a link that returns 304 →