Launching a website is exciting—and nerve-wracking. After months of planning, design, and development, everything comes down to flipping the switch. This comprehensive checklist ensures nothing critical gets overlooked in the rush to go live. We use this list on every project, and now you can too.
Content Verification
Content errors are among the most embarrassing post-launch discoveries. Verify each item before going live.
For more insights on this topic, see our guide on How to Give Website Feedback That Actually Helps.
1. Proofread all text content
Read every page word by word. Look for spelling errors, grammatical mistakes, and awkward phrasing. Fresh eyes help—have someone who hasn't been staring at the content review it.
2. Verify contact information
Check phone numbers, email addresses, and physical addresses on every page where they appear. Test that phone links work on mobile and email links open the correct mail client.
3. Test all internal links
Click every link on every page. Broken internal links frustrate users and hurt SEO. Use an automated tool to catch any you miss manually.
4. Check all external links
Links to other websites can break without warning. Verify that external links still work and point to appropriate destinations.
5. Review all images
Confirm no placeholder images remain. Verify alt text is present and descriptive. Check that images display correctly and aren't stretched or cropped awkwardly.
Technical Essentials
These technical items affect site functionality, security, and search visibility.
6. Install and verify SSL certificate
Your site should load over HTTPS with a valid SSL certificate. Check for mixed content warnings that occur when some resources load over HTTP.
7. Set up 301 redirects
If you're replacing an existing site, redirect old URLs to their new equivalents. This preserves SEO value and prevents visitors from hitting dead ends.
8. Configure custom 404 page
When visitors land on non-existent pages, they should see a helpful error page with navigation options—not a generic server error.
9. Test forms thoroughly
Submit every form on the site. Verify submissions arrive at the correct destination, confirmation messages display, and error handling works for invalid input.
10. Connect analytics
Install Google Analytics or your preferred analytics platform. Verify it's tracking pageviews correctly. Set up goal tracking for important conversions.
11. Set up Google Search Console
Verify site ownership in Search Console. Submit your sitemap. This gives you visibility into how Google sees your site.
12. Test site speed
Run the site through Google PageSpeed Insights. Address any critical issues affecting load time. Document baseline performance metrics.
SEO Readiness
These items help search engines understand and rank your content properly.
13. Verify unique title tags
Every page needs a unique, descriptive title tag under 60 characters. Titles should include relevant keywords naturally.
14. Check meta descriptions
Write compelling meta descriptions for each page (150-160 characters). These appear in search results and influence click-through rates.
15. Review heading structure
Each page should have one H1 tag containing the primary topic. Subsequent headings (H2, H3) should follow a logical hierarchy.
16. Generate and submit XML sitemap
Create an XML sitemap listing all pages you want indexed. Submit it through Google Search Console and reference it in robots.txt.
17. Configure robots.txt
Ensure robots.txt allows search engines to crawl your site. Remove any "noindex" directives that might have been used during development.
18. Set canonical URLs
Each page should have a canonical URL to prevent duplicate content issues. This is especially important for e-commerce sites with filtered views.
Cross-Browser and Device Testing
Your visitors use diverse browsers and devices. Verify the site works for all of them.
19. Test major desktop browsers
Check Chrome, Safari, Firefox, and Edge at minimum. Look for layout issues, font rendering differences, and JavaScript errors.
20. Test mobile browsers
Test on actual iOS and Android devices, not just browser emulators. Pay special attention to touch interactions and mobile-specific features.
21. Verify responsive breakpoints
Resize your browser window through all common widths. Watch for awkward in-between states where the layout breaks down.
Security and Backup
Protect your new site from the moment it launches.
22. Remove development artifacts
Delete test pages, sample content, placeholder user accounts, and any other artifacts from development.
23. Update all passwords
Change any default or shared passwords used during development. Ensure admin accounts have strong, unique passwords.
24. Configure automated backups
Set up regular automated backups of both files and database. Test that backups can be restored successfully.
25. Document login credentials
Create a secure document listing all account credentials you'll need: hosting, domain registrar, CMS admin, analytics, email, and any third-party services.
Post-Launch Immediate Actions
Once the site is live, these actions should happen within the first 24 hours:
- Test the live site on multiple devices and browsers
- Verify forms work with the production email configuration
- Submit the sitemap to Google Search Console
- Monitor analytics for any obvious tracking issues
- Check server error logs for unexpected problems
- Test page load speed on the production server
Common Launch Day Mistakes
Even with a checklist, these issues catch people off guard:
DNS Propagation Delays
When you point your domain to the new site, it can take up to 48 hours for the change to propagate globally. Some visitors may see the old site while others see the new one.
Cached Old Content
Visitors who've been to your site before may see cached versions of old pages. Consider cache-busting strategies for critical updates.
Email Disruption
If your email runs through your web hosting, domain changes can temporarily disrupt email delivery. Plan accordingly.
Third-Party Service Configurations
Integrations that worked on a staging domain may need reconfiguration for the production domain. Test everything again after DNS changes.
Related Reading
- Website Revision Rounds: How Many Is Normal?
- Website Wireframes Explained: Why Every Project Needs Them
- Website Content Gathering: Your Role in the Process
Ready for a Worry-Free Launch?
Our thorough launch process ensures every item on this checklist—and more—gets verified before your site goes live. Let's discuss your project.
Plan Your Launch