World Athletics publishes the official record database with ratification dates and progression histories for every event. Editors extract per-event data into a sheet with a slug column and a progression JSON array. SleekRank reads the rows and renders the current holder card plus the progression timeline.

When a record is set but not yet ratified, the row carries a pending_ratification column with the body reviewing the time. A conditional selector mapping surfaces a pending banner on the live page until World Athletics confirms. After ratification, the time promotes to current holder.

Combined events carry a sub_records JSON array with per-discipline numbers and the world record holder for each discipline within the overall performance. The progression timeline still surfaces overall combined-event scores, so the page reads consistently.

Each page carries a unique event, unique current holder, unique value, unique progression history, and unique schema. The shared structure is the template, not the content. Search engines treat athletics event pages as distinct entities.

Set cache duration to 600 seconds during major championships and Diamond League meets so new times reflect on the page within minutes. Outside the championship window, a 24-hour refresh handles routine ratifications and progression edits.

Yes. SleekRank supports JSON file, CSV, Google Sheets, REST API, custom post types, and SQL queries as data source types. A sports data provider can feed the page group from a live records API while smaller outlets stick with a sheet.

Add a category column with values like sprints, distance, throws, jumps. A second SleekRank page group reads the same source filtered by category and renders a per-category hub. The hub auto-updates as new events land in the source.

Update the slug if the event changes substantially, or keep the existing slug and update the event name only. For meaningful event format changes, redirect the old slug to the new slug. SleekRank does not silently leave orphan URLs live.