revalidation-strategy-planner

Revalidation interval depends on how often your data updates and how fresh content needs to be. Analyze your data sources' update frequency—static content can use longer intervals or ISR, while frequently-changing data may require SSR or shorter revalidation periods. The Skill examines your routes and data-fetch patterns to recommend specific intervals.

SSG pre-renders pages at build time for maximum performance; ISR revalidates pages on a schedule or on-demand after initial build; SSR renders pages per-request for real-time data. Choose based on content freshness needs: static content uses SSG, semi-dynamic uses ISR with cache tags, and personalized or live data uses SSR or streaming.

Cache tags label rendered content so you can revalidate specific routes without waiting for scheduled intervals. The Skill identifies which routes and data sources benefit from cache-tag assignments, then outputs concrete tag recommendations so you can trigger revalidation when underlying data changes.

Yes. Static pages use SSG, detail pages typically use ISR with appropriate revalidation, list pages may use ISR or SSR depending on update frequency, and personalized content requires SSR. The Skill analyzes each route's characteristics—data freshness, update patterns, and dynamic segments—to recommend the optimal strategy per route.

Dynamic routes and personalized content cannot use pure SSG; they require SSR or ISR with streaming for performance. The Skill detects dynamic route patterns and data-fetch dependencies to recommend whether SSR, ISR with revalidation, or streaming best fits your use case.