Fix users still seeing the old version after I deploy | Vovy
Vovy checks which layer is serving the stale copy, browser, service worker, CDN or DNS, and clears the right one so everyone gets your latest deploy.
I deployed but people still see the old version of my site
How it works
- Confirm the new deploy is live: Vovy checks Vercel Deployments to confirm the latest build is marked Current and assigned to your domain.
- Test without your cache: It loads the site in an incognito window and does a hard refresh with Cmd+Shift+R to see if the old version is only in your browser.
- Check for a service worker: In DevTools under Application, it looks for a service worker, often added by PWA templates, that keeps serving old files offline.
- Purge the CDN if needed: If Cloudflare sits in front of Vercel, Vovy can purge its cache, and it explains why double caching causes this. It asks first.
- Show which layer was stale: You get a card showing each cache layer, which one held the old copy, and the setting that stops it happening again.
What you provide
- Your live URL
- Cloudflare access if you use it
What you get
- The stale layer identified
- Cache cleared safely
- A fix so it doesn't repeat
FAQ
Why can't I just tell users to refresh?
Sometimes that works, but a service worker or long cache header can keep serving old files even after a normal refresh.
Does purging Cloudflare slow my site?
Briefly, while the cache refills from your host. It is safe and usually recovers within minutes.
Should I put Cloudflare's proxy in front of Vercel?
Vercel recommends against proxying through Cloudflare because it adds a second cache and can break things. DNS only is usually the better setting.
Related tasks
All tasksLoading...