Yes. Add a dates column as a JSON array of objects with city, venue, date, doors, presale, and on-sale URLs. A list mapping in the base page renders the array as a city-by-city table per leg. Reroutes are one edit in the sheet, no template change required.

Nest the dates by leg. Each leg can have its own array, and the list mapping renders a section per leg with its own heading. The Songs of a Lost World tour might have separate EU Spring, NA Summer, and AU Fall legs, each with its own date table on the same parent tour page.

Yes. Run a parallel page group at /tour-dates/{slug}/ with a flat feed of one row per night. Each per-date page renders venue, doors, ticket link, and links back to the parent tour URL as canonical, so the tour page accumulates authority while per-date pages capture long-tail searches.

Add columns for presale code, presale URL, VIP package URL, and VIP description. Surface them through selector and tag mappings so each tour page renders the right block in the right state. Presale codes can be conditionally rendered before the presale opens and hidden after using a date-based conditional.

Edit the dates array. Removed dates drop from the grid on the next cache flush; replaced dates appear in their slot. For cancelled-but-not-replaced dates, mark them with a status flag and either strike them through via a conditional or remove them entirely. The base page renders the working schedule, not a frozen snapshot.

Yes. Each date object in the array carries its own ticket URL, so Berlin links to DICE, London links to Ticketmaster, and Mexico City links to Ocesa. The base page renders the right CTA per row without a manual per-city build.

Add VIP package columns at the tour level for tours where the package is uniform, or per-date for packages that vary city by city. Surface them through selector mappings as a separate CTA block. SleekRank does not sell the packages; the link routes fans to your existing fulfilment platform.

Use both artists in the artist field or add a co-headliner column, and surface both through the base page hero and meta tags. The slug can include both names so the URL ranks for either artist-plus-tour query. Many bookers run a single tour page for co-headline routings rather than separate pages per artist.