Next.js Metadata Not Updating? Here's Why

You update generateMetadata, redeploy, and the old title or image still shows up when you share the link. Here's how to tell whether it's a caching layer or a code mistake.

Reproducible Example

This looks correct but will keep serving stale metadata after a content change:

export async function generateMetadata({ params }) {
  const post = await fetch(`https://api.example.com/posts/${params.slug}`).then(r => r.json());

  return {
    title: post.title,
    openGraph: {
      images: [post.image],
    },
  };
}

The fetch call here is cached by Next.js's Data Cache by default. If post.title or post.image changes in your CMS, this function won't see the new value until the cache revalidates. With no explicit strategy, that can mean not until the next full build.

Why Your Metadata Isn't Updating

The underlying fetch is cached

By default, fetch() inside generateMetadata is cached indefinitely in the App Router. Fix by setting an explicit revalidation window:

const post = await fetch(url, { next: { revalidate: 60 } }).then(r => r.json());

Or opt out of caching entirely for that request:

const post = await fetch(url, { cache: "no-store" }).then(r => r.json());

The route is statically generated

If the route uses generateStaticParams with no revalidation configured, the entire route, metadata included, is baked in at build time. Adding export const revalidate = 3600; at the page level forces periodic regeneration.

A CDN or edge cache is serving the old HTML

Even if your build is correct, Vercel's Edge Network, Cloudflare, or another CDN in front of your app can serve a cached HTML response that predates your fix. Check response headers:

curl -I https://yoursite.com/blog/post-slug

Look for x-vercel-cache: HIT or a similar CDN header. A HIT means you're looking at a cached copy, not your latest deploy.

opengraph-image.ts isn't picking up new data

If you're using the file-based opengraph-image.ts convention, Next.js generates a static image at build time by default. Dynamic content inside it is subject to the same caching rules as any other Server Component, so add explicit revalidation if it needs to stay fresh.

It's actually the platform's cache, not yours

The most common false alarm. Your app can be serving perfectly fresh metadata while Facebook, LinkedIn, or Slack are still showing a preview they cached days ago. Confirm what your server is sending before touching any Next.js code. See our guide to clearing OG cache on every platform.

Step-by-Step Fix Guide

1. Run curl -s https://yoursite.com/page | grep -i "og:" to see what your server actually sends
2. Check for a CDN cache HIT header with curl -I https://yoursite.com/page
3. Add explicit revalidate or cache: "no-store" to fetches inside generateMetadata
4. Force a fresh deploy to rule out a stale build cache
5. Verify the live result with Proovd

Next.js vs. Other Frameworks

Quick Fix Checklist

Frequently Asked Questions