After a deploy visitors still see old content on Next.js.
Next caches on multiple layers: data cache, route cache, fetch cache and CDN. Flushing one layer is rarely enough.
Try this first
- 1On content change use revalidateTag or revalidatePath, not just a redeploy
- 2Webhook from CMS to a revalidate endpoint
- 3Invalidate CDN cache (Vercel, Cloudflare) explicitly on asset changes
- 4Keep browser-cache headers for HTML short
When to bring us in
Cache strategy turned into patchwork: redesign from Next 16 cache components instead of patches on patches.
See also
- WordPress, plugins and theme have gone 6+ months without updatesOut-of-date WP is the number-one entry for malware. Don't just hit 'update all', back up first.
- Theme update broke the layout or threw a fatal errorThemes overwrite custom CSS on update unless you use a child theme.
- WordPress shows a blank screen after a plugin install or updateWSOD (white screen of death) is usually one crashing plugin. You isolate it.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.