Either remove the row from the source after the workshop runs, or filter on date in the template by comparing the date column to today's date at render time. SleekRank serves whatever is in the cached row, so the source decides what is visible. Some operators automate row removal with a Google Sheet script that hides past dates; others let the template hide expired rows while keeping them for case-study pages.

Add a bookingUrl column and inject it into the book button via a selector mapping. The URL can deep-link to Eventbrite, Tito, a WooCommerce product page, or a custom checkout. Booking and payment run in your booking system; SleekRank does not collect bookings or process payments. Most workshop runners use Eventbrite or Tito for ticketing because attendee management, refunds, and check-in flow already exist there.

Either add one row per occurrence with its own date and slug like /workshops/intro-to-pottery-lisbon-may/ and /workshops/intro-to-pottery-lisbon-june/, or run a single evergreen page per workshop topic with the next date as a column rendered prominently. The first approach gives every occurrence its own SEO page and historical record; the second consolidates link equity onto one URL but loses the per-date SEO benefit.

Yes. Use city as a column and run a per-city page group with a small cities sheet, then list-map the matching workshops onto each city page. Lisbon, Berlin, London, Paris, Amsterdam each become their own /workshops/{city}/ page that reflects current bookable workshops in that city. The cities sheet is just a list of slugs and display names; SleekRank does the matching against the main catalog feed.

No. SleekRank builds the SEO landing pages and per-workshop discovery URLs. Ticketing, attendee lists, refunds, and check-in still run in Eventbrite or your booking platform of choice. Pair them: the SleekRank page is the SEO-optimized destination for organic search, and the Eventbrite or Tito link is the actual checkout. Many workshop runners see better conversion when their own site ranks instead of just relying on Eventbrite's listings.

If your booking system exposes a capacity number via API, yes; pull it into the feed and render it via tag mapping. Otherwise it comes from the sheet and is as fresh as your cache allows. Some operators run a manual 'limited spots' or 'sold out' flag column that they update before each session, which gives urgency signaling without requiring real-time API integration.

Add startDate and endDate columns and render both in the template. Some workshops are weekend intensives or week-long retreats; show the full date range as a pill and use the startDate for sorting and filtering. SleekRank renders whatever the columns contain; the template logic decides how to format ranges.

Add an instructorBio or instructorBioUrl column. For inline bios, inject the text via tag mapping; for linked bios, use selector mapping to point to a separate instructor page. Some workshop businesses run a parallel /instructors/{slug}/ page group that holds full bios and link from each workshop page to the matching instructor profile, all from the same SleekRank setup.