A triathlon plan has a name, a race distance (sprint, Olympic, 70.3, Ironman), an experience level, a total duration in weeks, peak weekly hours, weekly swim, bike, and run volume, brick session frequency, key sessions per discipline, and notes on taper and race week. The substance shifts from a beginner sprint plan to an advanced Ironman plan, but the structure repeats with discipline.

SleekRank reads a triathlon plans sheet and generates one page per row at /triathlon/{slug}/. Tag mapping handles the title and weeks count, selector mapping fills the distance and level badges, list mapping renders the weekly schedule with swim, bike, run, and brick sessions, and meta mapping carries the description and Plan schema per plan.

Coaches edit the source directly. A peak-week update propagates through one cell. A new plan ships as a new row. The library cross-references swim, bike, run, and brick session pages so each weekly entry links to its own session page.

Triathlon plan queries are highly specific: "sprint triathlon plan 12 weeks beginner," "70.3 training plan 20 weeks," "Ironman finish plan 24 weeks." Each query maps to a particular distance, level, and duration, and a focused per-plan page outranks a generic listicle every time. The structural challenge is volume across three disciplines, because a complete library covers every distance and level combination, plus variants for time goals, returning athletes, and limited-hours plans. Each plan needs a multi-week schedule across swim, bike, run, and brick sessions, with cross-links to individual session pages, and that schedule has to stay in sync as session libraries get updated.

Hand-curating a hundred plans in WordPress invites drift, especially across three disciplines; doing it as data preserves consistency. SleekRank converts the sheet into a publication surface. Coaches own programming, the web team owns layout, and the library grows with the source.

Pair with SleekPixel for OG cards showing distance and weeks so shared links read as intentional.