Either remove the row after the event runs, or filter on date in the template by comparing the date column to today at render time. SleekRank serves whatever is in the cached row, so the source is the source of truth. Some sites keep a /events/past/ archive page group that reads the same data filtered to past dates, which preserves SEO value from historical events without cluttering the live collection pages.

Add a ticketUrl column and inject it into the buy button via a selector mapping. The URL can deep-link to Ticketmaster, DICE, RA, Eventbrite, a WooCommerce product page, or any ticketing platform. Ticketing and payment run in your ticketing platform; SleekRank does not handle the transaction itself. Most events use specialized ticketing platforms because seat selection, refunds, and barcode scanning at the door require dedicated tooling.

Yes. Add Event JSON-LD to the base template and use selector or tag mappings to inject row values into the script tag. Required fields like name, startDate, location, and offers map cleanly to columns. Event rich results in Google search show name, date, venue, and a buy-tickets link directly in the SERP, which moves click-through significantly for searches like comedy show Amsterdam tonight where multiple sites compete.

Either add one row per occurrence with its own date and slug, like /events/jazz-night-berlin-april-12/ and /events/jazz-night-berlin-april-19/, or run a single evergreen page per series with the next date as a column. The first approach gives every occurrence its own SEO page and historical archive; the second consolidates link equity onto a series URL but loses the per-occurrence SEO. Most sites pick per-occurrence for one-off events and evergreen for weekly residencies.

Run a second page group with a small types sheet covering Music, Art, Comedy, Film, Food, Theatre, Markets, and use a list mapping to render the matching events on each type page. Each type gets its own /events/{type}/ landing page that automatically reflects current bookings. The types sheet is just a list of slugs and display names; SleekRank does the matching against the events feed.

No. For a UI calendar with month views and date filters, pair SleekRank pages with your existing calendar plugin like The Events Calendar or FullCalendar. SleekRank focuses on SEO landing pages and per-event URLs; the calendar plugin handles the interactive month-view UI for users browsing by date. Many sites run both: SleekRank for the SEO-optimized event pages and a calendar widget on the homepage for date-driven browsing.

Add startDate and endDate columns and render the full range. Some festivals are weekend events with multiple stages; use list mapping for a stages or programs column to render the daily breakdown. Event JSON-LD supports endDate natively, so multi-day festivals get accurate rich result rendering when the schema is mapped from both columns.

If your ticketing platform exposes availability via API, pull it into the feed and render it as a pill via tag mapping. Otherwise add a manual soldOut or limited flag column and update it editorially. SleekRank serves whatever the cached row contains; real-time availability requires either an API-driven feed or short cache duration combined with manual updates from the ticketing dashboard.