Pool intent splits by neighbourhood, by amenity, and by audience. "Lap pool in East Austin with adult swim hours" or "family pool with slide in Phoenix" is a specific query that a single parks-department archive page cannot satisfy. The roster already lives in the parks-and-recreation operations sheet or the city facilities database your team maintains for permitting and seasonal staffing.

SleekRank reads that sheet and emits one WordPress page per row. Pool name maps to the H1, neighbourhood goes into title and breadcrumbs, admission fee renders as a badge via selector mapping, and the amenities array flows through a list mapping. Hours columns drive a weekly schedule block that updates on each cache refresh.

Neighbourhood hubs come from the same data. A second page group with /pools/{neighbourhood}/ as the pattern generates per-area pages listing every pool in that district. Closing a pool for renovation drops it from the hub on the next refresh, and the sitemap regenerates clean when the row is removed.

Pool searches are shaped by very specific intersections: neighbourhood plus amenity plus often audience plus seasonal hours. A single parks archive page filtered by query string cannot rank for "lap pool in East Austin with adult-only hours" because Google ranks pages, not parameter strings. The pools that rank carry real specifics: hours, fees, amenity lists, named flagship facilities, district context.

Maintaining that uniqueness across 200 pools by hand is impossible; maintaining it across 200 rows in a parks-ops sheet is a Tuesday. Pool data also moves seasonally: hours shift in May, fees update in January, renovations close and reopen facilities throughout the year. The team that tracks those changes is the parks operations team, not the web team, so manual directories drift within weeks of each season change.

SleekRank inverts that by making the operations sheet the SEO surface. The base page still belongs to WordPress, so accessibility, design, and tracking stay where they always lived. Adding a new facility becomes a sheet row plus a cache flush.

The directory stops lagging the actual roster.