Yes. Store subspecialty focuses as an array column with values like ECMO, cardiac_NICU, neuro_NICU, surgical_NICU, transport, BPD, palliative. Each focus-by-city rollup page group filters rows where the focuses array contains its URL parameter, so a multi-focus neonatologist contributes to every relevant rollup from one source row.

Store nicu_level as a column with values Level I through Level IV per AAP definitions. A tag mapping renders the level badge on every page. When a hospital upgrades or downgrades NICU level, one cell edit propagates through the profile, the level rollup, and the hospital page on the next cache flush.

No. SleekRank displays whatever is in the row. ABP verification is out of scope, but a scheduled audit script can compare the certifications column against the ABP public roster and flag mismatches in a status column that the directory then renders as a badge or hides via a conditional selector mapping.

Google Sheets, CSV files, JSON URLs and files, REST APIs, and Notion databases. Most academic NICU divisions run on internal physician APIs surfaced as REST endpoints; smaller perinatal networks usually run on Sheets edited by the division coordinator.

Yes. Generated profile, level, and city pages are included in the XML sitemap automatically. The base template is auto-noindexed so only the per-row pages compete in search. Each page has its own meta description, h1, and structured content matching referral-pattern queries directly.

Yes. Build the base profile in Bricks, Elementor, Oxygen, or Gutenberg. SleekRank only injects per-row data through tag, selector, list, and meta mappings on render, so existing brand layouts, faculty photo crops, and CV blocks carry through to every generated neonatologist page untouched.

Add a transport_program boolean column and an optional transport_role column with values like medical_director, attending, fellow. A selector mapping swaps a visible transport badge onto the page, and a separate rollup page group at /neonatologists/transport/{city}/ filters on the boolean to capture transport-specific referral queries.

Yes. Add fellowship_program and research_focus array columns. Tag mapping renders fellowship on the profile, and list mapping renders research focus as on-page text. Run a /neonatologists/research/{focus}/ rollup if research-focused referrals matter, with rows contributing wherever the research array contains the URL parameter.