Usually one row per spa with name, slug, city, services array, amenities array, hours, price range, currency, and a description field. SleekRank reads it from Google Sheets, CSV, JSON, REST API, or Notion. Sheets are the most common choice because the marketing or editorial team can update them in place without involving a developer for routine changes.

Yes. Define a separate page group for service pages where the URL pattern is /spas/{service}/{city}/ and filter rows where the services array contains the URL parameter. Glasshouse Spa with services for facials and massages contributes to both /spas/facials/london/ and /spas/massage/london/ from one row, no duplication anywhere in the data.

Every data source has a cache duration, configurable per page group. When prices or hours change, lower the duration or flush the cache to rebuild affected pages. For seasonal price changes that land on specific dates, schedule a cron job to flush the cache, or use a short duration during the transition window so updates propagate quickly.

No. SleekRank only generates pages from data. Booking integrations, forms, or scheduler embeds come from your theme or other plugins on the base page itself. Whatever you place on the base page renders on every generated spa URL, so a single booking widget configured once appears across the entire directory.

Map the og:image meta tag to a URL field in the row through a meta mapping. Pair with SleekPixel if you want generated images templated from the spa name, city, and primary service rather than hosting one image per spa. SleekRank only sets the tag value; the image source is up to you.

Yes. The base page can be built in any builder. SleekRank replaces tag content, CSS selectors, list HTML, and meta tags at render time, so the visual design, custom blocks, and plugin shortcodes on the base page all carry through to every generated spa URL untouched. Bricks, Elementor, Oxygen, and Gutenberg all work.

Yes. Store currency in its own column and price range as a number range, then concatenate them in a Twig template on the base page or in a derived column on the sheet. The price renders correctly per spa without hardcoding any currency assumptions, and the same approach handles tax-inclusive vs exclusive variations across regions.

Add a status column with values like open, seasonal-closed, or permanently-closed and filter rollup pages on it so closed spas drop out of city and service rollups during off-season. The profile URL can either return the seasonal-closed page itself or 404 — pick the behaviour with a row filter on the profile page group.