Most teams mirror the ACMS find-a-surgeon registry into a Google Sheet, then point SleekRank at the sheet as a CSV URL. ACMS membership refreshes annually as fellows graduate and surgeons retire. When the editor updates the sheet, all 600 city pages reflect the change on the next cache cycle. A 14-day cache is common for this kind of registry.

Yes. The roster row carries a fellowship-trained flag per surgeon. The list mapping renders different badges on each card so patients see at a glance which surgeons completed an ACMS-approved fellowship and which are general dermatologists who perform Mohs. Both audiences are valid but the distinction is decision-relevant.

The page renders cleanly with one fellow card, a hero count of 1, and a link to the nearest higher-density city for patients who want more options. Single-fellow city pages capture long-tail demand that aggregator sites miss, and they answer the specific query patients are typing.

Yes. If the source carries a same_day_reconstruction flag per surgeon or per city, a selector mapping renders a badge on the page header and on individual surgeon cards. Patients who need wound closure in the same surgical session value this signal because it shortens the treatment timeline.

Yes, via a meta mapping that writes JSON-LD into the page head. Each URL ships valid structured data with dermatology and Mohs surgery specialty fields, address, and credentialing. Google reads the schema regardless of card layout, which keeps the SEO surface stable as you iterate visible design.

Treat the suburb as its own row with its own slug. SleekRank emits a page per slug regardless of whether the city is a primary metro or a suburb. Patients searching by suburb name find the right page, and the base template links to adjacent metros for cases that need a higher-density referral path.

Yes. Anything on the base page renders on every generated city page. An intake form built with Gravity Forms or HubSpot appears on all 600 city URLs, with city and lead clinic passed into hidden form values via shortcode so submissions route to the right intake team.

Patients search by city first, not surgeon name. A CPT-per-surgeon inverts the search intent and forces taxonomy archives to recover the city URL. SleekRank gives you the city page directly with surgeons as data inside it, which matches how skin cancer patients actually start their referral search.