Yes. Store endoscopy capabilities as an array column (ERCP, EUS, ESD, EMR, POEM, capsule). Render them on the profile through a list mapping and filter rollups by capability to publish /gastroenterologists/ercp/{city}/ pages from the same source.

SleekRank reads from Google Sheets, CSV files, JSON URLs and files, REST APIs, and custom WordPress tables. Practice networks often expose PMS data through a JSON endpoint; smaller groups use a sheet maintained by the practice manager.

Store subspecialty as a column (general, IBD, hepatology, motility, advanced endoscopy, pediatric). Rollups filter on it to publish /gastroenterologists/hepatology/{city}/ pages that only include hepatologists from the same source rows.

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, focus, 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. Condition plus city pages match 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 screeningWait column with weeks-to-next-slot. Render it on the profile and let the rollup page sort ascending so patients see the shortest waits first. Set a short cache duration on the rollup so the number stays fresh.

Add a populations column (pediatric, adult, both). Rollups can filter on it to publish /gastroenterologists/pediatric/{city}/ pages that only list providers serving children, from the same source rows.