Either keep one evergreen page per walk with the next date as a column updated each month, or create one row per occurrence with the date in the slug. Most art walk sites use the evergreen approach since the walk identity is stable and only the night and gallery roster change.

Edit the row in the source sheet and clear the SleekRank cache. The page updates on the next cache refresh, typically within minutes. For walks where galleries confirm late, drop the cache duration to 300 seconds during the week of the walk so updates appear without manual flushes.

Yes. SleekRank renders inside the base WordPress page, so it inherits the theme's layout, header, footer, and styling. It works with Bricks, Elementor, Gutenberg blocks, and classic themes. The mappings target CSS selectors and HTML tags, so any theme that exposes named regions can host a per-walk template.

Yes, when each page has unique content driven from the row. The base page is automatically noindexed so only the generated per-walk URLs appear in the sitemap. Event JSON-LD with startDate, location, and offers makes the pages eligible for Google's event rich results panel.

Yes. Use conditional fields in the row to flip blocks on or off. A column like has_live_music or has_food_trucks drives a section's visibility via selector mapping. Larger walks get the extra block; smaller walks skip it. The template stays one file.

Remove the row from the sheet and the URL returns a 404 on the next cache refresh, with the sitemap entry dropped automatically. For canceled-but-archived walks, move the row to a past-walks sheet and run a separate /art-walks/past/ page group that reads the archive.

Each row should carry walk-specific copy in fields like neighborhood description, gallery roster, and feature artists. The mappings inject these into title, H1, and lead paragraphs so every URL has unique copy in the rendered HTML, not just a different night.

Yes. Run two page groups against the same database: one for walks at /art-walks/{slug}/ and one for galleries at /galleries/{slug}/. Link them with a participates_in column on the gallery sheet and a galleries column on the walk sheet. Both directories stay in sync from shared data.