Whatever you put in the data source. SleekRank only renders fields you map, so private notes, internal scheduling, or sensitive client-facing data can stay out of the source entirely or be excluded from the mappings. The directory should only contain data you want public. For HIPAA-relevant workflows, keep the public directory and the clinical record system fully separate, with the directory pulling only the public-facing roster columns.

Yes. Add an insurance column with an array of accepted panels and render it with a list mapping on the profile page. For network sites, add a parallel /therapists/insurance/{panel}/{city}/ page group filtered by panel so a searcher looking for an Aetna-accepting EMDR therapist in Denver lands on a page filtering all three. The same row contributes to specialty, panel, and city rollups simultaneously.

It is as fresh as your cache duration allows. For status that changes weekly, set a short duration like one or two hours and flush the cache when the sheet changes for immediate updates. For static fields like credentials, a longer duration is fine. Setting per-page-group cache durations means the accepting badge can refresh frequently while license credentials stay cached for a day to keep page rebuild costs low.

No. SleekRank generates pages from data; it does not handle form submissions or scheduling. Intake forms come from your theme, a forms plugin like Gravity Forms, or an embedded scheduler like Calendly or SimplePractice on the base page. Whatever you place on the base page renders on every generated profile URL, so a single form configured once works across the entire directory with the therapist context passed via URL or hidden fields.

Yes. Generated pages are real WordPress URLs in the sitemap. The base template page is auto-noindexed so only profile URLs appear in search. Each page has its own meta description, h1, and structured content. Long-tail queries like "EMDR therapist Denver waitlist" or "complex trauma specialist Portland" are exactly the intent these pages target with high relevance and accurate availability data.

Yes. Build the base profile page in any builder. SleekRank replaces tag content, selectors, list HTML, and meta on render, so the design, blocks, shortcodes, and theme styles on the base page carry through to every generated profile URL. Bricks, Elementor, Oxygen, Gutenberg all work the same way. The only requirement is that the elements you want mapped have stable selectors or class names the mappings can target.

Add a license_expiry column and a status column. Filter rollup page groups on status so therapists with lapsed licenses drop out automatically when the expiry date passes. A scheduled job can update the status column based on expiry dates without manual review. The profile URL itself can either return a notice or 404 by adding a status filter to the profile page group, depending on how you want lapsed providers handled.

Yes. Add a telehealth column with a boolean or a region array, then create a /therapists/telehealth/{state}/ page group filtering rows where telehealth is true and the licensed_states array contains the URL parameter. Telehealth providers naturally span multiple states, so this rollup pattern surfaces them where their licensure allows them to practise without duplicating their data per state in the source.