Yes. Each WOD is one row in the workouts sheet plus a few rows in the exercises sheet. A coach can prep a full month of workouts in one sitting and have all the /wod/{slug}/ URLs go live as their slugs become reachable; cacheDuration controls how fresh published rows stay across the day.

Append a row to the workouts sheet with the new slug (e.g. "2025-04-13"), fill in workout_name, format, time_cap, and scaling_label, then add the exercise rows tagged with that wod_slug. Clear the items table or wait for cacheDuration, run wp rewrite flush, and the URL goes live.

Yes. SleekRank renders on top of any WordPress page, including those built with Bricks, Elementor, Gutenberg, or a custom theme. Build the WOD layout once on the base page and SleekRank handles per-row replacements through the mapping system without altering theme files.

Yes. SleekRank emits every generated URL into its sitemap and noindexes the base template page automatically. Submit the sitemap once in Search Console; new workout rows start getting crawled after the next rewrite flush. Indexation quality depends on real prescription detail and unique workout content.

Yes. Carry a layout column on the workouts sheet and use selector mapping to inject or hide template fragments per row. A skill-day WOD can include a technique-video block that a metcon WOD omits, all from one shared base page through conditional mappings.

Delete the row from the workouts sheet and flush the cache. The /wod/{slug}/ URL stops resolving and returns a clean 404. Many coaches keep old WODs published forever as an SEO asset; retire only when a workout has been demonstrably superseded or contains incorrect prescriptions.

Not if each WOD carries a real prescription. The sheet structure forces workout_name, format, exercises, and scaling to be distinct per row; the editorial work of programming a real session and writing scaling guidance is what separates a programmatic WOD archive from a templated calendar stub.

SleekRank handles the page rendering; the logging side typically lives in a separate WordPress plugin or a comments thread on the page itself. The /wod/{slug}/ URL stays stable as a place to land, so any logging system pointing at that URL works the same way before and after a SleekRank rebuild.