Yes. Map pina_status as a tag and climate_specialties as a list mapping so they render as badge rows. PINA renders with the official Diplomate or Member credential icon, climate specialties render with Koppen climate iconography. Both refresh from the sheet on cache.

SleekRank groups the designer sheet by climate_specialties and publishes a hub per climate. Add a URL pattern like /permaculture/climate/{slug}/ and the Mediterranean, humid subtropical, cold continental, marine, dryland, and high altitude hubs appear automatically with matching designers.

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

Yes. Add a pdc_source column with values like Mollison lineage, Holmgren lineage, Hemenway lineage, regional school. Map as a tag and render in a credentials block beneath the main badge. Clients vetting designers often ask which PDC lineage trained them, so surfacing the source aligns the routing.

Update the pina_status cell to expired or remove the value. The page refreshes on the cache window with the membership removed and the designer drops out of any PINA filtered hub. The badge disappears automatically without a sweep across every related page.

Yes. Add a project_types column with values like homestead, market_farm, urban_food_forest, regenerative_ranch, school_garden. Map as a list and render as badges. Different funders and clients require different project portfolios, so surfacing types aligns the qualification path.

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

The cacheDuration in the page group config controls refresh frequency. Permaculture directories typically use 86400 seconds for a daily refresh, which is fast enough for new memberships, climate specialty changes, and project type additions without hitting the data source on every page load.