Website launch checklist

By Adrian Diaz

Content and first impressions

Explain what the website offers, who it serves, and what a visitor can do next. Proofread the key pages, check contact details, and replace placeholder copy and images. Follow each navigation link and call to action to its destination. Ask someone unfamiliar with the site to describe its purpose after a quick look; confusion is a useful signal to revise the heading or navigation.

Mobile and usability

Review the most important pages on a phone and at a narrow browser width. Look for clipped text, horizontal scrolling, controls that are difficult to tap, and images that cover essential information. Work through your main user journey from start to finish. Test forms with valid and invalid information, confirm that errors are understandable, and check that a successful submission reaches the intended recipient.

Accessibility

Use only a keyboard to move through navigation, links, forms, and dialogs. Check that focus remains visible and that every control has a meaningful label. Review heading structure, image alternatives, text contrast, and whether motion can be reduced. Automated checks can reveal useful issues, but they do not replace testing the actual experience. See the accessibility testing guide for a more detailed process.

Search and sharing

Give each important page a descriptive title, a useful description, and a canonical URL that points to the intended public address. Check that pages meant for search are not blocked from indexing. Review the sitemap and submit it through Search Console when appropriate. Share a test link in a messaging tool and inspect the image, title, and description that appear.

Performance and reliability

Resize and compress large images, remove unnecessary assets, and test representative pages on mobile. Check important redirects and the not-found page. Confirm that backups exist and that someone knows how to restore them. A backup is only useful if it can be recovered, so include a restore exercise in your maintenance process where practical.

Security and measurement

Verify HTTPS on the final domain and review access for the people who maintain the site. Update the CMS, plugins, and dependencies where applicable. Review privacy and cookie requirements for the site’s circumstances. Finally, confirm that analytics receives visits and that important actions such as enquiries or purchases are measured correctly. Recheck after launch using a real visit.

After the site goes live

A launch check is a snapshot, not a guarantee that every future change will be safe. Assign someone to monitor enquiries, orders, broken links, and site availability after release. Check the public version with a fresh browser session and confirm that the domain, HTTPS, and important redirects behave as expected. Keep a list of problems with an owner and a target date. Recheck any fix on the live site rather than relying only on a staging preview.

Make the checklist part of the handoff. The person who owns the site should know where the domain is managed, who can restore a backup, how to reach support, and which reports are used to monitor important actions. Some items do not apply to every website; record why an item was excluded instead of marking it complete without checking.

A practical launch rehearsal

Choose a representative visitor and follow the site from their first page to the action they came to complete. For a service website, that might mean finding a relevant service, reviewing the information, and sending an enquiry. For a store, it could mean finding an item, choosing a variant, checking delivery details, and completing an approved test order. Write down each step so another person can repeat it.

Run the rehearsal on a phone as well as a desktop browser. Check the links and fields that the visitor actually uses, including error messages and the confirmation after submission. An attractive homepage does not establish that a form reaches its destination. Confirm the message or order in the receiving system and remove any test records according to the business’s process.

After corrections, repeat the same journey on the public address. Keep the results with the launch notes so the owner knows what was checked, what is still open, and who is responsible for follow-up.

What to document

Record the final public domain, the person responsible for the site, and the location of the maintenance instructions. Include the date of the launch rehearsal and note any exceptions that still need work. If a check is not relevant, explain why instead of assuming it was completed. Save a list of the important accounts and recovery contacts using the organization’s secure process.

A useful follow-up is to repeat the enquiry or purchase journey after any major change to the theme, plugins, checkout, or form provider. Review the deeper guides linked below when an item needs more than a quick pre-launch check.

Put the guidance into practice

Start with the page or workflow that matters most to the people using the site. Write down the current behavior, the change you intend to make, and the person responsible for reviewing it. If the site has a staging environment, test the change there before applying it publicly. Keep a record of the previous configuration and make sure the team knows how to restore it if the change causes a problem.

After the change, repeat the original task with realistic content. Check it on a small screen and with a keyboard, and include any form, payment, or integration that the change could affect. Record the date, result, and any follow-up. Share the outcome with the site owner in terms of what visitors can now do and what remains uncertain. Revisit the check when the underlying content, theme, or connected tools change.

Interactive checklist

Progress is saved in this browser when storage is available.

0 of 30 checks complete

Explore the deeper guides

Explore related services.

Need a hand?

Discuss your project