# Launch Checklist

> Prepare and run a public product launch: technical readiness (indexing, Open Graph previews, analytics, error monitoring, status page, capacity), launch copy that is specific rather than hype, and community-platform etiquette for Product Hunt and Show HN based on their published rules (no vote solicitation, maker present to answer, easy to try). Use this skill when planning a launch day, posting to Product Hunt or Hacker News, preparing share previews, or reviewing launch copy. Activate when: launch checklist, product launch, launch day, Product Hunt, Show HN, Hacker News, launch post, OG image, Open Graph, social preview, go-live checklist.

- Skill: `latestaiagents/launch-checklist` (Agent Skill)
- Install (CLI): `npx get-skill add latestaiagents/launch-checklist`
- Raw SKILL.md: https://api.skillmd.com/api/skills/latestaiagents/launch-checklist/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: latestaiagents (https://skillmd.com/u/latestaiagents)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/latestaiagents/launch-checklist

---


# Launch Checklist

**Make the product easy to try, easy to share, and safe to receive traffic; then follow each community's rules exactly.**

A launch cannot guarantee rankings, upvotes, or signups. This checklist removes avoidable failures and keeps you within platform rules.

## When to Use

- One to two weeks before a public launch or major release
- Before posting to Product Hunt or Hacker News (Show HN)
- Reviewing launch copy, share images, or the go-live runbook

## When NOT to Use

- Ongoing SEO work (use `technical-seo-audit`)
- Paid campaign setup; this skill covers organic launches

## Workflow

### Step 1: Technical readiness (T-7 days)

| Area | Check | How to verify |
|------|-------|---------------|
| Indexing | Production does not carry staging `noindex` or `Disallow: /` | `curl -sI https://site/ \| grep -i x-robots-tag`; read `/robots.txt` |
| Canonical host | One host (www or apex), others 301 to it | `curl -sIL http://site/` |
| Sitemap | Lists launch pages; submitted in Search Console | Search Console Sitemaps report |
| Share previews | `og:title`, `og:type`, `og:image`, `og:url` present (the four properties the Open Graph protocol marks required), plus `og:description` and `og:image:alt` | View source; test in each platform's own preview/debug tool |
| Analytics | Key events fire (signup, activation) in production, consent handled per your jurisdiction | Real-time view while clicking through |
| Errors | Error monitoring and alerting on; someone on call | Trigger a test error |
| Capacity | Rate limits, queues, and third-party quotas reviewed for a traffic spike | Load test the signup path |
| Status | A status page or status channel exists and is linked | Open it logged out |
| Rollback | Previous version can be restored quickly | Rehearse once |

Open Graph example:

```html
<meta property="og:title" content="Acme Queue: background jobs for Node.js" />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://acme.dev/" />
<meta property="og:image" content="https://acme.dev/og/home.png" />
<meta property="og:image:alt" content="Acme Queue dashboard showing three running jobs" />
<meta property="og:description" content="Retries, schedules, and a dashboard. Open source, MIT." />
```

Use absolute URLs. Image size and aspect recommendations differ per platform and change; check each platform's current docs rather than trusting a remembered number.

### Step 2: Make it easy to try (T-5 days)

- A demo, playground, free tier, or open-source repo reachable in one click.
- Avoid forced email capture before people can see the product. Show HN asks for this explicitly: "ideally without barriers such as signups or emails".
- A short video or screenshots that show the product doing its main job.
- Pricing visible, or clearly stated as free.

### Step 3: Write specific launch copy (T-3 days)

- Lead with what it does and who it is for, in one sentence a stranger understands.
- Replace adjectives with facts: what it integrates with, what it costs, what it does not do yet.
- No unverifiable claims ("fastest", "10x"). If you cite a number, link the method.
- Write a first comment from the maker: why you built it, what is rough, what feedback you want.

| Instead of | Write |
|-----------|-------|
| "The future of productivity" | "A menu-bar timer that logs focus sessions to a CSV" |
| "Blazing fast AI-powered search" | "Searches your Markdown notes locally; no account required" |

### Step 4: Product Hunt

From Product Hunt's own launch guide and community guidelines (checked 2026-11-04):

- Post from a personal account representing a real individual; company or brand accounts may not post, vote, or comment.
- Newly created accounts must wait one week before posting; Product Hunt recommends joining well before launch.
- Makers can hunt their own product; a third-party hunter is not required.
- Ask for feedback, comments, and help spreading the word, **not upvotes**. Mass messaging, asking for upvotes, bots, and incentivized upvotes are against the rules and can lead to removal or unfeaturing.
- Do not run contests that require or reward upvotes.
- Self-promotional comments are removed; reply to people genuinely.
- Ranking considers more than upvotes and Product Hunt does not publish the algorithm.

Launch-day timing and asset specs (tagline length, gallery sizes) are set by Product Hunt and can change: read the current launch guide when you schedule.

### Step 5: Show HN

From the Show HN rules and HN guidelines (checked 2026-11-04):

- Title starts with `Show HN:`. Do not add uppercase, exclamation points, or hype.
- It must be something you made that people can try. Not allowed: blog posts, sign-up pages, newsletters, lists, other reading material, landing pages, fundraisers. Minor upgrades ("Foo 1.3.1 is out") generally do not qualify.
- You must be around to discuss it. Answer questions directly and without defensiveness.
- "Please don't ask friends to upvote or comment." HN guidelines: "Don't solicit upvotes, comments, or submissions."
- Posting your own work is fine part of the time; HN should not be used primarily for promotion.

Example title: `Show HN: Acme Queue - open-source background jobs for Node.js`

### Step 6: Launch day runbook

```markdown
- [ ] T-0: post goes live; maker comment posted
- [ ] Share the direct link with your own users and community (no vote requests)
- [ ] One person monitors errors, latency, and signups
- [ ] One person answers comments on each platform
- [ ] Log every bug report and feature request in one place
- [ ] Status page updated if anything degrades
```

### Step 7: After launch (T+1 to T+7)

- Thank commenters; follow up on reported bugs with fixes.
- Write down what happened (traffic sources, activation, issues) with numbers from your own analytics, not estimates.
- Turn repeated questions into docs or FAQ entries.

## Best Practices

1. Verify production indexing and share previews before anything else.
2. Remove signup walls from the first experience where possible.
3. Specific, factual copy beats superlatives; never claim what you cannot show.
4. Never ask for upvotes on any platform; ask for feedback.
5. Have the maker present and responsive for the whole launch day.
6. Staff monitoring and support separately from community replies.
7. Re-read each platform's current rules before posting; they change.

## References

Checked 2026-11-04:

- Show HN rules: https://news.ycombinator.com/showhn.html
- Hacker News guidelines: https://news.ycombinator.com/newsguidelines.html
- Product Hunt launch guide (before launch): https://www.producthunt.com/launch/before-launch
- Product Hunt sharing your launch: https://www.producthunt.com/launch/sharing-your-launch
- Product Hunt how it works: https://www.producthunt.com/launch/how-product-hunt-works
- Product Hunt community guidelines: https://help.producthunt.com/en/articles/3615694-community-guidelines
- Open Graph protocol: https://ogp.me/
- Google noindex and robots.txt: https://developers.google.com/search/docs/crawling-indexing/block-indexing

