The short answer
Before you post anywhere, make the product easy to try and easy to understand: a public pricing page, a clear one-line description, a share image and a page that loads for crawlers. Follow each channel’s own rules. Product Hunt and Hacker News prohibit soliciting upvotes, and Show HN recommends avoiding signup barriers. Hacker News also prohibits generated text and automated posting. Give directories complete, accurate product details.
| Channel | Rule to know | Source |
|---|---|---|
| Product Hunt | Tagline up to 60 characters; schedule within 30 days; scheduled launches go live at 12:01 a.m. Pacific; ask for feedback, not upvotes | Product Hunt launch guide and Help Center |
| Hacker News (Show HN) | Non-trivial work people can try; no quick one-offs or routine upgrades (major overhauls may qualify); no vote or comment solicitation, generated text or automated posting | Show HN and Hacker News guidelines |
| X | Share cards are cached; change the image URL, or share a fresh page URL, when you update the image | Our own experience |
| SOTA | Submissions reviewed against official sources before publication; inclusion is not guaranteed | SOTA submission page |
Before launch day
Make the product easy to try. Show HN recommends removing signup or email barriers so users can try your work and give feedback.
Publish a pricing page that loads without logging in, even if the answer is 'free during beta'. Include the billing period, usage allowance and known limits.
Write one sentence that says what the product does and for whom, and use it everywhere: your homepage title and description, your Product Hunt tagline and your directory listings. Consistent wording helps people, search engines and AI assistants connect the mentions.
Check the page that will be shared: a share image, a title and description, and content that appears before JavaScript runs. Our guides on SEO basics and on getting found by AI assistants cover what to check.
Product Hunt
Checked October 30, 2026: Product Hunt’s Help Center allows scheduling within 30 days of the current date. Its current launch guide says every launch goes live at 12:01 a.m. Pacific on its scheduled date and caps the tagline at 60 characters. The preparing-for-launch page also asks for a tagline with no gimmicks.
Use a square thumbnail; Product Hunt recommends 240 by 240 pixels and says thumbnail images must be under 3 MB. GIF thumbnails animate only on hover, so choose a first frame that works on its own. The gallery needs at least two images before it is viewable; the recommended gallery size is 1270 by 760 pixels.
Post a first comment as the maker: the preparing-for-launch page still reports that 70% of products that reached Product of the Day, Week or Month had one. Share your launch, but ask for feedback, not upvotes; the current Help Center launch guide says soliciting upvotes can disqualify a launch.
Hacker News: Show HN
Show HN is for something you made that people can try. Blog posts, landing pages, sign-up pages and fundraisers are off-topic, and you should be around to answer questions in the thread.
The project should be non-trivial; quickly generated one-offs are not suitable for Show HN. New features and routine version upgrades generally are not substantive enough, though a major overhaul may qualify.
Do not solicit upvotes or comments. Use a plain title beginning with 'Show HN:' and write your explanation yourself. The general HN guidelines prohibit generated text in posts, generated or AI-edited comments, and automated posting. They also ask you not to use HN primarily for promotion, and the HN FAQ asks you not to delete and repost the same story.
Directories, including SOTA
For each directory you choose, supply the same core facts: what the product does, who it is for, pricing and known limits. Use documented limitations and check the submission requirements before sending.
SOTA checks official sources and reviews submissions before publication; submitting does not guarantee inclusion. Use its form to review an AI draft or enter a name and summary, then submit a public GitHub Issue. The SOTA agent skill can also prepare a listing from your official website for review.
After launch: what we see go wrong
While building the SOTA catalog, we met many renames and moves, and some old domains stopped working without redirecting. If you rename or move the product, map old URLs to their corresponding new pages. Google’s site-move documentation recommends server-side permanent redirects, such as HTTP 301 or 308, where possible. Keep the old name on your site for a while so returning users can recognize it.
Keep facts current. Free-plan limits and prices change often, and outdated details in directories and AI answers outlive the change. A public changelog and a dated pricing page make updates easy to pick up.
Sources & method
Official documentation was checked on 2026-10-30. Selection advice is our assessment. Interfaces and requirements may change; check the linked source for the version you intend to use.
- Product Hunt: Preparing for launch
- Hacker News: Show HN guidelines
- SOTA: Submit a product
- SOTA agent skill
- SEO basics for a new AI product site (SOTA guide)
- How to get your AI product found by ChatGPT, Claude and Perplexity (SOTA guide)
- Product Hunt Help Center: How to schedule a post
- Product Hunt Help Center: How to post a product
- Product Hunt Help Center: Launch Guide
- Hacker News guidelines
- Google Search Central: Site moves with URL changes
- Hacker News FAQ
How SOTA reviews projects · Suggest a correction · Download the evaluation checklist