Page groups with several thousand generated URLs run on one base template without issue. Most franchise locators sit in the low thousands; most independent groups stay under a few hundred. The practical ceiling is hosting and crawl budget, not the plugin.

Yes. Edit your Google Sheet or push to your REST endpoint, then clear the SleekRank cache from the admin or via WP-CLI. No theme deploy, no static rebuild. Many groups set a one hour cache during enrollment season and a longer one off-peak.

Yes. SleekRank uses an existing WordPress page as the template, so Bricks, Elementor, Gutenberg, Oxygen, and classic themes all render correctly. The directory inherits whatever your site already looks like.

Each generated URL is a real WordPress page with full HTML and ships in the sitemap. The base template page is auto-noindexed so it never competes with the generated children. New rows typically index within a few crawls of the sitemap update.

Yes. Branch a mapping on a tier or category column, or run multiple page groups against subsets of the data with their own base templates. A common pattern: a richer template for flagship locations and a leaner one for express clubs.

Remove the row from the sheet and flush the SleekRank cache. The club URL stops resolving (returns 404), the neighborhood and amenity hubs drop it, and the sitemap regenerates. Configure a redirect in your normal WordPress redirects plugin if you want to send traffic to a nearby sister location.

Make the data carry the difference. Per-club amenities, class formats, equipment list, neighborhood landmarks, and a unique paragraph column all vary per row. Avoid copy-paste descriptions that swap only the location name, because Google detects that pattern quickly.

Yes. Use a multi-source page group: a Google Sheet for the editorial content (description, photos, amenities) and a REST API for live class schedules. Mappings target each source independently, so the static fields cache longer than the live schedule data.