Add a ticket_tiers JSON column with one object per tier (name, price, sessions, url) and map it to a list block for human display plus selector mapping into Event JSON-LD's offers array for structured data. Google's event rich results show price ranges for festivals with structured offers data, which moves click-through compared to plain blue links without prices.

Add a featured_bars column with bar slugs comma-separated. The template iterates the list and links each bar to its existing /bars/{slug}/ page if your site runs a bar directory in parallel. Cross-source lookup pulls bar names from the bars data source on render, so the festival page stays in sync as bars are renamed or rebranded.

Set cache duration to one hour during the festival week so editorial updates surface within an hour. Seminar cancellations, room changes, and added late-night activations happen frequently during the run; the short cache window keeps the public page accurate without manual flush after every change.

Yes. Event schema supports subEvent for each day's headline seminar or activation, and Google renders the parent event with date range plus sub-events in the rich results panel. For seven-day festivals like London Cocktail Week, this lets each day's seminar show up in search for queries like LCW saturday seminars.

Move them to /cocktail-festivals/{year}/{slug}/ via an annual archive page group. Archive pages preserve next-year search value because attendees research the prior year's content (winners, photos, lineups) when deciding whether to attend this year. The archive group reads the same sheet filtered to past years.

Add a discounts column with structured codes (early bird, partner hotel, trade) and render them as pill cards via list mapping. Discount codes are commonly affiliate-tracked; selector mapping into the partner URL captures attribution while keeping the discount visible to readers without aggressive popups.

No, per-city pages canonicalize to themselves and link out to canonical festival pages. The per-city pages aggregate link equity for the city-festival facet without competing with per-festival detail pages. Each festival's detail page wins rich result eligibility because it has the structured Event schema and complete data.

Maintain a unified sheet with country and region columns, or pull multiple data sources (one per editorial region) into the same page group. SleekRank handles multiple sources per group, and column normalization lets a European editor's sheet and an American editor's sheet write into the same template fields without rewrites.