Yes. Map nowra_status as a list and system_specialties as a list mapping so both render as badge rows. NOWRA renders with the official CIDS or IOWP credential icon, system specialties render with diagrams of each system type. Both refresh from the sheet on the cache window.

SleekRank groups the designer sheet by system_specialties and publishes a hub per system type. Add a URL pattern like /septic-design/system/{slug}/ and the mound, aerobic, drip dispersal, Eljen GSF, sand filter, and at-grade hubs appear automatically with the matching designers listed.

Yes. The base template includes a JSON-LD LocalBusiness block. SleekRank fills placeholders from the row data including service area, phone, review count, and price range. Per designer rich snippets render in search results from the same source data without separate plugin configuration.

Yes. Add a project_types column with values like residential, commercial, light_commercial, school, restaurant. Add a second URL pattern that includes project_type as a path segment. The directory generates a URL per designer per project type with H1 copy tuned to the intent.

Update the nowra_status cell to expired in the sheet. The page refreshes on the cache window with the expired credential removed and the designer drops out of any NOWRA filtered hub. The badge disappears automatically without a sweep across every related page or hub.

Yes. Add columns for soil_specialties with values like fractured_bedrock, high_water_table, shallow_soils, clay_loam, sand_gravel. Map as a list and render as badges. Property owners with challenging sites filter on soil expertise first, so surfacing the spec aligns lead routing.

Yes. The base template supports Gravity Forms and Fluent Forms with hidden fields. The designer slug and service state pass into the form submission so leads land in your CRM tagged with the source page. Form routing rules assign each lead to the matching designer or regional team.

The cacheDuration in the page group config controls refresh frequency. Septic designer directories typically use 86400 seconds for a daily refresh, which is fast enough for new credentials, system specialty changes, and state code amendments without hitting the data source on every page load.