People search "Chicago Public Library Sulzer Sunday hours", "NYPL Harlem study room", or "LA Public Library Wilshire computer use". The system website typically answers with a JS branch picker, a single citywide program calendar, and a generic about page. The data is real (each branch has fixed hours, dedicated collections, language services, computer access, meeting rooms, and a kids/teen room) but the indexable web surface for each branch is not.

SleekRank takes the system's branch roster (from the integrated library system, the public-relations roster, or a maintained sheet) and maps each branch to /library/{slug}/. Tag mappings handle the branch name and neighborhood. Selector mappings render the address, weekly hours, computer count, Wi-Fi policy, and a clear curbside or in-person banner. List mappings render languages in the collection, ongoing programs (storytime, ESL conversation, citizenship classes, tax help), and special features (maker space, music studio, business center, teen lounge).

The Chicago Public Library Sulzer Regional becomes /library/chicago-il-sulzer/. The NYPL Schomburg Center becomes /library/new-york-ny-schomburg/. Both render the per-branch data as crawlable HTML, both update on the next cache window, both rank for queries the system-wide branch picker cannot.

Public libraries are one of the most program-rich and most underserved service categories in local search. Each branch runs a unique mix of programs, languages, amenities, and study spaces, and the typical library website hides every bit of that behind a JavaScript branch picker that ranks for nothing in particular. A per-branch corpus with structured programs arrays, language-collection tags, computer access data, and proper Library schema makes each branch findable in the specific shape a real query takes.

The roster also captures the operational reality of a real system: dozens of branches at different scales, each maintaining its own programs and amenities, all of which deserve their own canonical URL. SleekRank treats the system's branch roster as the source of truth and the public site as a render target, so a new program, a renovation closure, or a language-collection expansion flows through every dependent page on the next cache refresh. The downstream impact is real: every branch page connects a resident with a service that is already in their neighborhood, paid for by their taxes, designed to be useful, and currently invisible to search.