Yes. Map top_origins and common_types columns with list mappings so they render as badge rows on the state page. Each badge links to the per origin or per tea type hub URL. Both refresh from the STI roster sheet on the cache window without editing the state page directly.

SleekRank groups the state tea sheet by top_origins values and publishes a hub per value. Add a URL pattern like /tea-blenders/origin/{slug}/ and the China, India, Japan, Taiwan, Sri Lanka and Kenya hubs appear automatically with the matching state blenders listed on each hub.

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

Yes. Add an organic_status column with values like USDA organic, fair trade, biodynamic and conventional per state. Add a second URL pattern that includes organic_status as a path segment. The directory generates a URL per state per status with H1 copy tuned to certification reality and buyer intent.

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

Yes. Add columns for avg_cupping_score, north_american_tea_champ and global_tea_champ. Map each as a tag and render in a quality block on the state page. Tea shop buyers filtering on cupping score above 90 see the matching states first, so surfacing the spec reduces inquiry email volume for STI chapters.

Yes. The base template supports Gravity Forms and Fluent Forms with hidden fields. The state slug and tea 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 STI contact or regional sourcing manager.

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