Building a Sitemap That Can't Go Stale: A Config-Driven Architecture for Next.js App Router
Building a Sitemap That Can't Go Stale: A Config-Driven Architecture for Next.js App Router Every team that ships a marketing site on Next.js eventually writes the same file: sitemap.ts. It loops over some blog posts, hardcodes a few static paths, and gets shipped without much thought. Six months later, someone notices Google has indexed /dashboard/settings, three new landing pages never made it into the sitemap, and nobody can explain why the homepage and a random FAQ page both have priority: 0
