There is no hard cap. Libraries with thousands of rows render fine because each page reads its row at request time and caches per the configured duration. Sheets and JSON endpoints scale to large libraries without issue.

Cache duration is configurable per source. For active development, set fifteen to thirty minutes. For a stable library, a day or longer is fine. A manual flush via wp-cli makes urgent edits appear immediately on the next request.

No. The base template is a normal WordPress page. Bricks, Elementor, Gutenberg, and any custom theme work because SleekRank only injects values into the elements you tag. Equipment and level badges render through the theme's existing styles plus the few classes you assign.

Yes. Each generated URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Submit the sitemap in Search Console and new workouts get crawled within hours of cache flush. Equipment-plus-duration queries are searchable territory the structured pages handle well.

Yes. Add equipment-specific blocks the template shows conditionally (band-tension callout for resistance band workouts, dumbbell-weight suggestion for dumbbell sessions). Most home workouts share the same skeleton, with equipment-aware blocks toggled by the row.

Removing the row removes the URL on the next cache cycle. The router returns 404 for that path, and SleekRank drops the URL from the sitemap. Search engines pick up the removal on their next crawl. No orphaned posts to delete in WordPress.

A 15-minute workout page still carries the same supporting blocks (warm-up cues, target-muscle notes, modifications). The body content stays substantial because the template fills in scaffolding from the row's structured fields rather than relying on long intro prose.

Yes. Store the video URL as a column and inject it via selector mapping into a video block in the template. YouTube, Vimeo, and self-hosted MP4 all work. For YouTube, wrap the URL in an iframe embed so the source can stay as just the watch URL.