Before going live, verify environments, load order, and security, then monitor production to catch regressions quickly.

Preflight (staging)

  • Environment detection: Confirm Smart Script loads staging files on webflow.io and production files on your live domain.
  • No console errors: Open DevTools on critical pages; ensure zero red errors and expected warnings only.
  • Load order confirmed: Page scripts load based on file order; test dependent features.
  • Page targeting: Check that each Slater file runs only where intended (templates, static pages).
  • Performance sanity: Test TTI and interaction responsiveness; enable minification if helpful.
  • Security review: No secrets in client code; validate third‑party script origins and scopes.
  • Accessibility and forms: Submit key forms; verify validation and success handling.

Go‑live steps

  • Publish production from Slater.
  • Clear critical caches if applicable; validate CDN headers and caching behavior.
  • Smoke test top 5 user journeys (homepage, nav, signup/contact, key CMS template, conversion page).

Post‑launch monitoring (first 48 hours)

  • Error tracking: Watch console/error logs; revert a feature by toggling its Slater file if needed.
  • Analytics diffs: Compare baseline vs. live metrics for bounce rate, form completion, and key events.
  • Rollback ready: Keep prior embeds handy in case you need a quick revert.

Success criteria

  • Zero blocking JS errors on core pages.
  • All critical forms and interactions pass test cases.
  • Metrics within expected variance vs. staging baselines.

FAQ
Q: Do I need different scripts for staging and production?
A: No. The Smart Script loads the appropriate environment automatically based on domain.

Q: How can I reduce production risk?
A: Ship in small batches, keep clear load order, and validate on staging before each promotion.

Q: Where is my code hosted in production?
A: Slater serves production JS from Amazon S3 with browser caching for reliability.

Sources