A swim session is warm-up, drill set, main set, cool-down. Each set has reps, distance, stroke, target interval, and a focus cue. The total session distance is the sum of all sets, the total time is the sum of all interval blocks. Coaches think in sets; pools post sets on whiteboards; swimmers read sets on lane sheets. The format is consistent because the constraints of the pool make it consistent.

SleekRank reads a sheet with one row per workout and generates an indexable URL at /swim/{slug}/. Tag mappings handle the title and total distance, list mappings render warm-up, drill, main, and cool-down blocks, selector mappings handle the focus cue and target heart-rate zone, and meta mappings carry the description and HowTo schema.

Coaches edit the set library where it already lives, in a sheet, in a planning doc, in a JSON file. A new session ships as a new row. The pool board, the printable card, and the indexable page all read from the same source.

Swim sets are dense, structured, and repetitive in shape. A 2400m threshold session and a 1500m technique session share the same four-block skeleton; only the contents of the blocks change. Hand-writing each session in the editor is a tax that scales with the library size, and coaches who try it tend to abandon the publishing side once the library passes thirty or forty sessions.

Programmatic generation removes that tax. The library lives in a sheet where sets are easy to compare and rotate, and the WordPress side becomes a layout concern that gets solved once. Long-tail swim queries (1500m threshold set, IM sprint workout, pull endurance set) reward libraries that surface every session at a clean URL with consistent structure, and the coaches who ship those URLs from a sheet end up with the SEO authority that drives discovery for everything else they publish, from race-day strategy posts to drill tutorials.