fix(sitemap): pin <lastmod> to deploy time, not request time - #604
Merged
Conversation
Sitemap runs on force-dynamic (to bypass Next's 2 MB Data Cache limit on the rendered output), which means `new Date()` at module init re-evaluates on every Google crawl. Effect: every URL had a freshly updated <lastmod> each visit, Google flagged the signal as unreliable sitewide and stopped using lastmod for recrawl prioritisation (confirmed behaviour, documented by Gary Illyes publicly). Fix: bake a build-time timestamp via next.config env injection, read it from process.env.NEXT_PUBLIC_BUILD_TIME in sitemap.ts. Stable per deploy, fresh per deploy. Per-bench <lastmod> still uses live bench.lastRunAt as before — that path was already correct.
Flotapponnier added a commit
that referenced
this pull request
Jun 21, 2026
…#605) * fix(sitemap): pin <lastmod> to deploy time, not request time (#604) Sitemap runs on force-dynamic (to bypass Next's 2 MB Data Cache limit on the rendered output), which means `new Date()` at module init re-evaluates on every Google crawl. Effect: every URL had a freshly updated <lastmod> each visit, Google flagged the signal as unreliable sitewide and stopped using lastmod for recrawl prioritisation (confirmed behaviour, documented by Gary Illyes publicly). Fix: bake a build-time timestamp via next.config env injection, read it from process.env.NEXT_PUBLIC_BUILD_TIME in sitemap.ts. Stable per deploy, fresh per deploy. Per-bench <lastmod> still uses live bench.lastRunAt as before — that path was already correct. * release: hold solana-tx-landing-latency off main Bench and its dependent /alternatives + /answers pages held off main while the harness data quality / methodology is iterated on dev. Matches the existing release-hold pattern (see 12bb8a7). Files stay on dev untouched; dev to main merges will need to re-delete or skip. Removed: - benchmarks/solana-tx-landing-latency.yml - alternatives/jito.yml (benchmark: solana-tx-landing-latency) - alternatives/helius.yml (benchmark: solana-tx-landing-latency) - answers/which-solana-rpc-lands-the-most-transactions.yml
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 freeto 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.
Sitemap runs on force-dynamic.
new Date()at module init re-evaluates on every Google crawl, so every URL got a freshly-updated each visit. Google flags lastmod as unreliable sitewide when that happens and stops using it for recrawl prioritisation (confirmed publicly by Gary Illyes).Fix: inject NEXT_PUBLIC_BUILD_TIME via next.config env at build time, sitemap.ts reads it. Stable per deploy, fresh per deploy. Per-bench still uses bench.lastRunAt (already correct, untouched).