Denshin / Blog / Process

The pre-launch checklist we run before shipping a client’s site

Empty states, error paths, SEO, Core Web Vitals, security headers, backups, and the handover test: the practical checklist that keeps a launch calm instead of catching fire.

Denshin Team · Product & Delivery · 25 June 2026 · 3 min read

The gap between "the build is done" and "this is ready for real users" is wider than most teams expect, and it's where reputations are quietly made or lost. A new product gets exactly one first impression. This is the checklist we actually run before we hand a client's site or app over to the world, not a theoretical best-practices list, but the things we've learned to check because, at some point, we got burned by not checking them.

Does it survive a real first visit?

Empty states. The product looks great full of demo data. What does a brand-new user with zero data see? Empty dashboards, empty lists, and first-run screens are the actual first impression, and they're the most-skipped part of any build.
Error states. Turn off the network and click around. A failed request should produce a calm, human message, not a spinner that spins forever or a white screen. Every state that can fail should fail politely.
The unhappy paths. Wrong password, expired session, declined card, duplicate email. These are where trust is won or lost, and they're invisible in a happy-path demo.

Will anyone find it?

Titles and meta descriptions on every page: unique, accurate, written for a human who's deciding whether to click.
Open Graph and Twitter cards, so a shared link looks like a real product and not a naked URL. Test the actual link in a real chat before launch.
Structured data where it fits (organization, breadcrumbs, articles), so search engines and AI answer engines can understand the page.
A sitemap and a sane robots.txt, and a quick check that you haven't accidentally shipped noindex on the whole site. It happens more than anyone admits.
Canonical URLs, so the same page on two paths doesn't compete with itself.

Is it fast enough?

Speed is a feature and, increasingly, a ranking factor. Check Core Web Vitals on a real mid-range phone over a normal connection, not on your developer laptop on office wifi. Compress and lazy-load images, serve modern formats, cache the static assets hard, and make sure the first meaningful paint happens fast. A beautiful site that takes six seconds to show anything is a slow site with good taste.

Is it locked down?

HTTPS everywhere, with HTTP redirecting to it.
Security headers in place, and no secrets, API keys, or test credentials shipped in the client bundle. Actually grep the build output; don't assume.
Access control verified by trying to reach things you shouldn't be able to. Test the locks by attacking your own doors.
Dependencies audited for known vulnerabilities before launch, not six months after.

Can the client run it without us?

This is the one most agencies skip, and it's the one we care about most. Can a non-technical person on the client's team add content, manage users, and handle the day-to-day without calling us? If the answer is no, the product isn't done: it's dependent. The admin panel ships with the product precisely so that handover is real and not theatrical.

When it breaks at 2am, will we know?

Error tracking wired up, so a production exception reaches a human instead of dying silently in a user's browser.
Uptime monitoring on the critical paths, so you hear it from a monitor and not from an angry customer.
Backups that are configured and restored at least once. A backup you've never tested is a hope, not a backup.
A rollback plan, so a bad deploy is a five-minute inconvenience rather than an emergency.

None of this is glamorous, and that's the point. The work that makes a launch feel calm is invisible when it's done well and very visible when it's skipped.

We run a version of this list before every handover, because the cost of catching these on Tuesday is trivial and the cost of catching them when a customer does is not. If you've got a launch coming up and want a second set of eyes before it goes live, get in touch: a pre-launch review is one of the cheapest forms of insurance there is.

Tags: Launch, Checklist, SEO, Web Performance, Quality

All posts · Work with Denshin