304 Not Modified

SEO

304 Not Modified is an HTTP status code returned when a client, such as a browser or a search engine crawler, asks whether a resource has changed since its last visit and the server confirms it has not. Instead of sending the full page again, the server sends a short response and the client reuses its stored copy.

Key Points

  • 304 responds to conditional requests using headers such as If-Modified-Since or If-None-Match.
  • The server confirms the content is unchanged and sends no body.
  • It saves bandwidth and server resources for browsers and crawlers.
  • Correct ETag and Last-Modified headers are required for it to work reliably.
  • A 304 should never be returned for content that has actually changed.

Practical Example

A large news site configures correct Last-Modified and ETag headers. When Googlebot revisits older articles that have not changed, the server returns 304 Not Modified, reducing server load and allowing crawling resources to focus on new and updated articles.

Why It Matters

For large websites, efficient caching helps search engines crawl what matters. Returning 304 for unchanged pages reduces server load and can support better crawl efficiency. The risk is misconfiguration: if a server returns 304 for updated pages, search engines and users may keep seeing outdated content.

Frequently Asked Questions

Does Googlebot support 304 Not Modified?

Yes. Google has documented that its crawlers support HTTP caching with conditional requests, which can reduce load on servers.

Is 304 an error?

No. It is a normal, successful response indicating that the cached version is still valid.

Related Terms

Sources

  1. IETF, HTTP Semantics, RFC 9110, Section 15.4.5 (304 Not Modified), https://httpwg.org/specs/rfc9110.html#status.304
  2. Google Search Central, Overview of Google crawlers and fetchers, https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers

← All terms in SEO Full glossary