Couch to 5k is a nine-week plan, three sessions per week, twenty-seven sessions in total. Each session is warm-up walk, alternating run and walk intervals, cool-down walk. The intervals follow a graded progression: minute-long runs in week one, eight-minute runs by week six, continuous twenty-minute runs by week nine. The shape is identical across sessions; only the interval pattern, totals, and effort target change.

SleekRank reads a sheet with twenty-seven rows and renders an indexable URL at /couch-to-5k/{slug}/. Tag mappings handle the title (Week 3 Day 2), list mappings render the interval blocks, selector mappings handle the week and effort badge, and meta mappings carry the description and HowTo schema for the session.

Coaches and beginner-running publishers edit the plan source where it lives, in a sheet or JSON file. A row update (an extra walk break, a slower target pace for a deload variant) flows through the entire plan on the next cache cycle. The session card, the indexable page, and any companion app screen all read from the same source.

Couch to 5k search is highly intent-shaped: beginners look up the specific session they are running today. 'Couch to 5k week 5 day 1' is a real query with real volume, and a focused per-session page outranks a single full-plan article every time. The structural problem in beginner-running publishing is that the plan has twenty-seven sessions and they all share the same skeleton.

Writing them as twenty-seven separate posts in the editor is a tax most publishers pay once and never repeat for the slow-progression or treadmill variants their audiences ask for. Programmatic generation removes that tax. The plan lives in a sheet where intervals are easy to compare across weeks, and the WordPress side becomes a layout concern solved once.

Variants ship as new source files, not new editor marathons. Long-tail couch to 5k queries reward publishers who surface every session at a clean URL with consistent structure, complete next/previous navigation, and matching social cards. The data layer becomes the SEO surface, and editorial throughput becomes a row insertion rather than a writing session per page.