What Incremental static regeneration (ISR) means
ISR gives you the speed of static pages without rebuilding the whole site when one product or post is updated. It is ideal for large catalogs and content sites on a headless CMS. Editors publish, and the page refreshes shortly after.
Why it matters for your website
ISR keeps pages fast like a static site while letting editors update content without a full rebuild. For large catalogs and content sites, that means quick updates and lower build times. Visitors get speedy pages, and your team gets fresh content.
Example
A furniture retailer's Next.js site uses ISR for product pages. When a price changes in the CMS, that page refreshes shortly after, without rebuilding thousands of others.
Tips
- Choose a revalidation time that matches how often content changes.
- Use on-demand revalidation so CMS updates refresh pages right away.
- Make sure your hosting platform supports ISR fully.
Common mistakes
- Setting revalidation so long that prices or stock look outdated.
- Assuming every host supports ISR the same way.
Questions about Incremental static regeneration (ISR)
What is Incremental static regeneration (ISR)?
A Next.js feature that rebuilds individual static pages in the background after they change.
What is on-demand revalidation?
It lets your CMS or app tell Next.js to rebuild a specific page right away when content changes, instead of waiting for a timer.
Is ISR good for SEO?
Yes. Pages are served as fast, pre-rendered HTML that search engines can read easily, and content stays reasonably fresh.
