sitemap: route.ts handler with explicit Cache-Control (fix P0 leftover) - #1483
Merged
Conversation
Next Metadata routes ignore next.config.ts headers() — the previous sitemap.ts left Next in charge of the response headers and hard-coded Cache-Control: public, max-age=0, must-revalidate on force-dynamic sitemaps. Every crawler hit re-ran the full loader chain (x-vercel-cache: MISS observed on prod 2026-07-26 after PR #1473 landed the config-level attempt). Confirmed by curl: my next.config /sitemap.xml rule was silently dropped. Move the builder logic to src/lib/sitemap-builder.ts and add a Route Handler at src/app/sitemap.xml/route.ts that returns a raw Response with: Content-Type: application/xml Cache-Control: public, s-maxage=3600, stale-while-revalidate=86400 Same builder logic, same buildFullSitemap + buildStaticFallback, just serialized to XML in the route and shipped with a real edge cache header. Also drop the now-redundant /sitemap.xml rule from next.config headers().
Flotapponnier
added a commit
that referenced
this pull request
Jul 26, 2026
Next Metadata routes ignore next.config.ts headers() — the previous sitemap.ts left Next in charge of the response headers and hard-coded Cache-Control: public, max-age=0, must-revalidate on force-dynamic sitemaps. Every crawler hit re-ran the full loader chain (x-vercel-cache: MISS observed on prod 2026-07-26 after PR #1473 landed the config-level attempt). Confirmed by curl: my next.config /sitemap.xml rule was silently dropped. Move the builder logic to src/lib/sitemap-builder.ts and add a Route Handler at src/app/sitemap.xml/route.ts that returns a raw Response with: Content-Type: application/xml Cache-Control: public, s-maxage=3600, stale-while-revalidate=86400 Same builder logic, same buildFullSitemap + buildStaticFallback, just serialized to XML in the route and shipped with a real edge cache header. Also drop the now-redundant /sitemap.xml rule from next.config headers(). Co-authored-by: Florent Tapponnier <contact@mobula.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1473
The #1473 attempt to set /sitemap.xml Cache-Control via next.config headers() was silently ignored — Next Metadata routes emit their own headers that override the config layer. Post-deploy verification (2026-07-26 03:30 UTC) showed sitemap still returned
public, max-age=0, must-revalidatewithx-vercel-cache: MISS.Fix
Convert to a Route Handler that returns a raw Response with the header we want:
src/app/sitemap.tstosrc/lib/sitemap-builder.ts(rename default export →buildSitemap)src/app/sitemap.xml/route.tsserializes to XML + setsCache-Control: public, s-maxage=3600, stale-while-revalidate=86400/sitemap.xmlentry from next.config.ts headers()Same builder logic, same fallback path, same content. Only the transport changes.
Test plan
curl -sI https://openchainbench.com/sitemap.xmlshowss-maxage=3600, stale-while-revalidate=86400andx-vercel-cache: HITon the 2nd request