Launching a website isn't just about finishing development. This checklist covers the key areas to review before going live, so you avoid common issues and missed details.
1. Project & Content Readiness
Before launch, make sure the site is actually finished, not just functionally complete, but ready for real users. This is where small oversights tend to slip through and create a poor first impression.
- Finalize all page content
Remove any placeholder text, draft notes, or "coming soon" sections. Every page should be complete and intentional. - Confirm headings, structure, and formatting
Check that headings follow a logical hierarchy (H1–H3), content is easy to scan, and spacing is consistent across pages. - Check all images
Ensure images are properly sized, compressed, and relevant. Avoid oversized files or stretched/cropped visuals that affect performance or layout. - Verify brand consistency
Review fonts, colors, and tone of voice across the site. Inconsistencies here are easy to miss during development but stand out immediately to users.
This step is less about fixing bugs and more about making sure the site feels complete, clear, and cohesive before anyone sees it.
2. Navigation & UX
Before launch, make sure users can actually move through the site without confusion. Even small navigation issues can make an otherwise solid build feel broken or unfinished.
- Test main navigation and dropdowns
Click through all menu items, including dropdowns and mobile menus. Make sure everything is accessible and behaves as expected. - Check all internal links
Verify that links point to the correct pages and that nothing leads to a 404 or outdated URL. - Review mobile responsiveness
Test key pages on different screen sizes. Navigation, spacing, and interactions should work cleanly on mobile, not just desktop. - Validate forms and interactions
Submit all forms (contact, signup, etc.) and confirm they send correctly, display proper messages, and handle errors clearly.
This step is about making sure the site feels intuitive and complete, users shouldn't have to think about how to use it.
3. Technical Setup
Before going live, confirm that the underlying setup is clean and production-ready. Issues here often aren't visible at a glance but can cause immediate problems after launch.
- Remove staging data and test elements
Clear out test content, dummy users, placeholder integrations, and any references to staging environments. - Confirm domain and hosting configuration
Ensure the domain is correctly pointed, DNS is fully propagated, and the site loads properly over the live URL. - Enable SSL (HTTPS)
Verify that HTTPS is active and enforced across the site, with no mixed content warnings. - Test across browsers
Check key pages and functionality in major browsers (Chrome, Safari, Edge). Look for layout issues or broken features.
This step is about making sure the site is properly configured for real-world use, not just working in a controlled development environment.
4. Performance Basics
A site can look complete but still feel slow or unresponsive. Before launch, take a pass on performance to avoid obvious bottlenecks that impact user experience and rankings.
- Optimize images and media
Compress images, use appropriate formats, and avoid loading oversized assets that slow down the page. - Minimize CSS and JavaScript
Reduce file sizes where possible and avoid loading unnecessary scripts or styles. - Test load speed
Check key pages (homepage, landing pages) using tools like PageSpeed Insights or Lighthouse to catch major issues. - Remove unnecessary plugins or scripts
Disable or delete anything not actively used, extra code adds weight and potential conflicts.
This step isn't about perfect scores, it's about making sure the site loads quickly and doesn't create friction for users.
5. SEO Basics
Before launch, make sure the site is set up so search engines can understand and index it properly. These are foundational elements, missing them can limit visibility from the start.
- Set page titles and meta descriptions
Each page should have a clear, unique title and description that reflects its content. - Check heading structure
Ensure proper use of H1, H2, and H3 tags so content is organized and readable for both users and search engines. - Add alt text to images
Provide descriptive alt text for accessibility and to give search engines context. - Create and submit a sitemap
Generate a sitemap.xml and submit it to Google Search Console. - Configure robots.txt
Make sure search engines are allowed to crawl important pages, and that noindex settings from staging have been left behind.
This step ensures your site is ready to be discovered, indexed, and understood once it goes live.
6. Tracking & Analytics
Before launch, make sure you can actually measure what's happening on your site. Without proper tracking, you're flying blind from day one.
- Install analytics tools
Set up Google Analytics (GA4) or your preferred platform and ensure it's properly connected to your site. - Connect Google Search Console
Verify your domain so you can monitor indexing, search performance, and potential issues. - Confirm tracking is working
Visit the site and check real-time reports or debug tools to ensure data is being recorded. - Set up key events or conversions
Define what matters (form submissions, purchases, clicks) and make sure those actions are tracked.
This step ensures you have visibility into how your site is performing and how users are interacting with it from the moment it goes live.
7. Security & Backups
Before launch, make sure the site is protected and recoverable. Even simple safeguards can prevent major issues later.
- Enable basic security measures
Use strong passwords, limit admin access, and ensure any security features or plugins are properly configured. - Set up automated backups
Confirm that regular backups are in place and stored securely, with the ability to restore if needed. - Remove unused components
Delete unused plugins, themes, or modules, they add risk and potential vulnerabilities. - Verify admin access and roles
Ensure only the right people have access, and permissions are set appropriately.
This step is about reducing risk, so if something goes wrong, you're protected and can recover quickly.
8. Final QA Checks
Before launch, take one last pass through the site as a user. This is where small issues surface, things that don't break functionality but impact trust and usability.
- Click through the entire site
Navigate every page and interaction to catch anything missed during development. - Test all forms and notifications
Confirm submissions work, emails are delivered, and confirmation messages display correctly. - Check for typos and formatting issues
Review content for spelling errors, inconsistent spacing, or layout glitches. - Validate error handling
Test the 404 page and ensure any redirects are working as expected.
This step is about polish, making sure the site feels complete, reliable, and ready for real users.
9. Launch Prep
Before going live, make sure everything is in place for a smooth transition. A bit of preparation here helps avoid last-minute issues and gives you a fallback if something goes wrong.
- Create a backup before launch
Take a full backup of the site so you can quickly restore if needed. - Plan your launch timing
Choose a time with lower traffic if possible, and ensure key team members are available if something needs attention. - Confirm access and credentials
Make sure you have access to hosting, domain, DNS, and any third-party services. - Monitor immediately after launch
Check the live site right away, test key pages, forms, and functionality to catch any issues early.
This step ensures you're not just launching the site, but doing it in a controlled, low-risk way.
10. Common Misses Before Launch
Even with a solid process, a few details are easy to overlook. These are common issues that often slip through and cause problems after launch.
- "Noindex" still enabled
Sites are often blocked from search engines during development, make sure this has been removed. - Broken or leftover staging links
Check for links pointing to staging domains or test environments. - Missing favicon and basic assets
Small details like the favicon, social preview images, or default icons are easy to forget. - Forms not sending properly
Email delivery issues (especially on new servers) can go unnoticed without testing. - Analytics not recording data
Tracking may be installed but not firing correctly, always verify before launch.
This final check helps catch the small but impactful issues that can affect visibility, functionality, and overall polish right after launch.
