Store artist or filmmaker names as an array per festival. List mapping renders them as cards or links. Profiles themselves can live elsewhere or as another SleekRank page group; the link is just the slug or external URL. If a headliner drops out, it's a sheet edit, not a content audit, and the change propagates on the next cache cycle.

Yes. Some festivals run several touring stops or have spring and autumn editions. Add an editions array column with date and city per edition, and the template renders each edition as its own block. For festivals where each edition warrants its own URL, treat each as its own row with a year suffix in the slug.

No. SleekRank renders the festival info page; ticket links typically point to external ticketing platforms. Store ticket tier names, prices, and URLs in the sheet, and selector or list mappings render the tiers on the page with proper outbound links. Ticketing logistics stay with the festival's existing payment provider.

Yes. Each generated URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Submit the sitemap in Search Console and new festival pages get crawled within hours of cache flush. Festival queries are seasonal but evergreen across years, which makes deep festival catalogs especially rewarding to maintain.

Yes. Maintain language-specific columns (description_en, description_es, description_fr) or separate sources per language. For multilingual travel sites, separate sources usually scale better because translators work in isolation. WPML or Polylang handles URL routing alongside SleekRank's slug-based generation.

Store hero image URLs and gallery arrays in the sheet, inject hero via selector mapping and gallery via list mapping. Festival photography is high-impact, so CDN-hosted images perform best. For SleekPixel-rendered OG cards, pull festival name, year, and location into a templated card so social previews stay consistent across the catalog.

Yes. Add a status column (upcoming, current, past) and filter or label sections accordingly. The current-edition block renders prominently on the page, while past editions collapse into a recap section. Refresh the status column annually as part of the editorial calendar; the change propagates across the entire festival catalog on a cache flush.

Add a stages or programs array, each entry with name, capacity, and a sub-lineup. List mapping renders each stage as its own block on the festival page. For very large festivals (Glastonbury's hundred-stage scope, for instance), nest an array of arrays and template the rendering through a partial that handles depth gracefully.