Services

Fix Stale Next.js Pages When ISR or Revalidation is Not Working

Use this page if 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.

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

  • Quick check: publish one targeted content change and verify which routes actually 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.
  • Clarify where invalidation is meant to happen and where it really happens.
  • Support changes that make content freshness more predictable.

When to bring me in

  • Bring me in when stale pages are undermining editorial or commercial trust in the platform.
  • Bring me in when ISR exists but nobody can explain confidently why some routes refresh and others do not.

Related technical articles

Selected project context

  1. Nando’s

    Senior software engineer on the UK and Ireland replatform, migrating Nando’s customer‑facing websites from legacy Drupal to a unified headless platform built with Next.js and Storyblok, with a focus on performance, accessibility, and SEO.

    Screenshot of the Nando’s website; part of John Kavanagh's development portfolio.

Related services

  1. Parent hub

    Vercel Deployment Debugging

    Choose the right Vercel production fix when builds, deployments, revalidation, or auth are blocking release confidence.

  2. Capability

    Next.js Platform Consulting

    Bring in senior Next.js architecture support when a legacy platform, older front end, or hard‑to‑maintain site needs migration planning, platform rescue, and clearer delivery direction.

  4. Adjacent scenario

    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.

Tell me what you're seeing

Send me the affected page or route, point me at the code if that helps, and tell me what you expected to happen versus what is happening now. If this connects to a Next.js migration, technical SEO drop, performance issue, launch, or platform move, include that context too. I'll come back with the clearest next step.

Send the details
Skip past clients

Previous Clients