Yes. Add a trialStatus column (active accruing, pending, closed) and an indications array. Render them on the profile through tag and list mappings, and let a rollup page group publish /oncologists/trial-active/{cancerType}/{city}/ pages from the same source.

SleekRank reads from Google Sheets, CSV files, JSON URLs and files, REST APIs, and custom WordPress tables. NCI centers usually expose physician data through an internal API; advocacy groups maintain a sheet edited by chapter leads.

Store cancer types as an array column so a physician treating both breast and gynecologic cancers appears on both rollups without duplicate rows. The rollup filters rows where the array contains the URL parameter.

Not on its own. It sets the og:image meta tag to whatever URL you supply via a meta mapping. Pair with SleekPixel for dynamic OG images that render the physician's name, focus, and city onto a templated card.

SleekRank includes generated pages in the sitemap and noindexes the base template automatically. Indexing is up to Google, but each page is a real WordPress URL with its own meta description, h1, and structured content. Diagnosis plus city pages match patient intent directly.

Yes. SleekRank uses an existing WordPress page as the template and rewrites tag content, selectors, list HTML, and meta on render. Any theme or builder works because the base page is a standard WordPress page with all its blocks intact.

Yes. Store oncology type as a column (medical, surgical, radiation, hematology, pediatric) and let rollups filter on it to publish /oncologists/radiation/{cancerType}/{city}/ pages from the same source rows.

The directory renders only public-facing information clinicians publish about themselves: credentials, focus, trial roles, affiliations. There is no patient data on the public pages. SleekRank does not store or transmit anything outside the source sheet you maintain.