Yes. Add HowTo JSON-LD to the base page once and inject step text, total time, and tools via selector or meta mappings sourced from the row. ExerciseAction is a less-supported type, so HowTo with structured steps is usually the safer SEO play. Validate with the Rich Results Test once and trust the structural pattern: every /exercises/{slug}/ ships consistent schema because both visible content and JSON-LD pull from the same columns.

Carry progression and regression columns with pipe-separated slugs. List mapping renders them as real internal links to /exercises/{slug}/. Each entry can carry both the slug and a display name separated by a delimiter so the link text reads naturally. Reciprocal linking is structural: if A lists B as a progression, B's row references A as a regression through the same column.

Yes. Carry a video_url column with the canonical YouTube URL. Selector mapping injects it into an iframe src on the base page. For lazy loading, wrap the iframe in a click-to-load shell on the base template so the embed only loads on interaction. SleekRank delivers the URL, the template owns the loading strategy.

Both live as columns. Render muscle and equipment as pills via selector mapping. Run secondary page groups under /exercises/by-muscle/{slug}/ and /exercises/by-equipment/{slug}/ that filter the same sheet by the relevant column. The result is multiple URL trees over one canonical exercise library, with each entry point ranking for its specific intent.

SleekRank generates the exercise pages. Workout builders, sets and reps trackers, and progressive overload tools live in your app, JS layer, or plugin. The exercise pages link out to or embed those tools as needed. The plugin's job is canonical movement reference content, not workout programming logic.

No, that is a coaching responsibility. SleekRank only places content into the template. Form descriptions, common mistakes, and safety notes come from your trainers or content team and should be reviewed by a qualified coach before adding rows. Pair with SleekAI to draft initial copy, but never publish exercise instructions without subject-matter review.

Add a status column with values like current, deprecated, archived, and filter the page group to only render current rows. Set up 301 redirects via your redirect plugin from deprecated URLs to current alternatives. The deprecated row stays in the source as historical record, useful for editorial audits even though it no longer renders a page.

Yes. Configure a rest_api source pointing at the public endpoint. Cache the response generously since the structured data rarely changes day to day. Map fields like name, description, muscles, and equipment into the template via selector or tag mappings. SleekRank handles the JSON traversal so nested fields are addressable directly. You can also blend an API source with editorial overrides via a sheet for movements you want to differentiate.