Why launches go wrong
Most launch-day problems are boring: a robots.txt left over from staging that blocks the whole site, a link preview with no image, a signup email that lands in spam, a checkout that was never tested with a real card. None of them are hard to fix. They get missed because launch week is busy. A checklist moves them out of your head.
Before launch
The longest section, and the one that matters most. Get the basics right first: one canonical domain over HTTPS, a title tag and meta description, an Open Graph image so shared links look like something, a robots.txt that allows crawling, and a sitemap submitted to Search Console. Then the parts people see: a tagline, a one-line description, a short demo, and posts drafted for each platform while you are calm.
Launch day
Post in the places your users already read, one at a time, and stay for the comments. Answer every reply quickly, ask for feedback rather than votes, and keep an eye on errors and signups. Add your product to SwipeToLaunch for a free listing where people swipe on new products, and check your Show HN title before you post on Hacker News.
After launch
Launch traffic is a spike. What lasts is what you do in the following weeks:
- Thank the people who helped, personally.
- Fix the top complaints and tell the people who raised them.
- Spread more directory submissions over the following weeks rather than in one burst.
- Check which listings gave you a followed link, and note your Domain Rating as a baseline.
- Pick a few keywords to write about, so search traffic builds after launch traffic fades.
Your progress stays with you
Ticks are saved in your browser's local storage. Nothing is sent to our server, and there is no account. Clearing your browser data or switching devices starts a fresh list, so export to Markdown if you want a copy.