Two Weeks Before
This is the stuff that takes time to propagate, or that you can't fix quickly if it's wrong on the day.
Domain and DNS
- The domain is set to auto-renew, with a card on file that won't expire before the renewal.
- DNS points where it should, for both the bare domain and
www, and one redirects to the other. - HTTPS works everywhere, and the certificate renews automatically.
http://redirects tohttps://with a single 301 redirect.
You can check the redirects and headers in one go with the Redirect and Header Checker.
If your product sends any email, this section matters more than anything else on the list, because a welcome email or password reset in the spam folder looks like a broken product.
- SPF, DKIM, and DMARC records are set up for your sending domain.
- Transactional email, like sign-up confirmations and password resets, goes through a proper sending service instead of your web server.
- You've sent yourself every email the product sends, to a Gmail address and to an Outlook one, and they all landed in the inbox.
- Replies to those emails go to an inbox someone reads.
The Email Deliverability Check looks at your domain's records against what Gmail and Yahoo require and tells you in plain English what's missing.
Legal and Accounts
- A privacy policy and terms page exist, and they describe what the product actually does with data.
- Cookie consent is handled if you need it. If your analytics doesn't use cookies, you may not need a banner at all.
- Your payment provider's account is fully verified and approved for live payments. Some providers take days to review a new account.
One Week Before
Monitoring
- Error tracking is installed, so you hear about exceptions from real users.
- Uptime monitoring checks the homepage and the sign-up flow, and alerts you somewhere you'll see it.
- Scheduled jobs, like nightly emails or billing runs, have heartbeat monitoring, so a job that silently stops gets noticed. CronWatch is what I use for this.
- Analytics is installed and you've checked that visits actually show up in it. I use Runlight on everything now.
- Backups run automatically, and you've restored one at least once to prove they work.
How the Link Looks When Shared
Most people will meet your product as a link in a feed or a chat, so this is your real first impression.
- Every page has a unique
<title>and meta description. - Open Graph and Twitter card tags are set, with a 1200 by 630 image.
- The favicon shows up in browser tabs, and there's an Apple touch icon for phones.
Paste your URL into the Social Card Preview to see how it'll look on X, LinkedIn, Slack, and iMessage before anyone else does. The SERP Preview does the same for Google results.
Search and Crawlers
robots.txtdoesn't block the whole site. This one is more common than you'd think after moving off a staging setup.- There's a
sitemap.xml, and robots.txt points to it. - Staging and preview environments are kept out of search with
noindexor a password. - The site is added to Google Search Console, so you can request indexing on launch day.
The Product Itself
- You've gone through sign-up and the main flow as a brand new user, on a phone as well as a laptop.
- Checkout works in live mode with a real card. Refund it afterwards.
- The empty states make sense, since every new user sees them first.
- There's a real 404 page with a way back.
- The pages load fast on a mobile connection, and images are compressed.
Preflight scans your codebase for most of this before you deploy, and the free Launch Readiness Check runs the website side of it against a live URL in about a minute.
Launch Day
If everything above is done, launch day can be about distribution.
- Pick one or two places where your users actually spend time, and put real care into those posts.
- Post early in the day for your audience's time zone. For Hacker News and most US-centric communities, that's a weekday morning, Eastern time. Product Hunt is the exception, since its day starts at midnight Pacific time and launching then gives you the full 24 hours.
- Write the post for that community, in its own format. A Show HN reads very differently from a Product Hunt launch.
- Stay around for the first few hours and reply to every comment, including the harsh ones.
- Tell your own audience, starting with your newsletter and the people who asked to be told.
If you're not sure where to post, the Launch Platforms Directory lists the launch sites and communities with what each one costs and whether you need an account.
The launch is a lot less scary when you already have a few people waiting for it. If you're launching to nobody, I wrote about building that audience first in Hey, Nobody's Coming.
The Week After
- Fix the bugs people reported, and tell them when you did.
- Reply to every email and DM, even if it's just a thank you.
- Look at where sign-ups actually came from in your analytics, and do more of whatever worked.
- Request indexing for your key pages in Search Console if you haven't.
- Write up how the launch went, with real numbers. People love these posts, and it gives you a second wave of attention.
The boring stuff is exactly what people notice when it breaks.
The fear of pressing the button never fully goes away. I wrote about how I ship anyway in Ship It Scared. Going through a list like this helps a lot, because once the boring stuff is done, the only thing left to worry about is whether people want what you made.
Also by me
Preflight.sh
This checklist is the version you go through by hand. I built Preflight to run the code side of it for you, scanning your codebase before you deploy or in CI, so the boring mistakes get caught long before launch day.