How to submit a product on Product Hunt: current rules, account requirements and a launch checklist you can date

You submit a product on Product Hunt from an account on the platform, by adding the product with its links, description, images and topics, and the rules that decide whether your submission stands are set by Product Hunt and published on its own pages. One of those rules concerns how new an account may be before it can post, and it is the kind of rule that is precise, checkable and liable to change. We have not made a dated check of the current official page as of 29 September 2026, so this page does not state the rule as a fact. It tells you exactly where to read it, how to record it so your own record does not go stale into a false claim, and what to prepare that no rule change can take away from you. A rule is a concrete thing, unlike a success promise, and the difference is the point of this page.

The answer, first

Four statements.

Rules are better than tactics, and dated rules are better than remembered ones. A platform rule tells you what will happen. A launch tactic tells you what worked for somebody whose conditions you do not know. Collect the rules first, with dates, then decide the tactics.

We do not restate the rules, we name the pages. The three documents to read are the platform's own launch or submission guidelines, its community guidelines, and its help material on accounts and posting. Read the current versions, record the URL and the read date, quote the sentence you are relying on into your sheet, and save a copy of the page. A paraphrase on our page would be wrong the week the rule changes, and it would be wrong in a way that looks authoritative.

Account age and account history are the rules people learn about too late. Platforms of this kind commonly require an account to exist for some period, or to have some history, before it can post or before a post counts. Whether that applies, in what form, and for how long is on the official page. Read it before you set a launch date, not after, and write the exact wording into your plan with the date you read it.

No rule and no checklist can promise you attention on the day. What a checklist can do is remove every avoidable reason for the launch to fail, which is a smaller claim and a true one.

How it was measured

There are two things to measure here, and neither of them is somebody else's launch.

The rule record, in seven fields. One row per rule you intend to rely on.

• The rule in the platform's own words, quoted, not summarised.
• Which document it came from, with the full URL.
• The date and time you read it.
• Any last updated stamp printed on the page.
• Whether the rule is stated as a requirement or as guidance.
• What you must do or hold to satisfy it, and whether you can verify that yourself today.
• The date of your next recheck, which for a launch should be the week before you post.

Quoting rather than summarising is the whole discipline. A summary of a rule is a new rule that nobody wrote, and it is the form in which wrong information about platforms spreads.

The launch readiness checklist, in the eleven items that are under your control. None of these depends on the platform, which is why they are worth doing first.

• A live product page that loads for a signed out visitor with no account required.
• A working way to try the product: a free tier, a trial, a sandbox, or a booked demo with a real calendar behind it.
• A stated price or a stated pricing model, with a date on the page.
• A one sentence description of what the product does, in the words a buyer would use, identical everywhere it appears.
• A named category, chosen to match how buyers describe the problem rather than how you describe the technology.
• Images and a short video that make sense with no sound and no explanation.
• A support contact that a person answers, and a stated response time.
• A public page listing what the product does not do and who should choose something else.
• A page answering the awkward commercial question in your category, such as what the total cost includes.
• Working links: every URL in the submission opened in a private browser window on a phone.
• A named person on duty for the whole launch day to answer comments, with nothing else in their calendar.

And the measurement worth running around a launch, in five steps. If part of the reason to launch is to be findable afterwards, measure it blind, before and after.

• Freeze 20 to 100 buyer questions in a versioned file, dated, and do not edit the file during the study.
• Put your brand name in none of them. The reason is measured: on 27 July 2026, two runs of the same 78 questions happened on the same day for clawlaw.in, the branded run returned the company first on almost every question, the blind run put it second by breadth and absent from the litigation due diligence questions it most wanted to win, and the branded run was discarded because it had only measured our own prompt.
• Ask each question three times per assistant and keep all three answers, because answers to identical words differ within a day.
• Print the arithmetic: 20 questions times 3 repetitions times 3 assistants is 180 answers, so 5 answers naming you is 5 of 180 on the named dates, and never a percentage on its own.
• Record any statement about whether a search was run as a claim, not a fact. In the aiknowsus.com audit of September 2026, Perplexity withdrew its own earlier statement when asked how many questions it had searched for, saying it could not honestly substantiate the claim, and in another batch that its claim to have searched all five was not adequately supported. Three separate batches.

What the numbers were

Dated checks of this platform's current submission rules completed by us: zero, as of 29 September 2026. So no account age figure, no timing rule and no threshold is stated as a fact anywhere on this page. Read the official pages and write down what you find.

Product launches we have run on this platform and measured: zero. There is no launch day result here, no upvote count, no traffic figure and no conversion number. Every one of those would be invented.

The one dated result we hold about a page becoming findable, with its sector named. On 6 August 2026, ChatGPT cited clawlaw.in/blog/how-to-check-a-companys-court-cases-in-india as a source for a vendor due diligence question, fourteen days after that page was published, in a zone where the same question set had named the company nowhere at baseline. Legal research software sold in India. That is one page, one citation, one date. Fourteen days is how long that one took. It is not how long anything takes, and it is not a launch result.

Two more counts, with their denominators, for expectation setting.

• 1 of 18. Across eighteen blind commercial questions on 18 August 2026, ChatGPT made clawlaw.in the top source on exactly one. Legal research software, India.
• 161 across 24 batches and 72 conversations. On aiknowsus.com in September 2026, the phrase recording that we were not cited appears 161 times in the engines' own self audits of their answers. Perplexity.

A launch is a day. Being findable is a programme. The second number is there to make that plain.

What this cannot tell you

• It cannot tell you the current rules. That is deliberate, and the record format above is the substitute.
• It cannot tell you what launch day will do for you. We have not run one and will not describe one.
• The eleven checklist items remove reasons to fail. They do not create attention, and no list can.
• Our one citation observation is a single event. Fourteen days from publication to citation happened once, for one page, in one sector, and reading it as a timeline would be exactly the error this page is written to avoid.
• A blind prompt study measures your prompt set on your dates, not the market.
• Nothing here promises a position in an AI answer or a position on any leaderboard.

Sources and change log

Sources. The rule record format, the eleven item checklist and the blind protocol are ours. The dated results come from the clawlaw.in programme, recorded in Tier_1/GEO_BASELINE_RESULTS_2026-07-27.md and Tier_1/GEO_GAP_ANALYSIS_2026-08-18.md, and from the aiknowsus.com audit of September 2026 across 24 batches and 72 conversations. The 6 August 2026 citation names a public URL and can be checked from outside. The capture wide counts cannot, until the captures are published. No sentence here paraphrases Product Hunt's documentation.

Change log. 29 September 2026, first publication, stating that no dated rule check has been made. When it is, this section will carry each rule quoted in the platform's own words, with its URL, its read date and any last updated stamp. If a rule changes after we record it, the old row stays and the new row goes above it, so the page shows the change rather than hiding it.

Common questions

Can we create an account and launch the same day?

Read the current official page on accounts and posting before you plan the date, and quote what it says into your sheet with the read date. Rules of this kind exist on many platforms and they change, so the only safe answer is the one you read yourself this week. Plan the launch date after that, not before.

Who should post the product, the founder or a supporter?

That is governed by the platform's own rules on who may post and how a maker is identified, so read those rather than a tactic from a blog. What is true regardless: the person who posts has to be available all day to answer comments, and that has to be their only job that day.

What is the most common avoidable launch failure?

We have not measured launches, so we will not rank causes. From the eleven item list, the two that are cheapest to check and most often wrong are links that fail for a signed out visitor and a product page that requires an account before anybody can see what the product does. Test both in a private browser window on a phone.

Does a launch help AI assistants describe us?

It creates public pages about you, which can help. What we can show is one dated case of a page becoming a cited source: on 6 August 2026 ChatGPT cited a specific clawlaw.in page fourteen days after it was published. That page answered one buyer question directly. It was not a launch post, and one event is not a pattern.

Should we prepare answers to comments in advance?

Prepare the facts, not the sentences. Have the price, the limits, the support contact and the "who should not buy this" answer written down and agreed, so that whoever is on duty answers consistently. On 6 August 2026 a headline figure on the clawlaw.in site could not be true, and when Claude checked it against public numbers it advised a buyer against the product. A launch day is the worst possible time to discover that one of your own numbers cannot be supported.

How soon should we measure whether anything changed?

Run the blind prompt set once before the launch and again four weeks after, with the file unedited between the two runs. Report both as counts out of the same denominator, with the dates. A change after a change is not proof of a cause, and it is still the only honest way to look.

What to do first

Read the three official documents today and write each rule you will rely on into a seven field row, quoted, with the URL and the read date. Then work through the eleven checklist items and fix the ones that fail in a private browser window on a phone. Set your launch date only after the rule rows are filled in, and recheck them the week before you post.