A checklist before a site launch

A launch is celebrated when the homepage finally looks like the mockup. That day usually surfaces what was nobody's task: the form says success and sends nowhere, the admin password is from a draft, an ad link goes to the old address, the certificate was issued for a neighbouring domain. The checklist below is short on purpose. It can be walked in a day if it is not left for the evening before traffic is switched on.

Before inviting people

• The domain and mail are in your organisation, not on a contractor's personal mailbox.
• HTTPS opens both with www and without. Old http does not live on its own.
• The form reaches an inbox or a CRM. There is consent text and a policy that opens.
• Analytics sees the submit, not only the view. Goals are checked with a test lead.
• Page titles are not identical and not empty. Key old addresses do not return 404.
• A copy has been taken and brought up once. The admin password is not from the mockup and is not shared.
• On a phone the first screen, the form and the phone number are readable. The page does not slide sideways.
• Extra test users and test payments are switched off.

A store and an account area add a permissions check to this list: someone else's order and someone else's profile do not open when a number is swapped. A landing needs the form and the scripts that must not read the fields. The depth differs. The habit of walking the list is the same.

Lexora walks this list before handing over our own projects and can walk it on a launch that is already built by someone else. The day ads go on is a bad moment to learn that a lead went nowhere.