Launch

Go-live checklist

Cross-check of what is done, what can wait, and what still needs owner action before a serious public launch.

Open validation reportOpen deployment guide

Checklist

StatusItemCross-check
PassedStatic build generated431 festival records and 431 event pages.
PassedCore required files existsitemap.xml, robots.txt, llms.txt, llms-full.txt, feed.xml, calendar.ics, manifest, 404 and deployment config are present.
PassedSource URLs presentNo festival record is missing source_url.
PassedDirectory labelingDirectory-style sources are labeled as directory-source and shown with a verify-before-booking warning.
ReviewSource quality423 records are directory-source. Improve these over time with official event, tourism, municipality or Pro Loco sources.
PassedNewsletter captureA static Netlify form is wired. Replace it with Beehiiv/ConvertKit later if newsletter automation is preferred.
PassedFestival submission/correction formA static Netlify form is wired. Replace it with Tally/Formspree if deploying outside Netlify or if workflow automation is needed.
BlockerAnalyticsSet PLAUSIBLE_DOMAIN or GA4_MEASUREMENT_ID before paid traffic, sponsor reporting or affiliate testing.
PassedAdvertiser inquiry formA static Netlify form is wired. Replace it with a CRM or advertiser inquiry form after launch if needed.
Can waitAffiliate linksBooking, Stay22, Viator and GetYourGuide placeholders can wait until traffic exists.
Can waitCheckout linksGuidebook and advisor pack checkout placeholders can wait until product files are ready.
Owner taskPublic deployment accountDeploy through Netlify, Cloudflare Pages or Vercel using /ops/deploy.html instructions.
Owner taskDomain and emailPoint domain/DNS and add a real contact or forwarding address.
Recommendation: the site is ready for external review and a Netlify soft preview. For a serious public launch, add analytics and begin replacing the highest-value directory-source records with official or tourism sources.