All Essays

Essay 82

Website launch checklist: the gate a business site passes before it opens

2026-10-01

Launch is a gate you pass deliberately, not a date you reach: a site that opens before it is checked borrows its first impression from luck.

Launch day gets treated like a birthday: a date on the calendar, chosen by enthusiasm, celebrated with an announcement. Then the site opens to real customers and the first contact form disappears into an inbox nobody watches. The announcement did its job. The site was never asked whether it could do its own job.

We treat launch as a gate instead: a short list of categories, each checked before the door opens. None of them is exotic, and all of them are the difference between a site that works and a site that merely exists. The gate costs an afternoon to pass deliberately, and it saves the weeks a bad first impression charges afterwards.

The first category is delivery: the forms actually deliver, and a human answers what arrives, because a form that vanishes into an unwatched mailbox teaches visitors never to write again. The second is honesty of links: every link goes somewhere real, and the page it promises is the page it opens. The third is behavior under bad conditions: the site is used on a real phone, on a slow connection, the way a customer will actually meet it.

The next categories are quieter. Both languages are complete, with nothing machine-shaped left in the copy, because one polished language sitting beside one rough one reads as a company that finished half its work. The analytics see traffic without seeing visitors as ghosts, so decisions rest on real signals instead of noise. And the search engines can find and read the pages, since a site that cannot be read is a site that cannot be found.

Two checks are the least glamorous and the most load-bearing. The backup exists and has actually been restored once, because a backup that has never come back through a restore is a hope, not a backup. And the load-bearing accounts (the domain, the hosting, the site itself) sit in the company's name under the company's control, so the departure of one person or one agency cannot hold the business hostage.

The staging discipline we describe elsewhere feeds this gate, and so does the delivery work on email: a site launches once, and it launches out of staging through these checks rather than around them. This is the gate our own site passes and the ones we maintain pass. It is guidance rather than a guarantee, but the difference shows in every site we inherit: some passed a gate, and some only passed a date.

FAQ

Direct, unambiguous answers

What should I check before launching my business website?

Treat launch as a gate, not a date. The categories worth passing: forms that actually deliver and a human who answers what arrives, links that go somewhere real, behavior on a real phone on a slow connection, two complete languages, analytics that see real visitors, pages search engines can read, a backup restored once, and accounts held in the company's name.

Why does the contact form on a new website go unanswered?

Usually because the message lands in an inbox nobody watches. Delivery is a check, not an assumption: a form that vanishes into an unwatched mailbox teaches visitors never to write again. Before launch, send a real message through every form, confirm it reaches a monitored mailbox, and confirm a person answers what arrives.

How do I know if my website backup actually works?

Restore it once. A backup that has never come back through a restore is a hope, not a backup. The check that matters is taking a copy and bringing the site back from it, so you learn the restore works before the day you need it, not during the emergency that would prove it the hard way.

Whose name should the domain and hosting be in?

The company's. The load-bearing accounts, the domain, the hosting, and the site itself, should sit in the company's name under the company's control, so the departure of one person or one agency cannot hold the business hostage. A site the company cannot reach is not the company's site, whatever the logo on it says.

Does it matter if one language of my website is rougher than the other?

It matters more than it looks. One polished language sitting beside one rough one reads as a company that finished half its work, and nothing machine-shaped should be left in the copy on either side. Launch with both languages complete, or be honest about the one that is still being finished.

Next step

Web Platforms

Web platforms and engineering (bilingual, RTL-native, fast, and built to be found) on the same stack that runs this site and our ventures.

Start an order, request a private consultation, or simply ask a question: one WhatsApp message in Arabic or English opens the conversation.

Talk on WhatsApp