What each part of the checklist covers
A website launch checklist is the list of checks you finish before a site goes live and is handed to the client: for example, the brochure site list in this tool has 33 checks, from proofread copy to tested forms and working backups, and ends with a handoff sheet the client signs.
The checklist is grouped by the kind of mistake each part catches.
- Content
- The words, images, prices and links. Most launch-day emails from clients are about a typo or a wrong phone number.
- Design QA
- Checking the layout on real phones, tablets and desktops, plus keyboard use and contrast. QA means quality assurance: looking for problems on purpose.
- Forms and email
- Every form sends, every message reaches the right inbox, and for shops a real test order goes through.
- Search basics
- Page titles, descriptions, redirects from old addresses and making sure the staging block on search engines is removed.
- Access handover
- The client owns their domain, hosting and accounts, and logins are shared through a password manager, never by email.
- Handoff sign-off
- A one-page record that the site was handed over, with the checks done, any open items and both signatures.
How many checks each kind of site needs
These counts come from the three starting points in the checklist above. They are examples: a shop needs checkout and returns checks a landing page does not.
| Group | Example: Brochure site | Example: Shop | Example: Landing page |
|---|---|---|---|
| Content | 5 | 6 | 4 |
| Design QA on phone, tablet and desktop | 6 | 6 | 6 |
| Forms and email | 3 | 6 | 4 |
| Search basics | 5 | 5 | 3 |
| Speed | 3 | 3 | 3 |
| Legal and cookies | 3 | 4 | 3 |
| Analytics | 3 | 3 | 2 |
| Backups and access handover | 5 | 5 | 4 |
| All checks | 33 | 38 | 29 |
Before you call it launched
A tick is a promise
Only tick what you actually checked on the live site. The sign-off sheet shows the count to your client, so an honest open item is better than a false tick.
Check the live site, not staging
Forms, redirects, analytics and search settings often behave differently once the real domain is connected. Run the checks again after the switch.
Your ticks stay in this tab
The checklist keeps your progress in this page only. Print or copy the sign-off sheet before you close the tab.
Legal pages need the client
You can publish a privacy policy page, but the client is responsible for what it says. Ask them to supply or approve the text.
Open items are fine if they are written down
Launching with a known gap is normal. Listing it on the sign-off sheet, with who will fix it, avoids an argument about it later.
Questions about launching and handing over a website
When should I start the launch checklist?
About a week before launch for content and design checks, and again on launch day for anything that depends on the live domain.
What is a website handoff sign-off?
A short document the client signs to confirm the site was delivered, listing what was checked and what is still open. It marks the end of the project and the start of any support terms.
Does the tool visit or scan my site?
No. The site address is only printed on the sheet. Nothing is fetched or uploaded, and every check is one you do yourself.
Is the checklist different for an online shop?
Yes. The shop preset adds checks for products and stock, a real test order, refunds, shipping, tax, and terms of sale.
What if the client will not sign the handoff sheet?
Send it by email with the open items listed and ask for a written reply instead. A written "looks good" is a reasonable record.
Who should do the checks: the designer or the developer?
Ideally someone who did not build the page, because fresh eyes catch more. On a solo project, take a break first and check on a different device.