Site Launch Checklist
Everything to verify before putting your site into production.
Launching a site is a critical moment. It's the culmination of weeks or months of work, and the first impression your users will have of your product. A problem on launch day can ruin this first impression and be costly to fix.
This checklist covers all technical aspects to verify before going live: infrastructure, security, DNS, SSL, monitoring and alerts. Use it systematically for every launch.
Better to spend an hour verifying everything before launch than to spend the night putting out fires afterward. Print this checklist, check each item, and launch with confidence.
Before Launch
Verifications to perform in the days before launch:
Infrastructure
- Production server configured and tested (not the dev server!)
- Resources sized for expected traffic (CPU, RAM, storage)
- Automatic backups configured and tested (restore verified)
- Production environment variables defined (no dev keys)
- Logs configured and accessible (rotation, retention)
SSL/HTTPS
- Valid SSL certificate installed (not self-signed in prod)
- HTTP to HTTPS redirect configured
- HSTS enabled (after full HTTPS testing)
- Certificate expiration date known and alerted
DNS
- DNS records configured (A, AAAA, CNAME as needed)
- TTL temporarily reduced (to facilitate corrections)
- DNS propagation verified from multiple locations
- Email records configured if applicable (MX, SPF, DKIM)
Monitoring
Monitoring configuration before go-live:
- Availability monitor created on production URL
- SSL monitor enabled to watch certificate expiration
- Response time thresholds defined and alerts configured
- Content verification configured (not just 200 code)
- Critical pages monitored (home, login, checkout...)
- Heartbeat monitor for scheduled tasks (cron, backups)
Alerts
Notification configuration:
- Alert recipients defined (who's responsible?)
- Alert channels configured (email, SMS, Slack)
- Escalation defined (what happens if no one responds?)
- Alert test performed (verify it actually arrives)
After Launch
Post-launch verifications:
- Site accessible from multiple locations
- SSL working correctly (no browser warning)
- Response time within expected norms
- First hours of monitoring without alerts
- Team available to react to potential problems
Frequently Asked Questions
How long before launch should I configure monitoring?
At least 48h before, ideally a week. This allows detecting configuration problems and ensuring alerts work.
Should I monitor the staging environment too?
Yes, recommended. Staging problems often foreshadow production problems. A simple monitor is enough.
What SLA should I aim for on a new site?
Start with 99.9% (8.77h max downtime per year). Adjust based on criticality. An e-commerce site needs more than a blog.
How to handle monitoring during DNS migration?
Monitor both old AND new URL during propagation. Remove the old monitor once propagation is complete (24-48h).
Do I need to be available 24/7 for launch?
Ideally, yes, for the first 24-48h. After that, monitoring takes over and alerts you only when necessary.
What if I detect a problem just before launch?
Postpone if possible. A delayed launch is better than a failed launch. If postponing is impossible, document the problem and have a rollback plan.
Launch with Confidence
A well-prepared launch is a successful launch. This checklist ensures you haven't forgotten anything on technical aspects. Combine it with your own business verifications.
With MoniTao in place, you'll be alerted immediately if something goes wrong after launch. Enjoy peace of mind and focus on your users.
Useful Links
Ready to Sleep Soundly?
Start free, no credit card required.