Wherever the people maintaining the directory prefer. SleekRank reads from Google Sheets, CSV files, JSON URLs and files, REST APIs, and Notion databases. A sheet works well for most networks because admins can edit it directly without a CMS login. For larger organisations, an admin tool exposing a JSON endpoint keeps the directory and the internal database in sync without manual exports.

Yes. Define separate page groups for therapists, modalities, and cities. The same row contributes to whichever pages it qualifies for through the URL pattern and any row filters. Anna Rivers can show on her profile, the deep-tissue Portland rollup, and the Portland city page from one row without duplicating data anywhere in the source.

Each data source caches for a duration you set, configurable per page group. When the sheet changes, you can wait for cache expiry or clear it from WP-CLI so the next request rebuilds the page. For low-frequency updates like license renewals, a one-day cache is fine; for accepting-clients status that changes weekly, set a shorter duration.

SleekRank does not generate images. It can set the og:image meta tag to whatever URL you provide via a meta mapping. Pair it with SleekPixel if you want dynamic OG images per therapist, with the name, modality, and city rendered into a templated card. Otherwise, host one image per therapist and reference its URL in a column.

SleekRank includes generated pages in the sitemap and noindexes the base template automatically. Indexing itself is up to Google, but each page is a real, crawlable WordPress URL with its own meta description, h1, and structured content. Long-tail queries like "prenatal massage Denver insurance" are exactly the kind of intent these pages target.

Yes. SleekRank uses an existing WordPress page as the template and replaces tag content, selectors, list HTML, and meta on render. Any theme or builder works because the base page is a normal WordPress page, with all its blocks, shortcodes, and theme styles intact across every generated URL.

Yes. Add an insurance column with an array of accepted panels and render it with a list mapping on the profile page. Add a parallel page group filtered by insurance to publish /massage-therapists/insurance/{panel}/{city}/ rollups, so a searcher looking for sports massage with Aetna in Austin lands on a page that filters the directory by all three criteria.

Store cities as an array column instead of a single value, then let the city rollup page group filter rows where the array contains the URL parameter. The therapist appears on every city page they list, and their profile shows all current locations through a list mapping. Travelling practitioners no longer need duplicate rows in the source.