A website can look finished while important functions remain untested. An inquiry form may display a confirmation without delivering the message, an old service URL may return an error, or a setting used during development may prevent public pages from appearing in search.
This website launch checklist helps your team verify the release before publishing and repeat essential checks on the live site. Use it for a new website or a redesign, adapting the checks to your platform and required functionality.
How to Use This Website Launch Checklist
For each check, record the result, the person responsible, and any unresolved issue. Use clear statuses such as passed, failed, or not applicable. A completed task should have evidence, such as a test submission, a screenshot, or a recorded URL check.
Agree on which failures block launch. Broken purchasing or inquiry functions, exposed private information, and unintended restrictions on public pages should be resolved before release. Minor cosmetic issues can be documented separately when the business accepts them.
If your website requirements are still being defined, start with our guide to the five steps to build a business website. This checklist applies once the release is ready for verification.
1. Check Published Content and Page Details
- Remove placeholder text, temporary images, and unfinished sections.
- Confirm service descriptions, contact information, opening hours, and locations.
- Check that pricing, offers, and availability statements are accurate where included.
- Verify permission to publish images, testimonials, and project examples.
- Review page titles, headings, spelling, and important calls to action.
- Open linked documents and confirm that visitors receive the intended files.
Check page details individually rather than assuming that a shared template makes every page correct. A copied service page can retain another service’s heading, contact information, or metadata.
2. Test Forms, Bookings, and Business Integrations
Test the complete process for each important visitor action. Seeing a success message is only one part of the check.
- Submit each inquiry form using valid test information.
- Confirm that the correct team receives the submission.
- Check that information reaches the intended CRM or other connected system.
- Verify confirmation messages and any customer emails.
- Test missing fields, invalid entries, and duplicate submissions.
- Confirm that spam protection does not prevent legitimate submissions.
- Check booking availability, notifications, and cancellation behavior where applicable.
For an online store, also test the payment provider’s supported test scenarios, shipping calculations, order notifications, and inventory updates. Follow the provider’s testing procedure and avoid creating unintended live charges.
Record what happens when a connection fails. The team should know how failed submissions or orders are detected and recovered.
3. Review Mobile Usability and Accessibility
- Test important pages and tasks on mobile and desktop.
- Check menus, buttons, popups, and forms at different screen sizes.
- Confirm that text remains readable when enlarged.
- Use a keyboard to navigate menus, links, and form controls.
- Check visible focus indicators and descriptive form labels.
- Review image alternatives and heading structure.
- Confirm that error messages explain how to correct the problem.
Automated tools can identify some problems, but they do not replace manual checks of important tasks. The W3C accessibility development guidance provides a useful reference for the team carrying out these checks.
If navigation or form interactions remain difficult to use, UI/UX design services can help investigate the underlying issue before launch.
4. Verify URLs, Links, and Redirects
- Check navigation, contextual links, buttons, and footer destinations.
- Confirm that public pages return the expected response.
- Review broken links and unexpected redirects.
- Use final preferred URLs in internal links where practical.
- Confirm that genuinely missing pages show an appropriate error page.
Additional Checks for a Website Redesign
Create a list of old URLs and their intended replacements. Where a page has moved, use an appropriate permanent redirect to its closest relevant replacement.
Test the old URLs directly. Avoid sending every retired page to the homepage, and check for redirect loops or unnecessary chains. Update internal links to the new destinations rather than relying only on redirects.
5. Check Search Accessibility and Page Metadata
- Review robots.txt and page-level indexing instructions.
- Remove development restrictions from public pages intended for search.
- Keep private accounts and sensitive information protected.
- Confirm that canonical tags use the intended production URLs.
- Check descriptive titles and relevant meta descriptions on important pages.
- Verify that internal links lead to crawlable public content.
- Check structured data against the information actually visible on the page.
Review the Sitemap Where One Is Used
A sitemap can help search engines discover URLs, particularly on larger or more complex websites. It is not mandatory for every website and does not guarantee indexing.
Where a sitemap is provided, check that it uses production URLs, excludes inappropriate entries, and lists the preferred public pages. Submit or reference it through the relevant search engine tools.
Google’s sitemap guidance explains when a sitemap is useful and its limitations.
For projects that need specialist review of crawlability, redirects, or page optimization, explore Agency Partner Interactive’s SEO services.
6. Check Performance on Representative Pages
Test more than the homepage. Include a service page, a page with large images, and a page containing an important form or interactive feature.
- Look for oversized images and unnecessary scripts.
- Check whether fonts or embedded media delay useful content.
- Review loading behavior on mobile connections.
- Watch for elements moving while the page loads.
- Confirm that caching does not show outdated or private information.
Use laboratory tests to identify problems before launch. Once sufficient live visitor data is available, review field measurements as well. A single performance score does not describe every visitor’s experience.
If substantial traffic is expected, agree on an appropriate load test with the hosting and development teams. Confirm permission, limits, and the environment before running it.
7. Validate Analytics and Important Events
- Confirm that the intended analytics property receives production data.
- Check that tracking is not installed more than once.
- Test important events such as completed inquiries, bookings, or purchases.
- Compare recorded completions with actual submissions or order records.
- Verify consent behavior where applicable.
- Check tracking across external booking or payment services where required.
Distinguish an attempted action from a completed one. A click on a submit button should not automatically be counted as a successful inquiry if the form fails validation.
Record the launch date and significant tracking changes so later performance comparisons have context.
8. Confirm Production Settings, Access, and Recovery
- Verify the production domain, HTTPS certificate, and intended domain redirects.
- Check that production integrations use the correct credentials and endpoints.
- Remove temporary test accounts and unnecessary administrative access.
- Confirm that backups cover the required files and data.
- Document how the release can be recovered or rolled back.
- Assign responsibility for monitoring failures and responding to incidents.
HTTPS protects information in transit, but it does not establish that the entire application is secure. Access controls, application updates, and other relevant security checks still need attention.
Confirm that the recovery plan is usable, not simply that a backup file exists. For a site collecting orders or inquiries, consider how recent activity would be preserved during recovery.
9. Repeat Essential Checks Immediately After Launch
Publishing can change routing, credentials, caching, or integration behavior. Repeat critical tests on the production website.
- Open the homepage and important destination pages.
- Complete a test inquiry or other approved business action.
- Confirm delivery to the appropriate team or system.
- Test selected old URLs and their redirects.
- Recheck public indexing instructions and canonical URLs.
- Confirm analytics activity and expected events.
- Review application errors and hosting alerts.
During the first few days, monitor error reports, submissions, and customer feedback. Assign a person to investigate unexpected changes rather than assuming the launch checklist covers every future issue.
Keep a Launch Record
Save the approved checklist, unresolved issues, launch time, responsible contacts, and recovery instructions. Include enough evidence for another team member to understand what was checked.
A practical record contains the check, result, evidence, owner, and required follow-up. This makes handover easier and helps distinguish a new problem from an issue already accepted before launch.
Frequently Asked Questions
What should a website launch checklist include?
It should cover content accuracy, visitor tasks, forms and integrations, mobile usability, accessibility, URLs, search settings, performance, analytics, and recovery arrangements.
Should testing happen only on the staging website?
No. Complete appropriate checks before launch, then repeat important tasks on production because live settings and integrations may differ.
Does a sitemap guarantee that my pages will be indexed?
No. A sitemap helps search engines discover URLs, but it does not guarantee crawling or indexing.
Should every issue be fixed before launch?
Resolve issues that prevent essential tasks or create unacceptable risk. Document lower-priority issues and obtain explicit acceptance from the responsible business owner.
How long should a website be monitored after launch?
Monitor closely during the initial release period and continue routine monitoring afterward. The intensity depends on the website’s functions, traffic, and business importance.
Launch with Evidence, Not Assumptions
A completed website launch checklist should demonstrate that important tasks work, public pages have the intended settings, and the team can respond if something fails.
If testing identifies problems that require implementation work, explore Agency Partner Interactive’s web development services to discuss the fixes and launch support your project needs.
Not big on reading? That’s okay. Watch “Creating a Website Launch Checklist” instead.
Using the power of Artificial Intelligence, we turned this blog into a video for you. Watch it below.
