Technical Diagnostic
A focused review of affected routes, templates, deployment behaviour, crawl signals, CMS behaviour, performance bottlenecks, or code paths, followed by a prioritised fix plan the team can take into delivery.
Fix Stale Next.js Pages When ISR or Revalidation is Not Working
Content is published, but pages stay stale because cached output, invalidation paths, or deployment behaviour keep old versions live longer than anyone expects.
Fix content not updating and stale pages before ISR or revalidation problems make live freshness unpredictable for teams and users.
Short Answer
ISR and revalidation problems matter because they make live freshness unpredictable. A page may look available, but published content still stays stale for editors, customers, or search engines. A good diagnosis follows one content change from trigger to route update, separates cache issues from dependency issues, and makes freshness behaviour predictable again.
Typical Symptoms
- Published content is not refreshing when ISR or revalidation should update it.
- Some routes refresh and others stay stale for too long.
- Teams no longer trust the live freshness behaviour of the platform.
Likely Causes
- Revalidation triggers and actual route dependencies are out of sync.
- Caching assumptions changed with platform or routing updates.
- The site depends on freshness paths that are not fully represented in the current model.
What I Look at First
- Publish one targeted content change and verify which routes refresh, which stay stale, and how long each path takes.
- Whether the problem is trigger‑based, cache‑based, or route‑dependency‑based.
- How deployment and invalidation paths differ between route types.
How I Help Fix This
- Trace the freshness problem through the actual runtime behaviour.
- Compare the intended invalidation path with the one production actually follows.
- Make content freshness more predictable across the affected routes.
When to Look at This
- When stale pages are undermining editorial or commercial trust in the platform.
- When ISR exists but nobody can explain confidently why some routes refresh and others do not.
What Gets Resolved
- ISR, on‑demand revalidation, tags, cache headers, webhooks, and deployment timing are traced as one publishing path.
- The first real failure is separated from retry noise and downstream symptoms.
- Local, preview, build, and production differences are made visible.
- Environment, config, cache, runtime, and deployment behaviour are checked in order.
- Fixes are prioritised so the team can ship with more confidence.
How This Usually Works
Recovery Sprint
A short, concentrated engagement for a defined technical SEO, performance, CMS, Vercel, migration, or production issue where the business needs the cause isolated and the first fixes moved quickly.
More Specific Service Pages
Next.js Vercel Build Timeout and Memory Fix
Find the route, data, dependency, or asset work that is stretching Vercel builds, then reduce the pressure before releases become unreliable.
Next.js Site Broke After Deploy
Stabilise a Next.js production incident after deploy when the app works locally but the live site is now broken, inconsistent, or only failing against production conditions.
Headless CMS Cache and Revalidation Debugging
Fix content not updating from your CMS before stale pages and revalidation failures stop editors trusting what the live site is actually showing.
Related Services
Headless Architecture Consulting
Headless architecture advice before CMS, content model, preview, revalidation, metadata, schema, media, localisation, and editorial ownership decisions become expensive to reverse.
Next.js Platform Consulting
Senior diagnosis for existing React and Next.js estates where routing, CMS, deployment, SEO, data ownership, and delivery risk have become one platform problem.
Headless CMS Integration
Fix headless CMS operations where preview, publishing freshness, revalidation, metadata, rich text, media, environments, or editor trust has stopped being reliable.
Vercel Deployment Debugging
Debug Vercel deployment paths where local, preview, build, and production behaviour diverge around logs, environment variables, middleware, cache, runtime behaviour, or failing routes.
Related Technical Articles
CMS Content Not Updating in Next.js. CMS Content Not Updating in Next.js
A production runbook for stale CMS content in Next.js, covering webhooks, route dependencies, ISR, cache boundaries, preview, and editor trust.
Why Your Next.js App Router Page is Stale: Cache Tags, Revalidation, and CMS Publishing. Why Your Next.js App Router Page is Stale: Cache Tags, Revalidation, and CMS Publishing
Debug stale Next.js App Router pages with cache tags, revalidation paths, CMS webhooks, preview freshness, dependency graphs, and simpler cache contracts.
Incremental Static Regeneration and CMS Publishing Freshness. Incremental Static Regeneration and CMS Publishing Freshness
How Incremental Static Regeneration affects CMS publishing freshness, including rebuild timing, stale pages, previews, and editorial expectations.
Static Generation with CMS Content and Build‑Time Data. Static Generation with CMS Content and Build‑Time Data
How static generation works with CMS content and build‑time data, including routes, previews, rebuilds, freshness, cache limits, and deployment trade‑offs.
Optimising Next.js Performance with Incremental Static Regeneration (ISR). Optimising Next.js Performance with Incremental Static Regeneration (ISR)
How ISR improves Next.js performance by mixing static speed with controlled freshness, and where it fits best over fully dynamic rendering for changing content.
Caching Strategies for Data Fetching in Next.js. Caching Strategies for Data Fetching in Next.js
Caching strategies for data fetching in Next.js, including force‑cache, revalidation, stale data trade‑offs, and the debugging traps teams hit in production.