Yes. The capabilities column is mapped with a list mapping and renders as badges in the page header. Shops carrying multiple capability lines such as channel letters and LED pylons get both badges in the order they appear in the source cell. Per capability hubs use the same column to build filtered landing pages.

Add the shop and its new service city to the roster sheet with the correct city and state values. SleekRank groups by city for the URL pattern, so the new city page appears on the next cache refresh without a developer ticket. The page inherits the base template and capability badges automatically.

Yes. The base template includes a LocalBusiness JSON-LD block with placeholders for company name, service area, phone, and review count. SleekRank fills the placeholders from the row data, so every generated city page ships with valid structured data that search engines can parse for richer snippets.

Yes. Use a ul_listed column with values like yes or no and add a second URL pattern such as /signage-fabricators/ul-listed/{slug}/ that draws from the same sheet filtered by UL status. Each combination gets its own URL with its own H1, copy block, and permit messaging driven by the field.

Update the ul_listed cell in the source roster. The page refreshes on the next cache cycle with the badge removed, and the shop no longer appears in the UL listed hub. To remove the shop entirely, delete the row or set a status column to inactive and filter the page group on it.

Yes. Add columns for permit_assistance, service_radius, and minimum_order. Map each as a tag or selector in the template and the values render in the relevant template block. Buyers comparing sign shops often filter on permit assistance first, so surface it in the page header for the right intent.

Yes. The base template can include a Gravity Forms or Fluent Forms block with hidden fields populated from the row data. The shop slug and service city pass through as hidden form values, so the lead lands in your CRM tagged with the source page automatically without per-page form config.

The cacheDuration setting in the page group config controls refresh frequency. Most signage directories use 86400 seconds for a daily refresh, which is fast enough for UL listing renewals and shop changes without hitting the Google Sheets API or ISA portal on every visitor page load.