Most teams maintain a mirror of the AHPBA directory in a Google Sheet, then point SleekRank at the sheet as a CSV URL or REST endpoint. When AHPBA refreshes membership, the editor updates the sheet and 200 city pages reflect the change on the next cache cycle. Cache durations of 14 to 30 days are common for slow-moving rosters.

The page still renders cleanly. List mappings show one surgeon card instead of three, the hero badge shows a member count of 1, and the page links to the nearest higher-volume city as a related option. Single-surgeon city pages are valuable because they answer the specific query that family is typing.

Yes. Run two SleekRank page groups against the same roster with different filters. The pancreatic surgeon group filters to rows where pancreatic-procedure flag is true. The HPB-general group includes all members. Each group has its own URL pattern, base page, and mappings.

Yes, via a meta mapping that writes JSON-LD into the page head. The schema template references row fields for name, address, specialty, and hospital affiliation. Each city URL ships valid structured data that matches Google's MedicalBusiness expectations, generated from the same template that drives the visible content.

Set the row to inactive or remove it from the source. SleekRank returns 404 on the next cache refresh and removes the URL from the sitemap. For closed transplant programs you usually keep the URL as a 301 redirect to the nearest active program, which a simple redirect mapping handles.

Yes. Anything that lives on the base page renders on every generated city page. A Gravity Forms or HubSpot referral form on the base page appears on all 200 city pages, with row fields like city and lead hospital passed into hidden form values so submissions are tagged with context.

A custom post type indexes each surgeon as a canonical entity, which is the wrong unit of search for HPB care. Patients search by city, not by surgeon name. SleekRank flips the model so the URL is per-city, surgeons are data within the page, and the directory matches how patients actually search.

Yes. SleekRank supports multiple data sources per page group. Pair the AHPBA roster as the primary source with a hospital case-volume JSON as a secondary source, joined on hospital name or NPI. The base page can render both surgeon cards and hospital volume tables side by side.