Most teams mirror the ACPA roster into a Google Sheet they own, then point SleekRank at the sheet as a CSV URL. When a team is added, removed, or moves hospitals on the ACPA registry, one row changes and the matching city page refreshes on the next cache cycle. Cache duration is typically 7 to 30 days for this kind of slow-moving directory.

You have two options. Either skip those cities by filtering the source so only rows with one or more approved teams emit pages, or publish a thin page that lists the nearest approved team in an adjacent metro. SleekRank renders only the rows present, so filtering is the cleaner path for medical search where thin pages hurt trust.

Yes. Use two data sources in the same page group: the ACPA-derived approved teams file and a second JSON of solo-practice surgeons by city. The base template references both, listing approved teams first and other surgeons in a secondary section so the page reflects the full local picture.

A meta mapping populates a JSON-LD block in the page head from row fields. You write the schema template once with placeholders for name, address, and medical specialty. SleekRank injects the row's values per page, so each city URL ships valid structured data without per-page editing.

Set the row to inactive or remove it from the source. On the next cache refresh the URL returns 404 and the sitemap drops the entry. If you prefer a soft transition, add a redirect mapping for that slug to an adjacent metro before removing the row.

Yes. SleekRank uses an existing WordPress page as the base template. Build it with the block editor, your theme, and your existing patterns. Mappings target HTML elements by tag, CSS selector, or meta name, so the base page stays editable in Gutenberg and the generated pages inherit every change.

A CPT shines when each entity is the canonical search target. Cleft families search by metro, not by surgeon name, so the city is the canonical page and surgeons are list items within it. SleekRank makes the city the URL and treats surgeons as data rendered inside it, which is the inverse of how a CPT would model it.

Yes. Anything you can add to the base page renders on every generated city page. A Gravity Forms block, a Calendly embed, or a custom block all work. You can also pass row fields into form hidden values via shortcodes so submissions are tagged with the city and the lead surgeon.