Per edition is the better pattern for fairs that draw traveling collectors, because buyers search for specific dates and vendor counts. Use slug values like a-current-affair-brooklyn-may-2026 so each edition has its own SEO history and can rank for year-specific queries it earns over time.

Either move past rows to a separate archive sheet feeding /vintage-fairs/archive/{slug}/ or 301 the past slug to the current edition. Both preserve link equity while keeping the current calendar clean for buyers and crawlers.

Yes. A fourth page group at /vintage-fairs/{specialty}/ filters rows where the specialties array contains the URL slug. /vintage-fairs/mid-century/ and /vintage-fairs/denim/ become specialty-specific hubs powered by the same data.

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

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. Build the ticketing block once into the base WordPress page using your usual ticketing plugin (WooCommerce, FooEvents, Tickera) and inject the fair-specific event ID via a selector mapping into a hidden field. One template, one ticketing flow, every fair inherits.

Each edition has different dates, different vendor counts, and often different specialty mixes. Vary the meta description and intro per edition and the corpus reads as a real chronological directory rather than duplicate variations.

Each new row becomes a real WordPress URL with full HTML and ships in the sitemap on the next refresh. New URLs typically index within one or two crawl cycles after the sitemap resubmits. For fast indexing, link the new edition from the per-city hub and the home page.