gr-ph-launch
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese⚠️ 2C 产品慎用 Product Hunt
⚠️ Caution for 2C Products on Product Hunt
本 skill 默认 dev / maker / B2B 受众。2C 消费品 / 教育 / 应用 / 游戏：Product Hunt 受众是 maker/科技人，与普通消费者错配、ROI 极低——最多发一次拿个 badge。请把精力换到 垂类社区（Reddit / 小红书 / 知乎 / Naver 카페）+ 短视频（TikTok / 抖音 / YouTube）+ 垂直 KOL，并用"免费产品当钩子"做转化。完整 2C 渠道数据库（各国 MAU + 公开来源）+ 三路 Launch 分叉见 → （及 ）。
gingiris-seo-geo/references/2c-adaptation.mdgingiris-launchThis skill defaults to dev / maker / B2B audiences. 2C consumer goods / education / apps / games: Product Hunt's audience is makers/tech professionals, which mismatches with ordinary consumers and results in extremely low ROI — at most, launch once to get a badge. Please shift your focus to vertical communities (Reddit / Xiaohongshu / Zhihu / Naver 카페) + short videos (TikTok / Douyin / YouTube) + vertical KOLs, and use "free products as hooks" for conversion. Complete 2C channel database (country-specific MAU + public sources) + three-way Launch fork see → (and ).
gingiris-seo-geo/references/2c-adaptation.mdgingiris-launchgr-ph-launch — Product Hunt 发布
gr-ph-launch — Product Hunt Launch
深度参考
In-depth References
详细方法论与案例库见：
- —— 14 天时间线 + 5 大板块
references/framework.md - —— hunter 选择矩阵
references/hunter-playbook.md - —— maker comment 6 种模板
references/maker-comment.md
注：首次使用时 Claude 应读再开始。references/framework.md
Detailed methodology and case library:
- — 14-day timeline + 5 core sections
references/framework.md - — Hunter selection matrix
references/hunter-playbook.md - — 6 maker comment templates
references/maker-comment.md
Note: Claude should readfirst before using this skill for the first time.references/framework.md
14 天时间线（精简版）
14-Day Timeline (Simplified Version)
T-14：准备
T-14: Preparation
- 产品页面就绪（落地页、定价、FAQ）
- 已有 ≥ 100 早鸟用户 + 邮箱列表
- 选 1 个 hunter（优先级：活跃 > follower 数）
- 筹备 3 张主 gallery 图 + 1 个 30 秒 demo video
- Product page ready (landing page, pricing, FAQ)
- Have ≥100 early adopters + email list
- Select 1 hunter (priority: activity > follower count)
- Prepare 3 main gallery images + 1 30-second demo video
T-7 到 T-2：预热
T-7 to T-2: Pre-warming
- PH discussion 板块发 1 篇"we're launching, AMA"
- Twitter / LinkedIn / Reddit 预告（不贴 launch 页面链接，避免抢流量）
- Newsletter 给用户打招呼
- 确认 hunter 时区 + 发布时间（PST 00:01）
- Post a "we're launching, AMA" in PH discussion section
- Tease on Twitter / LinkedIn / Reddit (do not post launch page link to avoid traffic diversion)
- Greet users via newsletter
- Confirm hunter's time zone + launch time (PST 00:01)
T-1：终检
T-1: Final Check
- 所有 asset 最终版锁定
- 准备 first comment 文稿（500 字以内）
- 准备 10 条可能的 FAQ 回复模板
- 联系 10-20 个核心支持者提醒明早
- Lock all final versions of assets
- Prepare first comment draft (within 500 words)
- Prepare 10 possible FAQ response templates
- Contact 10-20 core supporters to remind them of tomorrow morning
T-0：发布日
T-0: Launch Day
- 00:01 PST hunter 发布
- 00:15 maker（你）发 first comment
- 整天：每 30 分钟回一批评论；不刷 upvote
- 14:00 PST：peak time，推 second wave（通讯录 + community）
- 23:00 PST：总结发一条感谢帖
- 00:01 PST Hunter launches the product
- 00:15 Maker (you) posts first comment
- All day: Reply to batches of comments every 30 minutes; do not刷 upvote
- 14:00 PST: Peak time, push second wave (contact list + community)
- 23:00 PST: Post a thank-you note to summarize
T+1 到 T+7：momentum
T+1 to T+7: Momentum
- 回完所有评论（包括差评）
- 把 PH featured 截图 + 数据做成 case study
- 若进入 daily #1 → 做一篇"how we won"博客（）
gr-blog-post - 将所有 upvoter 邮箱导入用户池
- Reply to all comments (including negative ones)
- Create a case study with PH featured screenshot + data
- If ranking daily #1 → Write a "how we won" blog post ()
gr-blog-post - Import all upvoters' emails into user pool
Hunter 选择矩阵
Hunter Selection Matrix
| 优先级 | 标准 |
|---|---|
| P0 | 最近 30 天有成功 hunt 且产品领域相似 |
| P1 | Follower 1k+ 且活跃（每周发帖） |
| P2 | 跟你有真实社交关系（聊过、共同朋友） |
| ❌ | Follower > 50k 但已 6 个月没 hunt |
搜 hunter：
https://www.producthunt.com/@<category>-hunters| Priority | Criteria |
|---|---|
| P0 | Has successful hunts in the last 30 days and operates in similar product domains |
| P1 | 1k+ followers and active (posts weekly) |
| P2 | Has real social connections with you (talked before, mutual friends) |
| ❌ | >50k followers but hasn't hunted in 6 months |
Search hunters:
https://www.producthunt.com/@<category>-huntersMaker Comment 6 种模板
6 Maker Comment Templates
（详见 ）
references/maker-comment.md- Founder story：为什么做 → 你的痛 → 解法
- Before / After：有你的产品前 vs 后，对比鲜明
- Key stats hook：一个爆炸性数据开头
- Honest limitation：承认产品还不完美，显得真实
- Community thanks：感谢参与测试的用户（点名 @）
- Tech stack pride：讲技术选型（适合开发者向产品）
选哪个：看目标受众。To dev → 6；to general → 1 或 3。
(See details in )
references/maker-comment.md- Founder story: Why you built it → Your pain point → Solution
- Before / After: Contrast between life without your product vs with it
- Key stats hook: Start with an explosive data point
- Honest limitation: Admit the product isn't perfect to appear authentic
- Community thanks: Thank beta users (tag @ specific users)
- Tech stack pride: Talk about tech stack selection (suitable for developer-focused products)
Which to choose: Depends on target audience. For devs → 6; for general audience → 1 or 3.
反踩雷清单
Risk Avoidance Checklist
- ❌ 不要在 launch 当天还在改产品（flaky）
- ❌ 不要让家人朋友刷 upvote（PH shadowban 很快）
- ❌ 不要在 first comment 留外部链接（触发审核降权）
- ❌ 不要忘记 mobile 截图（40% 流量来自手机）
- ❌ 不要硬撑 daily #1，#2-#3 也是成功（且少被喷）
- ❌ Don't modify the product on launch day (flaky)
- ❌ Don't ask family/friends to刷 upvote (PH shadowban is fast)
- ❌ Don't include external links in first comment (triggers review and demotion)
- ❌ Don't forget mobile screenshots (40% of traffic comes from mobile)
- ❌ Don't force daily #1, #2-#3 are also successes (and less likely to be criticized)
上票控速红线（2026 实测更新）
Upvote Speed Red Line (Updated with 2026 Tests)
- 总量 ≤100 票/小时、单一渠道 ≤30 票/小时——PH 约每 2 小时清一次可疑票，突刺会被剥掉
- 支持者用**手机 + 蜂窝数据（4G）**投票，别挤同一个办公室 Wi-Fi
- badge 曝光分层：周榜 ≈ 日榜 7 倍、月榜 ≈ 30 倍——先定冲哪个榜再定节奏；冲月榜选每月第二/三周的周二
- Total ≤100 votes/hour, single channel ≤30 votes/hour — PH clears suspicious votes every ~2 hours, sudden spikes will be removed
- Supporters should vote via mobile + cellular data (4G), don't use the same office Wi-Fi
- Badge exposure tiers: Weekly list ≈7x daily list, monthly list≈30x daily list — Decide which list to target first to set rhythm; choose Tuesday of the second/third week of the month for monthly list
Go / no-go：预算分级基准
Go / No-go: Budget Tier Benchmark
| 预算 | 现实产出 |
|---|---|
| ~$1K | 小几百注册（跳过 PH，直接 KOC + 垂直社区） |
| $5K | 24h 约 1,800 票可达——实战案例：冲上日榜第一后被 PH 事后清票收回。控速红线必须遵守 |
| $1–2 万 | ~100 万曝光 + 小几千注册 |
预算不高别卷 PH：同预算给 ~10 个 Twitter KOL/KOC 曝光和注册都更高——PH 曝光→upvote 转化仅 ~1%，Reddit 开源宣发曝光→star 转化 5–8%。
| Budget | Realistic Output |
|---|---|
| ~$1K | A few hundred sign-ups (skip PH, go straight to KOC + vertical communities) |
| $5K | ~1,800 votes in 24h achievable — Practical case: Reached daily #1 then had votes cleared by PH afterwards. Must follow speed red lines |
| $1–20K | ~1M impressions + a few thousand sign-ups |
Don't compete on PH with low budget: Same budget gives higher impressions and sign-ups from ~10 Twitter KOLs/KOCs — PH impression→upvote conversion is only ~1%, while Reddit open-source promotion impression→star conversion is 5–8%.
发布日流量倒排法
Launch Day Traffic Reverse Planning Method
先定总流量盘子 → 拆每渠道硬数字 → 每渠道 UTM 短链归因。
实测（某 AI Agent 产品，2025-12）：50 万流量 = 40 万 Twitter（40 红人 quote）+ 2 万 Reddit + 2 万 YouTube 投流 + 2 万群组 + 其余 → 约 800 注册、CAC $6.25。
进阶节奏：双日结构（发布日一半红人导官网、打榜日另一半导 PH）；KOL 集中爆破（50–100 个 KOL 约定 24–48h 内密集发布）。
First set total traffic target → Break down hard numbers per channel → Attribute via UTM short links per channel.
Test data (an AI Agent product, Dec 2025): 500K traffic = 400K from Twitter (40 influencer quotes) + 20K from Reddit + 20K from YouTube ads + 20K from groups + others → ~800 sign-ups, CAC $6.25.
Advanced rhythm: Two-day structure (half influencers direct to official website on launch day, half direct to PH on ranking day); KOL concentrated burst (50–100 KOLs agree to post intensively within 24–48h).
级联推荐
Cascade Recommendations
- 发布日 + 24h → 监控"<product name> product hunt"等关键词排名
gr-seo-patrol - 上 daily #1 后 → 写一篇"how we won"并设 canonical 为主
gr-blog-post - 评论有大量质疑 → 启动正式访谈
gr-user-interview
- Launch day +24h → to monitor keyword rankings like "<product name> product hunt"
gr-seo-patrol - After reaching daily #1 → to write a "how we won" post and set canonical to main site
gr-blog-post - If there are lots of doubts in comments → to start formal interviews
gr-user-interview
API 依赖
API Dependencies
| Service | Env var |
|---|---|
| Product Hunt（公开页爬取） | 无（用 web-access skill） |
| GitHub PAT（博客联动） | |
| Service | Env var |
|---|---|
| Product Hunt (public page crawling) | None (use web-access skill) |
| GitHub PAT (blog linkage) | |