On this page
Definition
Website launch testing is the final review process used to check that a website works correctly before it is made public. It should cover content, links, forms, mobile layouts, page speed, SEO settings, analytics, security, redirects, DNS and hosting readiness.
A launch should not be treated as a simple button press. Even a well-built website can have missed redirects, broken forms, incorrect tracking or DNS issues if the final checks are rushed.
Key Takeaways Before Launch
- A pre-launch website checklist should test both user-facing items, such as navigation, forms and mobile layouts, and technical items, such as redirects, metadata, indexing rules, DNS and SSL.
- Testing should happen in a secure staging environment first, then key checks should be repeated after the website goes live because live hosting, DNS and third-party integrations can behave differently.
- A clean launch reduces avoidable disruption, protects search visibility and gives users a smoother experience, but it does not remove the need for ongoing maintenance, monitoring and improvement.
Quick answer
What Should Be Tested Before a Website Goes Live?
Website Pre-Launch Checklist
Use this checklist as a practical starting point before approving a new website for launch. The exact checks may vary depending on the website platform, content, hosting setup and connected services.
-
User experience and conversion checks
Review the main navigation, internal links, calls-to-action, contact forms, phone links, enquiry paths, service pages, product pages and checkout flow where relevant. A user should be able to understand what you offer and take the next step without confusion.
-
Technical, SEO and tracking checks
Check title tags, meta descriptions, headings, canonical tags, redirects, XML sitemap, robots settings, schema markup where used, analytics, conversion tracking, page speed and Core Web Vitals. Search engines need to crawl and understand the site after launch.
-
Infrastructure, security and launch checks
Confirm SSL/TLS, hosting readiness, backups, DNS records, email-related records, staging to live deployment steps, third-party integrations and post-launch monitoring. These checks help reduce downtime, broken services and unexpected launch issues.
User testing
Test the Website Like a Customer Would Use It
Launch process
A Practical Website Launch Testing Process
A structured launch process keeps testing organised and reduces the chance of missing important issues. The steps below are a general framework, not a replacement for a project-specific checklist.
-
Test the staging website first
Review the website in a secure staging environment before it is public. Check content, layouts, navigation, forms, functionality, integrations and SEO foundations. This is the safer place to find issues because changes can be made before customers or search engines see the site.
-
Approve launch only after key fixes are complete
Record issues, assign responsibility and retest after corrections. Approval should be based on practical readiness, not only visual approval. Where the website replaces an existing site, redirects, content migration and tracking should be checked before launch.
-
Repeat critical checks after the site is live
Once the website is live, test forms, SSL, redirects, analytics, DNS, page access, indexing settings and key user journeys again. Some issues only appear once the live domain, hosting environment or third-party services are involved.
Do Not Skip Live Testing After Launch
SEO checks
SEO Tests That Should Be Completed Before Launch
Staging Testing vs Live Testing
Both stages matter. Staging testing helps catch issues before public launch, while live testing confirms the final domain, hosting and integrations behave as expected.
| Area | Staging Testing | Live Testing |
|---|---|---|
| Purpose | Find and fix design, content, functionality and SEO issues before the public website is visible. | Confirm the launched website works correctly on the real domain with live hosting, DNS and integrations. |
| Risk level | Lower risk because the site is private and changes can be made before users or search engines are affected. | Higher risk because issues may affect customers, tracking, search engines or business operations. |
| Typical checks | Layouts, content, forms, navigation, page templates, integrations, redirects plan and technical SEO setup. | SSL, DNS, redirects, forms, analytics, indexing access, caching, uptime monitoring and key conversion paths. |
Common Issues Found During Website Launch Testing
Final testing often reveals issues that are small individually but serious if they reach the live website. These examples show why a structured launch review matters.
The contact form submits but no email arrives
Likely cause
The form may be misconfigured, the notification address may be wrong, or email authentication and DNS records may not support reliable delivery.
Solution
Test form submissions from multiple pages, confirm where notifications are sent, check spam folders and review SPF, DKIM and DMARC where email delivery is involved.
Pages load correctly on desktop but break on mobile
Likely cause
The layout may not have been tested across common screen sizes, or content such as tables, buttons or images may not respond properly.
Solution
Test key pages on mobile and tablet viewports, check tap targets, menus, forms, text sizing, image scaling and sticky elements before launch.
Old URLs show 404 errors after launch
Likely cause
Redirects from the previous website may be missing, incomplete or pointing to unsuitable pages.
Solution
Prepare a URL redirect map before launch, test important old URLs after launch and monitor errors so affected pages can be corrected quickly.
Website Launch Testing Mistakes to Avoid
Most launch issues are avoidable when the testing process is planned. These mistakes are common when a launch is rushed or treated as purely visual approval.
Only checking the homepage
Do this instead
Test the full journey across key pages, including service pages, contact pages, forms, menus, footer links, location pages and any product or checkout pages.
Leaving SEO checks until after launch
Do this instead
Review metadata, headings, crawl access, sitemap, redirects, internal links and page structure before launch. SEO works better when it is built into the structure, not patched in later.
Changing DNS without a launch plan
Do this instead
Audit existing DNS records first, prepare the new hosting environment, coordinate timing and understand that DNS propagation and third-party systems can still cause temporary interruptions.
Performance and security
Speed, Security and Hosting Checks Before Go-Live
DNS Changes Can Affect More Than the Website
Our approach
How We Approach Website Testing and Launches
Website Launch Testing FAQs
These short answers address common questions businesses ask before approving a website launch.
Should a website be tested before or after it goes live?
Who should approve a website before launch?
Can launch testing guarantee there will be no issues?
Planning a Website Launch?
If your website is being rebuilt, migrated or prepared for launch, we can help you review the structure, functionality, SEO foundations, hosting and deployment plan before it goes live.