Yes. Map rpa_status as a tag and system_specialties as a list mapping so they render as badge rows. RPA renders with the official CRD or CHD credential icon, system specialties render with iconography for hydronic, electric, snow melt, and Warmboard. Both refresh from the sheet.

SleekRank groups the installer sheet by system_specialties and publishes a hub per system type. Add a URL pattern like /radiant-floor/system/{slug}/ and the hydronic, electric, snow melt, and Warmboard hubs appear automatically with the matching installers listed and linked to their detail pages.

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 installer rich snippets render in search results from the same source data without separate plugin configuration.

Yes. Add a project_types column with values like new_construction, slab_retrofit, joist_retrofit. Add a second URL pattern that includes project_type as a path segment. The directory generates a URL per installer per project type, each with its own H1 and copy tuned to the intent.

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

Yes. Add columns for authorized_boiler_brands and authorized_manifold_brands. Map each as a list and render in the system spec block. Buyers comparing radiant floor quotes ask which boiler and which manifold the installer uses, so surfacing the spec reduces qualification calls.

Yes. The base template supports Gravity Forms and Fluent Forms with hidden fields. The installer 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 installer or regional team.

The cacheDuration in the page group config controls refresh frequency. Radiant floor directories typically use 86400 seconds for a daily refresh, which is fast enough for new credentials, PEX brand authorizations, and territory expansions without hitting the data source on every page load.