Yes. SleekRank supports REST API sources, so you can read schedules from systems with public or authenticated APIs and render them with a list mapping. Each schedule row becomes a repeated block on the gym page. Authentication headers are configured per data source, and the API response shape is flexible because mappings target specific JSON paths.

As fresh as your cache duration allows. Set a fifteen-minute cache for fast-moving class times, or flush the cache from WP-CLI on demand. Static fields like address and monthly rate can use a much longer duration to keep the booking API hits low while still letting class times stay current on the public page.

No. SleekRank renders pages from data; it does not handle transactions. Drop your booking provider's widget on the base page and it appears on every generated gym URL. The widget can read the gym slug from the URL if it needs to scope the booking flow to the right location.

Yes. Map og:image to a per-row image URL via a meta mapping, or pair with SleekPixel for templated OG cards that render the gym name, city, and type automatically. SleekRank only sets the meta tag value; the image either comes from your CDN or from a SleekPixel template.

Remove the row and the URL stops resolving on the next cache flush. Manage redirects in your SEO plugin since SleekRank does not handle 301 chains. A safer pattern is to add a closed-status column and filter rollup pages on it, so the gym drops out of listings without breaking inbound links to its profile overnight.

Yes. The base page is a regular WordPress page, so any theme or builder controls layout. SleekRank replaces tag content, CSS selectors, list HTML, and meta tags at render time. Custom blocks, plugin shortcodes, and any visual design on the base page carry through to every generated gym URL.

Add separate columns for day_pass and monthly_rate, then map each to its own element on the page. Some gyms show both, others show only one — leave the cell blank in the sheet and the corresponding selector renders empty. Conditional Twig logic on the base page can hide an empty block entirely if needed.

Yes, with a second page group. Run /gyms/coaches/{slug}/ off a coaches sheet and link from each gym profile via a list mapping that renders coach slugs as anchors. The coach pages reuse the same base-page approach, with their own credentials and class fields rendered from the coaches sheet.