Per edition is the better pattern for craft fairs because buyers search for specific dates and craft mixes. Use slug values like portland-holiday-craft-dec-2026 so each edition has its own SEO history and can rank for year-specific queries it earns.

A second page group at /craft-fairs/{category}/ filters rows where the craft_categories array contains the URL slug. /craft-fairs/pottery/ lists every pottery fair in the sheet, ordered by date. Makers find the right fair to apply to without scrolling through the entire calendar.

Yes. Store vendor data in a sub-table or a separate sheet keyed to the fair slug. A list mapping reads the vendor data and renders the booth roster on the fair page. Vendors update their own rows; the fair page rebuilds itself.

Yes. Map row fields into a JSON-LD Event block via a meta mapping. Fair name, edition dates, location, vendor count, and image flow per row. Validate one page with Google's Rich Results Test, then trust the template across the corpus.

Build the application form once into the base WordPress page using your usual form plugin and inject the fair-specific routing ID via a selector mapping into a hidden field. Applications land in the right inbox or sheet automatically per fair.

Yes. Build the ticketing block once into the base page using WooCommerce, FooEvents, or Tickera, and inject the fair-specific event ID via a selector mapping. One template, one ticketing flow, every fair inherits.

Move past rows to an archive sheet feeding /craft-fairs/archive/{slug}/ or 301 the past slug to the current edition. Both approaches preserve link equity while keeping the current calendar clean.

Each city hub lists different fairs with different dates, vendor counts, and category mixes. Vary the meta description and intro per city, and the corpus reads as a real local directory rather than templated variations.