Why Is My Website Showing the Old Version After an Update?

If you deployed a new version of your website but still see the old version, do not immediately assume the deployment failed. The old version can come from several places, including browser cache, CDN cache, hosting cache, DNS pointing to an old server, an incomplete deployment, the wrong production folder, or a service worker.

The fastest way to troubleshoot it is to determine whether the old version is visible only to you or to everyone.

First: Check the Website in a Private Window

Open the website in an incognito or private browser window. If the new version appears there but not in your normal browser, your local browser cache may be responsible. This is one of the quickest tests you can perform.

Test From Another Device

Open the website on another device. You can also test using a different internet connection. If other users see the new version while your computer shows the old one, the problem is probably local caching rather than deployment.

Check Whether the New Files Are Actually Deployed

Before changing cache settings, confirm that the new files are on the hosting server. If your hosting dashboard provides deployment history or uploaded files, check the latest deployment. For a static website, make sure the updated HTML, CSS, JavaScript, and images were actually included.

Check the Browser Network Request

Open developer tools and inspect the page. Look at the Network tab. Reload the page and inspect the requested HTML, JavaScript, and CSS files. If the browser is receiving old files, inspect their cache-related information. This can tell you whether the old content is coming from the browser or the server.

Check for CDN Caching

If your website uses a CDN or reverse proxy, the CDN may have cached the older version. In that situation, your origin server can already contain the new files while visitors continue receiving cached responses. Check the CDN or hosting dashboard for cache controls and purge options. Only purge the cache when necessary.

Check DNS if You Recently Moved Hosting

If you recently changed hosting as well as deploying a new website, check DNS. Your domain may still be resolving to the previous server from some networks. This is different from browser caching. If the domain points to two different hosting environments depending on the resolver, investigate DNS before changing website files.

Check Service Workers

Progressive web applications can use service workers to cache files locally. A service worker can sometimes continue serving previously cached resources even after the website has been updated. If your application uses a service worker, inspect its cache behavior. Do not delete service-worker code blindly because it may be responsible for legitimate offline functionality.

Check Your Deployment Directory

Another common mistake is updating one directory while the server is serving another. For example, you may have built the new version into dist but accidentally uploaded a different folder. Confirm which directory your hosting server actually serves.

A Simple Troubleshooting Order

Use this order: open the website in private browsing, test from another device, test from another network, confirm the latest files are deployed, inspect Network requests, check CDN or hosting cache, check DNS if hosting recently changed, check service workers if your application uses them, and confirm the server is serving the correct directory. This prevents you from making unnecessary changes.

How to Prevent Confusion During Future Deployments

Use a consistent deployment process. After every deployment, confirm the build completed, confirm the correct output directory, deploy the new files, open the site privately, test important pages, check the browser console, and check the Network tab if something looks old. For larger sites, use versioned asset filenames or a deployment system that handles cache invalidation automatically.

FAQ