304 Not Modified

304 Not Modified is an HTTP status code a server sends when a browser or crawler already holds the current version of a URL. The response has no document body; the client reuses its stored copy. The URL still exists, and the stored version is current.

What a 304 response means

A browser or crawler that has fetched a URL before can send a validator with the next request, usually If-None-Match (an ETag) or If-Modified-Since. If the file on the server is the same, the server answers with status 304 and an empty body instead of sending the HTML again.

The empty body is the point of the status. The client already has the page and should render that copy. A 304 is a successful cache check: the URL exists, and the stored version is still the right one.

How 304 differs from 404 and 410

A 404 means the server cannot find that URL. A 410 means the URL was removed on purpose and should be dropped from the index. A 304 means the opposite: the URL is still there, and the cached copy is current. Search engines keep the URL indexed and skip downloading the document again.

A soft 404 is a separate failure. The server returns 200, but the page looks blank or like a “not found” message, so Google refuses to index it. Do not answer a missing URL with 304. Use 404 or 410 for pages that are gone, and use 304 only when a real cached copy is still valid.

Why it matters for crawl budget

Googlebot sends cache validators too. A 304 lets it confirm a page is unchanged without spending bandwidth on the full HTML, which leaves crawl budget for new and updated URLs.

That only works when the crawler already has a stored copy. A 304 with nothing to fall back on teaches the crawler nothing about the URL. Keep cache headers on stable pages you want in the index, and answer removed URLs with 404 or 410.

Related Terms

Put this into practice with KarmaLinks, an AI backlink exchange platform where verified websites trade do-follow backlinks through safe ABC-only triangular exchanges.