Yes. Map top_origins and common_profiles columns with list mappings so they render as badge rows on the city page. Each badge links to the per origin or per roast profile hub URL. Both refresh from the SCA roster sheet on the cache window without editing the city page directly.

SleekRank groups the city coffee sheet by top_origins values and publishes a hub per value. Add a URL pattern like /coffee-roasters/origin/{slug}/ and the Ethiopia, Colombia, Guatemala, Kenya, Burundi and Costa Rica hubs appear automatically with the matching city roasters listed on each hub.

Yes. The base template includes a JSON-LD LocalBusiness block per city with Organization wrappers for the listed roasters. SleekRank fills the placeholders from the row data including roaster count, single origins and SCA member count. The rich snippets render in search without separate plugin configuration.

Yes. Add a process_focus column with values like washed, natural, honey, anaerobic and mixed per city. Add a second URL pattern that includes process_focus as a path segment. The directory generates a URL per city per process with H1 copy tuned to the process style and the cafe buyer intent.

Update the roaster_count and member list cells in the sheet to reflect the change. The city page refreshes on the cache window with the new totals and the closed roaster drops out of any per single origin hub. Closures flow through the same data path without manual archive sweeps.

Yes. Add columns for avg_cup_score, competition_medal_count and barista_champ_count. Map each as a tag and render in a quality block on the city page. Coffee buyers filtering on cup score above 88 see the matching cities first, so surfacing the spec reduces inquiry email volume for SCA chapters.

Yes. The base template supports Gravity Forms and Fluent Forms with hidden fields. The city slug and single origin preference 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 SCA chapter or regional sourcing manager.

The cacheDuration in the page group config controls refresh frequency. Coffee roaster directories typically use 86400 seconds for a daily refresh, which is fast enough for SCA membership updates, new roaster additions and competition results without hitting the data source on every page load.