How to Get Featured on Product Hunt: The Criteria

To get featured on Product Hunt, your product has to be a live digital product that scores well on at least one of four things the team says it looks for: useful, novel, high craft or creative. It also must not fall into a category Product Hunt has said it does not feature, such as waitlists, directories, templates, courses, services and stores. There is no form to fill in and no application to make. The team reviews each submission against those written criteria, so the work is making your draft listing pass them before you ever press submit. Below is the criteria set, then an audit you can run on your own draft in about twenty minutes.

That matters because an unfeatured launch is not a failed launch with a low number. It is a launch that happens on a page almost nobody is browsing. You can spend a month preparing, post a careful first comment, answer every reply, and still sit outside the homepage because of something the guidelines would have told you in the first minute. The reasons are written down. So this post quotes the rules, turns each one into a check, and puts the fix next to each way a draft can fail.

Everything quoted here comes from Product Hunt's own help centre, the featuring guidelines, last updated March 2026 when we read it on the day this was published. These are policies, and policies change, so reread that page before you submit.

What does "featured" mean on Product Hunt?

Featured means your launch appears on the Product Hunt homepage, where the day's browsing audience actually looks. Posting a product and featuring a product are two different events. Anyone with an account can post. The team decides what goes on the homepage.

The guidelines open with the reason for the split: "We aim to showcase the newest and most impactful products in tech. While we appreciate all submissions, not every product can be featured on the homepage." The same page says the team reviews each submission against its criteria and that "in the vast majority of cases, our featuring decisions are final and based on the information provided in your submission and provided links."

Read that last part again, because it changes what you do. The decision rests on what you submitted: the name, the tagline, the description, the gallery, the links. It does not rest on how hard you work on launch day, or how many friends you message. The submission is the audition.

This also explains why upvotes are not the lever people assume. Upvotes help rank products that are already on the page. They do not decide whether you get onto it. The guidelines say so directly: "While user engagement is important, it's not the sole factor in our featuring decisions."

What criteria does Product Hunt use?

Product Hunt names two basic requirements and four qualities.

The two requirements are in the "What We Feature" section. The primary focus is "digital products and services", and "We only feature products that are currently available." So a product that works today, which a stranger can open and use, is the baseline.

The four qualities are what the team looks for in a featured launch:

• Useful: "How practical and beneficial is the product for users?"
• Novel: "How innovative or unique is the product in its approach or solution?"
• High Craft: "How well-designed and delightful is the product to use?"
• Creative: "How fun, engaging, or imaginative is the product?"

The page adds the most encouraging line in the whole document: "Featured launches don't need to score high in every category - often they spike in one or two of these." For a solo maker this is the useful part. You are not trying to be the most original, most beautiful, most practical product of the day. You are trying to be clearly strong at one thing, and to make that one thing obvious in your listing.

Then there is the list of what the team does not feature. It is long, and it catches more indie projects than people expect: waitlisted products (unless immediate access is provided), directories or lists, templates, boilerplates, podcasts, courses, reports, events, books, services, commerce sites and stores, deal sites, off-topic submissions, most Kickstarter projects, and hardware without a prominent digital component.

Four further factors can sink a launch even if it avoids that list: vaporware, products that "seem primarily focused on immediate monetization rather than providing long-term value", standards that move as the field moves ("What was novel yesterday may be commonplace today"), and the point above that engagement is not the only measure.

Which listing details get products passed over?

Mostly the ones that make your product look like it belongs on the exclusion list, or that make the strongest quality invisible. Here is the audit. Run it against your draft listing, not against your product in your head. The team only sees the listing.

Check	Pass looks like	Fail looks like	The fix
Live today	A stranger can open the link and use the product in under a minute.	The link is a landing page with a "coming soon" button, or a waitlist form.	Open an early-access path that works now, or wait to launch until it does. The guidelines allow waitlisted products only "if immediate access is provided."
A digital product, not a service	The listing describes software someone operates themselves.	The product is a done-for-you offer, a consultancy, or a store.	Reframe only if it is honestly true. If the thing you sell is a service, it is on the do-not-feature list and no wording will change that.
Not on the exclusion list	The product is not a template, boilerplate, directory, course, report, book or deal site.	It is a Notion template pack, a list of resources, a launch-day discount page.	Ship the working tool inside the template (a generator, a calculator, an app), or pick a different venue for the template itself.
One strong quality, stated early	The first sentence of the listing makes clear whether the point is useful, novel, crafted or creative.	The description lists ten features and the reader cannot tell which one matters.	Choose the quality you actually spike on and lead with it. Cut the feature list to three.
Tagline says the job	A stranger can say what the product does after reading it once.	The tagline is an adjective pile or a slogan.	Rewrite it verb first with one job. We cover the method in how to write an app tagline.
Gallery proves it works	Legible screenshots of the real product, showing the core job being done.	Blurry images, mockups with no product in them, or a gallery of logos.	Retake the images at readable size and show the working state. See screenshots for launch listings.
Not a pure money page	Value is visible before any payment is mentioned.	The first thing a visitor sees is a price and a checkout.	Show what the product does before what it costs, and make a free path obvious if there is one.
Not vaporware	Everything described in the listing exists.	Features are described in the future tense.	Describe only what works today. Move the roadmap out of the listing.
Links work	Every link resolves, and the main one goes to the product.	Dead links, a link to a repository with no running demo, a login wall with no way to sign up.	Click every link in a private window the day before you submit.

Score yourself honestly. A single fail in the first three rows is serious, because those rows are categorical. The rest are about making your best quality easy to read, and they are fixable in an afternoon.

One thing the table does not do is guess at what the team will decide. Nobody outside Product Hunt can tell you that a listing that passes these checks will be featured, and anyone promising it is selling something. The audit raises the chance that your listing is judged on what the product is, instead of being set aside for a reason you could have fixed.

How far ahead should you schedule?

Product Hunt's help centre gives one hard number about scheduling, and you should be careful not to stretch it. In its article on how to schedule a post, the platform says you can use "Schedule Launch" to "pick the day within 30 days of your current day for the post to go live." After that you can keep editing from "My Products," and the post "will not be indexed on the site, and no users will be able to upvote it until the scheduled time."

That is a ceiling of thirty days, not a recommended minimum. The same help centre does not say how many days the team needs to review a submission, and the featuring guidelines state no lead time at all.

You will see a different number repeated in community threads, usually that you should submit at least two weeks in advance and that late submissions are not eligible for the homepage. We could find that claim in a forum discussion, but not on Product Hunt's own pages, so treat it as a report from other makers. It is a reasonable habit anyway, because it leaves time to fix problems. Before you rely on a specific lead time, check the help centre or ask support, and plan around the number it gives you.

There are two more timing facts from Product Hunt's launch preparation guide. It recommends joining the platform "well ahead of your launch (three months or more)", and it says that "Newly created accounts will even need to wait 1 week before posting a product." If your account is brand new, that is a hard schedule constraint, and it is the most common avoidable delay for first-time makers.

The practical plan is simple. Create your account early and use it like a person would. Build the listing as a draft. Run the audit above. Fix what fails. Schedule only after the draft passes. The launch-day mechanics, with a clock, are in the hour-by-hour launch runbook.

What can you do if your launch isn't featured?

Start by reading the guidelines as feedback, not as rejection. They say plainly that "not being featured doesn't reflect negatively on your product's quality or potential." That is true in the sense that the rules are about fit with a particular homepage, not a verdict on your work. A good template, directory or service can be excellent and still not belong there.

Next, resist the urge to lobby. The page says "Reaching out is rarely necessary" and that "Providing additional context does not guarantee that your product will be featured." It asks makers to reach out only with critical information that was missing from the original submission. If your listing had a factual gap, such as a missing link or an access path you forgot to mention, that is the case for a short, polite note. Anything else is a request to reconsider a decision the page calls final in most cases.

Then do the useful thing, which is to treat the launch page as what it still is. Your product has a page and a link. People can still visit it, comment on it and try the product if you send them there. The homepage is the audience you did not get. The comments, the feedback and the first users from your own network are the audience you can still get.

From there, one of three paths makes sense.

1. Fix and relaunch. If the audit found a real fail, such as a waitlist or a thin gallery, repair it and read the rules on repeat launches in our relaunch guide before you try again.
2. Take it somewhere the criteria fit. If your product is a directory, template or service, the featuring rules are not the right test. Pick a venue whose audience wants that kind of thing. There is a sorted list in Product Hunt alternatives for indie apps.
3. Get it in front of people directly. A launch is not the only way to find users. Getting your first 100 people to try your app covers the slower, more reliable route.

Does featuring decide whether a launch works?

No, and it is worth being honest about how much weight to put on it. Featuring decides whether you get the browsing audience of one particular homepage on one particular day. That can be a large amount of attention, and for some products it is the point of launching there. But it does not decide whether people who arrive will try the product, stay, or tell anyone about it.

Those outcomes depend on what a stranger sees in the first minute: whether the tagline says what the thing does, whether the screenshots show it working, whether they can try it without friction. That is the same work the audit asks for. Which means preparing for featuring and preparing for real users are nearly the same job, and doing it well is rarely wasted even when the homepage says no.

If you are still deciding whether the platform is the right room for your app at all, our take on whether Product Hunt is worth it for indie apps goes through the trade honestly. And if you are wondering whether to ask someone with a following to post it for you, the answer is in do you need a hunter on Product Hunt.

Frequently asked questions

Why wasn't my product featured on Product Hunt?

Product Hunt does not give a per-product explanation in the guidelines, so the honest answer is to compare your listing with the written criteria. The common causes are a product that is not yet live, a waitlist without immediate access, a product in an excluded category such as a template, directory, course or service, a listing that mostly reads as a sales page, or a draft where no single quality (useful, novel, high craft, creative) stands out. The audit table above checks each one.

Can you appeal a featuring decision?

The guidelines call featuring decisions final in "the vast majority of cases" and say reaching out "is rarely necessary." They allow contact only when you have "critical information" that was missing from your original submission, and they add that extra context "does not guarantee" a different outcome. So the useful route is to fix the listing and, if it makes sense, launch again under the repeat-launch rules, not to argue the first decision.

Does a landing page count as a product for featuring?

Not on its own. The team only features products that are "currently available", and waitlisted products are excluded unless immediate access is provided. A landing page that leads to a working product someone can use today is fine, because the product is what is being judged. A landing page that collects emails for something that does not exist yet is the pattern the guidelines describe as vaporware or a waitlist.

Are unfeatured launches visible anywhere?

The guidelines only say that not every product can be featured on the homepage. They do not describe where unfeatured products appear in browsing. What you can rely on is that your product has its own page and its own link, so you can send people there and collect comments. Do not plan around organic discovery from an unfeatured launch, because the homepage is where the browsing audience looks.

---

If your product is a live app that people can try for free, there is a place for it that has no featuring test. Submit your app to TryMy free. A person reads each listing before it goes live, and approved apps sit in a browsable showcase next to other things people can actually try. We list only free, free-trial and freemium apps. There is also a featured spot for the top of the grid, and it is a position and a badge, not a traffic guarantee. The free listing is the part that does the work.