feat: add average-time SEO landing pages for IRONMAN and 70.3#251
Conversation
Adds two statically-prerendered landing pages targeting evergreen search
queries ("average ironman time", "average half ironman time"):
- /stats/average-ironman-time and /stats/average-half-ironman-time with
medians by age group, gender, and year, percentile table, median splits,
finish-time histogram, and an FAQ section with FAQPage JSON-LD
- Extend scripts/build-search-index.js to emit data/distance-stats.json.gz
(per-distance aggregates) in the same single CSV pass; committed like the
other index artifacts
- Add getDistanceStats() to data.ts and DistanceStats types
- Link both pages from /stats and list them in the sitemap
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DM6tEZaDCx5PQgaxuV8Fh8
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DM6tEZaDCx5PQgaxuV8Fh8
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 34 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (9)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
P1 of the adoption strategy: two statically-prerendered landing pages targeting evergreen head queries ("average ironman time", "average half ironman time", "average 70.3 time by age group") that nothing else on the web answers with this much data.
/stats/average-ironman-timeand/stats/average-half-ironman-time— sharedAverageTimeArticleserver component with:RaceHistogram)FAQPageJSON-LD/courses, and/racesscripts/build-search-index.jsnow also emitsdata/distance-stats.json.gz(2.8 KB, committed like the other index artifacts) from the same single CSV pass — per-distance percentiles, age-group/gender/year medians, and pre-binned histograms clipped to p0.1–p99.9getDistanceStats()indata.ts+DistanceStatstypes/statsnot-found.tsxtitle no longer doubles the| TriTimessuffix introduced by the layout title templateTesting
npm run test: 157/157 pass;npm run lint: cleannpm run build: green — both new pages prerender as fully static (no runtime corpus reads)next start: unique titles/descriptions/canonicals,FAQPageJSON-LD present, sitemap includes both URLs, tables and histogram render with real dataathlete-index,course-stats,aggregate-stats) are byte-identical; onlydistance-stats.json.gzis new🤖 Generated with Claude Code
https://claude.ai/code/session_01DM6tEZaDCx5PQgaxuV8Fh8
Generated by Claude Code