Yes. Add a ticket URL column on the show row and map it to the CTA button through a selector or tag mapping. SleekRank does not sell tickets itself; the page renders the link to your existing ticketing platform, whether that's DICE, Eventbrite, AXS, Ticketmaster, or a direct Shopify checkout.

Add a status column. Past shows can either drop out of the sitemap by filtering them at the urlPattern level, or persist with a recap block via a conditional in the base page. The second pattern preserves accumulated backlinks and lets the URL host post-show photos, setlists, or reviews.

Yes. Run additional page groups that read the same calendar feed but apply different group-by logic. /artist/{slug}/ renders all shows for one artist, /venue/{slug}/ renders all shows at one venue, and the original /shows/{slug}/ stays as the per-show URL. One feed, three SEO surfaces, no duplicate data.

Add a support-acts column as a JSON array and surface it through a list mapping on the base page. Lineup additions, drop-offs, or swaps update on the next cache flush, so the page always reflects the working bill rather than the original announcement.

Yes, though many promoters omit them on listing pages because tiers change. If you want prices on the page, add price columns by tier and map them through selector mappings. For dynamic pricing platforms, link to the ticket platform directly and let it surface current prices live, since the SleekRank cache will lag any real-time changes.

Use one row per night with the date in the slug, like /shows/idles-electric-ballroom-london-2026-05-09/ and /shows/idles-electric-ballroom-london-2026-05-10/. The artist index rolls all nights together, and each night has its own URL with its own ticket link and door time.

Yes. Add a genre or tag column on the show row and use sleekRankRelatedEntries to surface related shows at the bottom of each base page. Genre, venue, and city are common filters, and the helper picks up to six related shows deterministically per page to fill the related cluster.

Append a new row to the Google Sheet, save, and clear the SleekRank cache. The URL appears within minutes after the next rewrite-aware cache cycle. Run wp rewrite flush only if you've added a brand-new slug pattern; row additions don't require flushing rewrites, only cache clearing.