⚠️ Caution for 2C Products on Product Hunt

gingiris-seo-geo/references/2c-adaptation.md

gingiris-launch

gr-ph-launch — Product Hunt Launch

In-depth References

• references/framework.md

  — 14-day timeline + 5 core sections

• references/hunter-playbook.md

  — Hunter selection matrix

• references/maker-comment.md

  — 6 maker comment templates

Note: Claude should read

references/framework.md

first before using this skill for the first time.

14-Day Timeline (Simplified Version)

T-14: Preparation

• 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 to T-2: Pre-warming

• 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: Final Check

• 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: Launch Day

• 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 to T+7: Momentum

• 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 Selection Matrix

https://www.producthunt.com/@<category>-hunters

6 Maker Comment Templates

references/maker-comment.md

1. Founder story: Why you built it → Your pain point → Solution
2. Before / After: Contrast between life without your product vs with it
3. Key stats hook: Start with an explosive data point
4. Honest limitation: Admit the product isn't perfect to appear authentic
5. Community thanks: Thank beta users (tag @ specific users)
6. Tech stack pride: Talk about tech stack selection (suitable for developer-focused products)

Risk Avoidance Checklist

• ❌ 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)

Upvote Speed Red Line (Updated with 2026 Tests)

• 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: Budget Tier Benchmark

Launch Day Traffic Reverse Planning Method

Cascade Recommendations

• Launch day +24h →

  gr-seo-patrol

  to monitor keyword rankings like "<product name> product hunt"
• After reaching daily #1 →

  gr-blog-post

  to write a "how we won" post and set canonical to main site
• If there are lots of doubts in comments →

  gr-user-interview

  to start formal interviews

API Dependencies

GITHUB_TOKEN