Yes. List treatments as an array column. Each treatment-by-city rollup page group filters rows where the treatments array contains its URL parameter, so a spa offering Botox, filler, and microneedling contributes to three Scottsdale rollups from one source row, with no duplication needed.

Edit the supervising_md column on the affected row and flush the cache. The profile, every treatment rollup the spa appears on, and the city page all re-render with the new physician name through the same tag mapping, so credentials never drift between profile and rollup.

No. SleekRank only generates pages from data. Boulevard, Mindbody, Vagaro, and similar booking embeds live on the base page itself and inherit on every generated spa URL. Context like the spa slug can be passed through URL parameters so a single booking widget routes correctly across the whole directory.

Google Sheets, CSV files, JSON URLs and files, REST APIs, and Notion databases. Operations teams running multi-location groups usually pick Notion for typed property fields; editorial directories tend to prefer Sheets so a content lead can edit without touching the dashboard.

Yes. Generated profile, treatment, and city pages are included in the XML sitemap automatically. The base template is auto-noindexed so only the per-row pages compete in search. Each page has its own meta description, h1, and structured content, which is exactly what long-tail "treatment in city" queries reward.

Yes. Build the base spa profile in Bricks, Elementor, Oxygen, or Gutenberg. SleekRank only injects per-row data through tag, selector, list, and meta mappings on render, so existing brand templates, before-and-after sliders, and review widgets carry through to every generated medical spa URL untouched.

Add promo_price and promo_until columns. Render the promo as a selector mapping that swaps a discount chip onto the page when promo_price is set. A short cache duration (one to four hours) means time-sensitive promotions reflect almost immediately and expire cleanly when the column is cleared.

Yes. Add a devices array column listing Sciton, Cutera, Allergan, Galderma, BTL, and similar entries. Run a separate page group at /medical-spas/{device}/{city}/ that filters rows where the devices array contains the URL parameter, so device-specific queries get matched pages from one source.