Yes. Map credentials and service_specialties columns with list mappings so they render as badge rows. ISA credentials render with the official certification icons, specialties render with iconography for risk assessment, pruning, removal, and plant health care. Both refresh from the sheet on cache.

SleekRank groups the arborist sheet by credentials and publishes a hub per credential value. Add a URL pattern like /arborists/credential/{slug}/ and the TRAQ, BCMA, Municipal Specialist, and Certified Tree Worker hubs appear automatically with the matching arborists 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 arborist rich snippets render in search results from the same source data without separate plugin configuration.

Yes. Add a client_types column with values like residential, commercial, municipal, utility, insurance. Add a second URL pattern that includes client_type as a path segment. The directory generates a URL per arborist per client type with H1 copy tuned to the intent.

Update the credentials cell in the sheet to reflect the new credential list. The page refreshes on the cache window with the expired credential removed and the arborist drops out of any credential filtered hub. Renewal cycles flow through the same path without manual sweeps.

Yes. Add columns for crew_size, equipment_owned, and chipper_capacity. Map each as a tag and render in a capability block. Property owners with large removal jobs filter on crew size and chipper capacity, so surfacing the spec reduces qualification calls before estimates.

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

The cacheDuration in the page group config controls refresh frequency. Arborist directories typically use 86400 seconds for a daily refresh, which is fast enough for new credentials, TRAQ requalifications, and service area expansions without hitting the data source on every page load.