Either remove the row after the week wraps, or filter on the endDate column in the page group so SleekRank only generates URLs for upcoming weeks. SleekRank serves whatever is in the cached row, so the source decides what is visible. Past weeks drop from the sitemap on the next cache refresh, and some drinks outlets keep a recap archive that surfaces past weeks for editorial retrospectives.

Add a signatureServes column with comma-separated drink names, or a sub-rows table with drink, bar, price, and recipe. Render via list mapping. Cocktail week pages live on signature-serve discovery, so making the drink lineup scannable above the fold lifts engagement.

Add a wristbandUrl column and inject it into the buy button via a selector mapping. The actual checkout runs in your ticketing platform of choice, whether Eventbrite, DesignMyNight, or a cocktail-week-direct system. SleekRank only handles the SEO landing page, not the cart or payment flow.

Run a second page group with a small bars sheet listing every participating bar, then use a list mapping to render the matching cocktail-week appearances on each bar page. The same cocktail-weeks feed drives per-week pages and per-bar roll-ups, so a bar's full year of cocktail-week participations renders on its own page.

Themed-week formats like Negroni Week and Old Fashioned Week have a single signature serve per event but participating bars across many cities. Add a theme column and run a per-theme page group; participating bars become the rows, with each bar's variation on the theme rendered via list mapping on the theme page.

Embed the official cocktail-week map via an iframe or static image, or run a sub-page per city with a participating-bars list and a centered map. SleekRank does not render maps itself, but it can swap in per-city maps through selector mappings that point at embed codes stored in the source sheet.

Run a sub-rows table with bar, cocktail name, price, and ingredients. Render as a table or list on each cocktail-week page. Some weeks let each bar offer one signature serve; others let bars run a full themed menu, and the column structure should reflect which model applies to each week.

Add a participatingBars column with comma-separated names and render via list mapping. For deeper profiles, run a parallel /bars/{slug}/ page group with bartender names, neighborhood, and signature style, and link from each cocktail-week page to matching bar profiles.