Key takeaways
- If the page and its files are current, leave the 304s alone. Turning caching off to get rid of them makes the site slower and fixes nothing.
- A WordPress site can have four or more separate caches: the browser, a caching plugin, the host’s server cache or reverse proxy, and a CDN. Kinsta’s docs say purging the server cache does not necessarily clear the CDN.
- Test in a private window first, purge only the layer holding the old copy, and test again while logged out. If the page is still old, compare ETag, Last-Modified and Cache-Control.
- WooCommerce stores should keep caching and exclude Cart, Checkout and My Account, as WooCommerce’s developer docs list.
- The WP Super Cache warning about missing 304 responses refers to Expert mode’s lack of browser-side 304 checks. Server caching still works.
You open the browser’s Network tab, a crawl report or a server log, and see a row of 304s next to your stylesheets, images and pages. It looks like a fault. It usually means caching is doing its job.
304 Not Modified is how a browser or cache confirms that the copy it already has is still current. People usually search for it for a different reason, though: they edited something and the old version keeps showing up. That is a real problem, and it lives in a specific cache. Our guide to finding why a WordPress page is not updating covers the wider version of that symptom. This article is about the 304 itself, and how to tell whether it means anything.
A 304 means the copy you already have is still good
A 304 is a successful answer to a question. The question is a conditional request: the browser already holds a file, so it sends a validator along with the request. That is either an If-None-Match header carrying the file’s ETag (a version token) or an If-Modified-Since header carrying a date. If the server finds the file unchanged, it replies 304 with no body, and the browser reuses its stored copy.
RFC 9110, the HTTP standard, defines 304 as a response to conditional GET and HEAD requests that carries no content. MDN’s 304 reference describes it the same way: the server has no need to send the resource again. The WordPress Advanced Administration Handbook goes further and treats it as a goal. Its page on caching says browser caching lets the server return more 304s instead of sending unchanged files again.
So the useful question is not “how do I remove the 304”. It is “does the visitor see the right page?” If they do, there is nothing to fix.
How 304 differs from 200
A 200 sends the full file. A 304 sends only headers and tells the client to use what it has. A 200 does not prove the content is fresh, either. A page cache can return a perfectly successful 200 containing last week’s HTML. The status code tells you how the file arrived, not whether it is the right file.
When a 304 actually points at a problem
A 304 for a file that has not changed is correct. A fault exists only when the file did change and some layer still treats the old version as current. The causes below are listed roughly in the order sources most often suggest checking them. Nobody has measured how often each one occurs.
1. Your own browser is holding the old copy
Open the page in a private window or a different browser. If the update shows there, the problem is local to your normal browser, and clearing its cache fixes it for you. WordPress.org’s “I make changes and nothing happens” FAQ warns that an ordinary refresh may not clear the browser cache. Try the private window before you wipe your whole browser cache, since that also throws away useful data.
2. The caching plugin is serving HTML from before your edit
Plugins such as WP Super Cache, W3 Total Cache, WP Rocket, LiteSpeed Cache and Breeze save finished pages. Logged-in editors usually bypass that saved copy, which is why you see the new version in the editor while visitors get the old one. Purge the affected URL from the plugin’s toolbar or settings, then check the page while logged out.
3. The host has its own cache you did not know about
Many hosts run a server cache or a reverse proxy such as NGINX in front of WordPress, and it does not care what your plugin does. In one W3 Total Cache support thread, changes took a few hours to appear. Disabling the plugin did not help. The cause was a separate GoDaddy host cache, and clearing that fixed it. Look in your hosting dashboard for a “clear cache” or “purge” control.
4. The CDN still has the old file
Cloudflare, QUIC.cloud and host-run CDNs keep their own copies at the edge. Kinsta’s server caching docs say its server cache and CDN cache are separate, so purging one does not necessarily clear the other. Purge the specific URL at the CDN as well.
5. The change is not where you think it is
The same WordPress.org FAQ lists a cause that has nothing to do with caching. The change was never published, was uploaded to the wrong file, or was made at a different address from the one you are viewing. A child theme, a staging copy or the www versus non-www address are common versions of this. Check it before you purge anything.
6. A validator says “unchanged” when the file changed
This is the one case where the 304 itself is the visible symptom. The server or an intermediary generates the same ETag or Last-Modified value for a file that has changed, so every conditional request gets “not modified”. Purging will not fix it for long. Someone with access to the server or CDN configuration has to correct how validators are generated or invalidated.
How to check what is answering, step by step
Work from the outside in and change one thing at a time. You need nothing more than a browser for the first steps. Purging a host cache needs your hosting dashboard, and fixing validator rules needs server access.
- Confirm the symptom. Note the URL, what should appear and what appears instead.
- Test in a private window. If it is correct there, the issue is your browser.
- Open DevTools, then Network. Reload and click the stale file. Under Headers, look at the status,
ETag,Last-Modified,Cache-ControlandAge, plus any header naming a cache, such ascf-cache-statusorx-litespeed-cache. - Purge the narrowest thing you can. Start with the single URL in the layer the headers point to.
- Test again while logged out. Editors often bypass page caches, so your own view proves little.
- Compare validators. If a changed file still returns 304 against an old
ETag, you are in cause 6.
From a terminal, you can see the same headers without the browser’s own cache getting involved:
curl -I https://example.com/wp-content/themes/your-theme/style.css
curl -I -H 'If-None-Match: "the-etag-you-recorded"' https://example.com/wp-content/themes/your-theme/style.css
The first command shows what the server sends today. The second asks the server the same conditional question the browser asks. A 304 there for a file you know has changed is the evidence a host or developer needs.
Why “clear everything” is a poor first move
Purging every layer at once often works, but you learn nothing about which layer was stale, so the problem returns next week. It also leaves every cache cold. In a W3 Total Cache thread from a busy, frequently edited site, the owner reported about 1,200 ms for an uncached page against about 20 ms cached. The advice given there was to preload the cache from a sitemap after purging. On a small brochure site a full purge costs little. On a busy store or a client site, purge one layer at a time.
Cases that look like 304 problems but are not
WooCommerce carts and accounts showing the wrong content
If shoppers see someone else’s cart or an old checkout, the fault is page caching on pages that must stay dynamic. A 304 is not the cause. WooCommerce’s guide to configuring caching plugins says to exclude Cart, My Account and Checkout from the cache, and notes that many caching plugins already do. Keep caching on and add the exclusions. Turning caching off for the whole store fixes nothing the exclusions would not fix.
WP Super Cache says your site does not support 304
The warning is about a 304 that is missing. It does not mean server caching is broken. The WP Super Cache FAQ explains that 304 browser checks work in Simple mode but not in Expert mode. In Expert mode, pages are still cached on the server. Switch to Simple mode only if browser-side revalidation matters to you.
A plugin shows visitors a “304 error”
If a form or plugin shows the word “304” to users, do not assume the caching plugin caused it. In a Breeze support thread, Easy Form Builder showed a “304 error” on a second form submission. The developer traced it to how the form handled authentication rather than to Breeze. Report it to the plugin’s developer with the steps to reproduce it.
A 304 sitting next to a broken page
When something breaks, the Network tab fills up with 304s for files that are fine. In forum reports about failed licence activations and broken homepages after updates, a 304 appeared alongside the problem without causing it. Look for the red rows, such as 4xx and 5xx responses, and for console errors. If you find a 500, our guide to fixing a server error 500 is the better place to start.
Do 304s hurt SEO or speed?
No. Google’s documentation on how HTTP status codes affect its crawlers treats 304 as a signal that the content has not changed, and Google reuses the version it crawled before. A rising 304 count in Search Console crawl stats is not a fault on its own. Check whether Google sees the current content, and leave correct 304s alone.
For speed, a 304 is cheaper than a 200 because nothing is downloaded again. The browser still has to contact the server, though. Long cache lifetimes, which let the browser skip that contact entirely, are faster still. The tradeoff is freshness, and versioned file URLs handle it. WordPress adds a ?ver= parameter to enqueued scripts and styles for this reason. If you are tuning caching for performance, our guide to speeding up a WP site safely covers the host and plugin side.
When to stop and get help
Stop purging when the private-window test, a URL purge in every layer and a logged-out check all fail. Also stop if the headers show a changed file still validating as unchanged, or if the stale copy is in a host or CDN cache you cannot reach. At that point, send your host or developer the URL, what changed, when you purged each layer and the response headers you saw. That turns a vague complaint into a short job. Do not edit .htaccess caching rules or turn caching off site-wide because you saw a 304.
If you would rather not trace this yourself, SiteSelf’s agent can track down the stale layer on your site on request. It needs hosting (SSH) access to inspect headers and server caches, and it reports what it checked and what changed.