Skip to main content
Toronto roots. Digital possibilities.[email protected]

The Unicorn blog

A practical website launch checklist for business teams

Rocket beside a website launch checklist

A launch is a coordinated change, not just a file upload. Editors, developers, hosting administrators, and business owners may each hold part of the picture. A short checklist with named owners makes those pieces visible and helps the team decide whether the site is ready to go live.

Agree the release and the people involved

Identify the exact version being released, the planned window, and who can approve a go-ahead or a rollback. Make sure the person making the decision can reach the people doing the work. Keep the release notes and known limitations in a place everyone involved can find.

Review the essential content

Confirm company details, contact information, service descriptions, and any agreed pricing. Check images and alternative text, remove demo content from the intended public journeys, and review important links. Ask the content owner to verify the actual pages rather than relying only on a spreadsheet marked complete.

Test the paths that lead to action

Submit an enquiry using a safe test process and verify where it is stored and how staff are notified. Check navigation and keyboard use on mobile and desktop. Include errors and confirmation messages; those states are part of the customer experience even though they are less visible during a design review.

Check the environment and recovery plan

Verify the runtime, document root, permissions, backups, and intended public URL. Confirm that staging-only settings will not block indexing or expose test integrations. Keep matching code and database recovery material available, and decide what evidence would cause the team to stop or revert the release.

Verify again after the switch

Check the live response, redirects, forms, critical assets, and monitoring after deployment. Record the outcome and assign any follow-up work. A launch can be technically successful while leaving editorial tasks unfinished, so finish with a clear handover and an owner for ongoing maintenance.

Make the next step practical

Have a question about your own platform? Plan support after launch and tell us what you would like to improve.