fix(seo): regenerate bench-published map (new benches stuck at 2025-01-01) - #2271
Merged
Conversation
…he 2025-01-01 floor keyed-rpc-robinhood (live since 2026-08-27) and every bench added since the last regeneration emitted datePublished 2025-01-01 in JSON-LD, the FLOOR_PUBLISHED fallback in src/lib/seo/bench-dates.ts. A datePublished a year before the site existed, next to a dateModified that moves hourly, is exactly the freshness signal the file header warns about. Regenerated with scripts/generate-bench-published.mjs as documented. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CpArutAtXuBb1BVNUDXoYA
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.
src/data/bench-published.jsonfeeds JSON-LDdatePublishedon every bench page and must be regenerated when a bench is added (see the header ofsrc/lib/seo/bench-dates.ts). It was not, so every bench added since the last run emitted theFLOOR_PUBLISHEDfallback: 2025-01-01, a year before the site existed, next to adateModifiedthat moves hourly. The file's own comment describes what Google does with that: "appeared today, churns daily", downranked.Observed on
/benchmarks/keyed-rpc-robinhood(live since 2026-08-27,datePublished: 2025-01-01T00:00:00.000Z) whilebase-rpccorrectly shows 2026-07-03.Regenerated with
node scripts/generate-bench-published.mjs, nothing else touched.🤖 Generated with Claude Code
https://claude.ai/code/session_01CpArutAtXuBb1BVNUDXoYA