Yes. Store procedures as an array column (PCI, TAVR, AF ablation, MitraClip, LVAD, Watchman, ICD, CRT). Render it as a list on the profile and let a rollup page group filter on it to publish /cardiologists/tavr/{city}/ pages from the same source.

SleekRank reads from Google Sheets, CSV files, JSON URLs and files, REST APIs, and custom WordPress tables. Health systems often expose physician data through an internal API; ACC chapters maintain a sheet edited by the membership coordinator.

Add credentials columns (FACC, FHRS, FSCAI, FSCMR) and render them as badges on the profile through tag mappings. Filterable rollups can also show credentials per row in the rollup table view.

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 per physician, with the name, subspecialty, and city rendered 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. Subspecialty plus city pages target referral 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. Add a hospitals array column. Render it as a list on the profile and use a separate page group to publish /cardiologists/hospital/{slug}/ rollups that filter by affiliation. Useful for systems that want a navigable physician roster per hospital.

Store cities as an array column. The rollup page group filters rows where the cities array contains the URL parameter, so a cardiologist splitting time between two cities appears on both rollups from one row in the sheet.