Yes. The marble_origins column is mapped with a list mapping and renders as badges in the page header. Shops carrying multiple origins such as Carrara and Calacatta get both badges in the order they appear in the source cell. Per origin hubs use the same column to build filtered landing pages for designers.

Add or update the shop in the roster sheet with the correct nsi_accredited and renewal_date values. SleekRank picks up the updated NSI badge and the renewal page on the next cache refresh without a developer ticket. The page inherits the base template and origin badges automatically.

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

Yes. Use the nsi_accredited column with values like accredited, pending, or none, and add a second URL pattern such as /marble-fabricators/accredited/{slug}/ that draws from the same sheet filtered by accredited shops. Each combination gets its own URL with its own H1 and trust signal copy.

Update the nsi_accredited cell in the source roster to lapsed or none. The page refreshes on the next cache cycle with the NSI badge removed, and the shop no longer appears in the accredited hub. The base record stays live with the updated status and the next accreditation cycle date visible.

Yes. Add columns for sealer_compatibility, template_method, and seam_method. Map each as a tag or selector in the template and the values render in the relevant template block. Designers comparing marble shops filter on sealer compatibility and digital templating first, so surface those fields 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 marble origin carriage pass through as hidden form values, so the consultation request lands in your CRM tagged with the source page and the design intent.

The cacheDuration setting in the page group config controls refresh frequency. Most marble directories use 86400 seconds for a daily refresh, which is fast enough for NSI accreditation renewals and shop additions without hitting the NSI portal or Google Sheets API on every visitor request.