Services

Fix Stale Content, Webhook and Revalidation Issues in Headless CMS and Next.js Stacks

Bring me in when content is not updating from the CMS because webhooks, caches, and route invalidation are no longer agreeing, so published changes are fresh in one place and stale in another.

Fix content not updating from your CMS before stale pages and revalidation failures stop editors trusting what the live site is actually showing.

Typical symptoms

  • Published content is not appearing on the site when editors expect it to.
  • Webhooks fire but the front end remains stale or partially updated.
  • Different routes refresh at different times or not at all.

Likely causes

  • Webhook triggers, route invalidation, and cache layers are not aligned.
  • The system does not clearly distinguish preview freshness from published freshness.
  • Revalidation is happening, but not for the routes or dependencies that matter.

What I look at first

  • Quick check: publish one controlled content change and trace the webhook, cache, and route freshness path end to end.
  • Which content changes fail first and whether the failure is deterministic.
  • How freshness behaviour differs between preview and published routes.

How I help fix this

  • Trace the stale‑content problem across the actual invalidation chain.
  • Prioritise the routes and content types that matter commercially.
  • Support changes that make freshness more predictable and testable.

When to bring me in

  • Bring me in when stale content is eroding editorial or commercial trust in the platform.
  • Bring me in when revalidation exists on paper but behaves differently by route, environment, or content type.

Related project experience

  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 technical articles

Related services

  1. Parent hub

    Headless CMS Integration

    Choose the right CMS operations fix when preview, freshness, or editorial performance has stopped being trustworthy.

  2. Capability

    Headless Architecture Consulting

    Bring in headless CMS consulting when CMS architecture, SEO controls, preview trust, or revalidation decisions are about to lock in operational pain.

  3. Adjacent scenario

    Next.js Draft Mode Preview Fix

    Restore reliable draft mode and CMS preview flows so editors can review unpublished content without fighting cookies, auth, or iframe failures.

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