Launching a website without a checklist is like flying without a pre-flight inspection. Everything might be fine. Or you might discover a critical problem at the worst possible moment, when real users are watching. This checklist covers the 25 items that matter most, organized into five categories so nothing falls through the cracks.
Performance (1-5)
1. Page Load Speed Under Three Seconds
Run every key page through Google PageSpeed Insights and WebPageTest. If any page takes longer than three seconds to become interactive on a mobile connection, visitors will leave before they see your content. Compress images, defer non-critical JavaScript, and enable browser caching before launch day.
2. Images Are Optimized and Properly Sized
Every image should be served in a modern format like WebP or AVIF, with explicit width and height attributes to prevent layout shift. Use responsive images with the srcset attribute so mobile devices do not download desktop-sized files. A single unoptimized hero image can add several seconds to your load time.
3. CSS and JavaScript Are Minified and Bundled
Unminified files waste bandwidth and slow rendering. Make sure your build process compresses CSS and JavaScript, removes unused code, and combines files where practical. Check that critical CSS is inlined so the page renders without waiting for external stylesheets.
4. Server Response Time Is Fast
Your server should respond in under 200 milliseconds. If it takes longer, investigate your hosting plan, database queries, and server-side rendering pipeline. A slow server penalizes every single page on your site regardless of how well you have optimized the front end.
5. CDN Is Configured and Working
A content delivery network serves your static assets from servers closest to your visitors. Verify that your CDN is properly configured, that cache headers are set correctly, and that purging works when you deploy updates. Test from multiple geographic locations to confirm global performance.
SEO (6-10)
6. Every Page Has a Unique Title Tag and Meta Description
Title tags should be under 60 characters, include relevant keywords, and accurately describe the page content. Meta descriptions should be under 160 characters and give searchers a reason to click. Duplicate titles and missing descriptions are among the most common SEO issues found at launch.
7. URL Structure Is Clean and Consistent
URLs should be lowercase, use hyphens instead of underscores, and follow a logical hierarchy. Avoid query strings for permanent pages. Once you launch, changing URLs means setting up redirects, so get the structure right from the start.
8. XML Sitemap Is Generated and Submitted
Your sitemap should include every page you want indexed and exclude everything you do not. Submit it to Google Search Console and Bing Webmaster Tools. Verify that it updates automatically when you add or remove pages.
9. Robots.txt Is Correct
A misconfigured robots.txt file can block search engines from your entire site. Double-check that you are not accidentally disallowing important pages and that staging environment directives have been removed. Test the file using Google Search Console's robots.txt tester.
10. Canonical Tags Are Set Properly
Every page should have a self-referencing canonical tag to prevent duplicate content issues. If you have pages accessible at multiple URLs, the canonical tag tells search engines which version to index. Check that trailing slashes, www vs. non-www, and HTTP vs. HTTPS variations all resolve correctly.
Accessibility (11-15)
11. All Images Have Descriptive Alt Text
Screen readers depend on alt text to convey image content to visually impaired users. Every meaningful image needs a clear, concise description. Decorative images should use an empty alt attribute so screen readers skip them. This also helps your SEO.
12. Keyboard Navigation Works Throughout
Every interactive element on your site should be reachable and operable using only a keyboard. Tab through your entire site and verify that focus states are visible, dropdowns open and close, modals can be dismissed, and the tab order makes logical sense.
13. Color Contrast Meets WCAG Standards
Text must have a contrast ratio of at least 4.5:1 against its background for normal text and 3:1 for large text. Use a contrast checker on every color combination in your design. Low contrast is one of the most common accessibility failures and one of the easiest to fix.
14. Forms Are Properly Labeled
Every form field needs an associated label element, not just placeholder text. Error messages should be clear and specific, telling users exactly what needs to be corrected. Required fields should be marked visually and programmatically using the required attribute.
15. Heading Hierarchy Is Logical
Use heading levels in order without skipping. Each page should have exactly one H1 that describes the page content. Headings create an outline that screen reader users navigate by, and a broken hierarchy makes the page confusing to navigate.
Analytics (16-20)
16. Analytics Tracking Is Installed and Verified
Install your analytics platform, whether Google Analytics 4, Plausible, Fathom, or another tool, and verify it is collecting data on every page. Use real-time reports to confirm events are firing. Discovering after launch that tracking was broken means lost data you can never recover.
17. Conversion Goals Are Defined and Tracking
Identify the actions that matter most: form submissions, phone calls, purchases, downloads. Set up goal or event tracking for each one. Without conversion data, you cannot measure whether your website is actually working or just attracting visitors who leave without acting.
18. UTM Parameters Are Planned
Before you start promoting your new site, establish a UTM naming convention for campaign tracking. Document it so everyone on your team tags links consistently. Clean UTM data makes it possible to attribute results to specific marketing efforts.
19. Search Console Is Connected
Google Search Console provides data you cannot get anywhere else: which queries bring visitors, how your pages appear in search results, and what technical issues Google has found. Verify your site, submit your sitemap, and review the initial crawl report.
20. Error Monitoring Is Active
Install an error tracking service like Sentry, LogRocket, or Bugsnag to catch JavaScript errors, failed API calls, and broken user experiences. Real users will encounter problems you never found in testing. Error monitoring tells you about them before they contact you, or worse, leave silently.
Security (21-25)
21. SSL Certificate Is Installed and Forcing HTTPS
Every page should load over HTTPS with no mixed content warnings. Verify that HTTP requests redirect to HTTPS automatically. Check that your certificate is valid, not expired, and covers all subdomains you are using. Browsers now warn users about insecure sites, which destroys trust immediately.
22. Contact Forms Have Spam Protection
Without spam protection, your inbox will fill with junk within days of launch. Implement a honeypot field, rate limiting, or a privacy-respecting CAPTCHA solution. Test that legitimate submissions still go through smoothly after adding protection.
23. Security Headers Are Configured
Set up Content Security Policy, X-Content-Type-Options, X-Frame-Options, and Strict-Transport-Security headers. These prevent common attacks like cross-site scripting, clickjacking, and protocol downgrade attacks. Use a tool like SecurityHeaders.com to grade your configuration.
24. Admin and Staging URLs Are Not Publicly Accessible
Lock down CMS login pages, staging environments, and development tools before launch. Search engines should not index your staging site. Admin panels should require strong authentication and ideally be restricted by IP or placed behind a VPN.
25. Backups Are Automated and Tested
Automated daily backups should be running before you launch, not after your first emergency. Verify that you can actually restore from a backup. Store backups in a separate location from your production server. A backup you have never tested is not really a backup.
After Launch
Launching is not the finish line. In the first 48 hours after going live, monitor your error logs, check analytics for unexpected behavior, test all forms by submitting real entries, and review your site on multiple devices. Schedule a one-week post-launch review to catch any issues that did not appear immediately.
Create a recurring monthly audit using a condensed version of this checklist. Websites degrade over time as content is added, plugins are updated, and third-party services change. A regular review keeps small issues from becoming big problems.
Frequently Asked Questions
How far in advance should I start the pre-launch checklist?
Start at least two weeks before your target launch date. Performance optimization and accessibility fixes often reveal deeper issues that take time to resolve. Rushing through the checklist in the final hours defeats its purpose. Some items, like analytics setup and UTM planning, benefit from even earlier preparation.
What is the most commonly missed item on launch checklists?
Error monitoring. Teams focus heavily on making the site look right and perform well, then forget to set up systems that catch problems after launch. The second most missed item is testing form submissions end-to-end, including confirmation emails and CRM integrations, not just that the form displays correctly.
Is it a bad idea to launch on a Friday?
Generally, yes. If something goes wrong after a Friday launch, your team may not be available to fix it over the weekend. Launch on a Tuesday or Wednesday so you have the rest of the work week to monitor, respond to issues, and make adjustments with your full team available.
Do I need a staging environment?
Absolutely. A staging environment that mirrors production lets you test changes without risking your live site. It is essential for verifying the launch checklist items because you can catch and fix problems before real visitors encounter them. Most modern hosting platforms make staging environments easy to set up.