Yes. The processes column is mapped with a list mapping and renders as badges in the page header. Shops running multiple processes such as vacuum and gas nitriding get both badges in the order they appear in the source cell. Per process hubs use the same column to build filtered landing pages for RFQ intent.

Add or update the shop in the roster sheet with the correct ams_2750_status and audit_date values. SleekRank picks up the updated AMS 2750 badge and the cert renewal page on the next cache refresh without a developer ticket. The page inherits the base template and process badges automatically.

Yes. The base template includes a LocalBusiness JSON-LD block with placeholders for company name, service area, phone, heat treating processes, and review count. SleekRank fills the placeholders from the row data, so every generated city page ships with valid structured data for industrial buyer snippets.

Yes. Use the ams_2750_status column with values like compliant, pending, or not pursued, and add a second URL pattern such as /heat-treating-services/aerospace/{slug}/ that draws from the same sheet filtered by AMS compliant shops. Each combination gets its own URL with its own H1 and qualification copy.

Update the nadcap_status cell in the source roster to lapsed or pending. The page refreshes on the next cache cycle with the badge demoted, and the shop no longer appears in the Nadcap accredited hub. The base record stays live with the updated status and the next audit date visible.

Yes. Add columns for furnace_size, lead_time, and load_capacity. Map each as a tag or selector in the template and the values render in the relevant template block. OEM buyers comparing heat treaters filter on max furnace size and lead time first, so surface those fields prominently in the page header.

Yes. The base template can include a Gravity Forms or Fluent Forms block with hidden fields populated from the row data. The shop slug, city, and process capability pass through as hidden form values, so the RFQ lands in your CRM tagged with the source page and the buyer intent automatically.

The cacheDuration setting in the page group config controls refresh frequency. Most heat treating directories use 86400 seconds for a daily refresh, which is fast enough for Nadcap and AMS 2750 audit renewals without hitting the MTI portal or Google Sheets API on every visitor page load.