Yes. Either use a days array on the row with a list mapping that renders each day inside one URL, or duplicate the row per day so the urlPattern emits separate URLs. Pick row duplication when each day has different vendors or hours, since you then get distinct titles and meta descriptions per day-market combination.

Add an active or season column and filter on it in the base page template. Off-season markets either drop from the directory entirely if you also filter at the urlPattern level, or render with a closed-for-season block while keeping the URL alive for continuity. PSU Market March-December stays indexed year-round but reflects the closure during winter.

Yes. Pass a vendors array per row and use a list mapping to render them inside the base page. Each list item can include vendor name, produce focus, and a link out. SleekRank does not limit list length, so long-running markets with sixty vendors render the same way as small ones with eight.

No. SleekRank renders content and does not process forms or payments. Link out to the market organiser's sign-up tool from each row through a selector mapping. Most market sites already use Google Forms or a dedicated event tool for vendor applications, and SleekRank simply surfaces the link per market page.

Yes. Map an image URL column to og:image, or pair with SleekPixel for dynamic cards combining market name, day, and city. Configure the meta mapping in the page group and every market gets its own Open Graph card without manual design work per row.

Each data source has its own cacheDuration, set when you configure the page group. Edit the sheet and clear the SleekRank cache to publish immediately, or wait for the next cache cycle. For seasonal market sites, an hour or two of cache is usually fine since vendor changes do not happen mid-day.

Add a months-active column to each vendor row in the vendors array and surface it through the list mapping with conditional rendering in the base page template. Visitors see which months a strawberry stand or honey vendor actually attends, which improves trust on tourism searches.

Add a neighborhood column and either change urlPattern to /farmers-markets/{neighborhood}/{slug}/ or run a parallel page group keyed on neighborhood that pulls from the same sheet. Each page group is independent, so neighborhood-level splits across larger cities cost little beyond the new mapping.