TL;DR
The link on your Hacker News submission is nofollow. The value comes from the echo: the wave of backlinks from the hundreds of sites that scrape HN, a measurable Domain Rating bump, secondary coverage and AI citations.
The fastest way to fail is to treat HN like Product Hunt with worse design. It’s a discussion community that punishes marketing language, hype titles and anything that smells like a traffic grab.
Ranking is decided in the first 60–90 minutes by genuine early vote velocity. There are only 30 front-page slots and the feed turns over fast, so most submissions die in /new.
Vote rings and soliciting upvotes don’t just fail — they get your URL shadowbanned or your domain banned for life. That’s the reputation you’re protecting.
Comments are often a better, lower-risk channel than submissions. Being the genuinely useful voice in relevant threads compounds quietly for months.
Use the Fit-and-Risk Scorecard and the two-week Show HN plan below before you post anything.
Hacker News is not Product Hunt — and confusing the two is how you get burned
If you’ve run a Product Hunt launch, you might be tempted to treat Hacker News as the same game on a uglier site. Don’t. That confusion is the single most expensive mistake founders make here. Product Hunt is a launch platform; the community expects to be marketed to. Hacker News is a discussion community of engineers, founders and technical sceptics who will punish anything that reads like a press release — and the punishment can be permanent.
Start with the same uncomfortable fact we covered for Product Hunt: the link on your submission is nofollow. HN won’t pass authority to your domain through the post itself. So if your only goal is “one juicy backlink,” you’ve misread the channel. The links that matter come from what a front-page hit sets off, not from the post.
But Hacker News carries something Product Hunt doesn’t: a genuine downside. Get the culture wrong — solicit upvotes, post hype, run a little voting ring with your team — and HN’s ring detection can shadowban your URL or ban your domain for life. There is no appeal queue that reliably reverses it. That’s why this guide is framed around reputation: the upside is real, but it’s the one channel where a clumsy move can cost you the asset entirely.
Hold two ideas together and the rest follows. First, the reward is an echo, not a direct link. Second, the risk is to your reputation and your domain, not just to a single campaign. Everything below is about maximising the first while never touching the second. For where this sits in the wider toolkit, it’s one channel among many in our complete guide to the link building strategies that work in 2026 — just one that demands more care than most.
It’s worth being honest about why this channel is worth the effort at all, given the risk. Hacker News is one of the few places left on the internet where an unknown founder with a genuinely interesting build can outrank a well-funded competitor on merit alone. There’s no ad budget to buy your way past, no follower count that guarantees reach. The community decides, in public, in real time, whether what you made is interesting. When it decides yes, the payoff — technical users, durable links, credibility — is hard to replicate anywhere else. When it decides no, you’ve usually lost nothing but an afternoon. The only way to turn a no into a real loss is to cheat, which is exactly why the rules below matter more than the tactics.
First, the deliverable: the HN Fit-and-Risk Scorecard
Before you even draft a title, work out whether you should be posting at all — and in what format. Score each row 0 to 3, total it, and read the verdict. This keeps you from spending your reputation on a post that was never going to land.
| Factor | What a 3 looks like | Your score |
| Content fit | A technical deep-dive, a real build, original data, or an honest founder story — not launch copy or a listicle. | 0–3 |
| Trial-ability | People can actually use the thing right now — a working demo, runnable software, a usable site (required for Show HN). | 0–3 |
| Account standing | An aged account with a real history of useful technical comments — not a same-day account that only ever posts its own links. | 0–3 |
| Live presence | You can be glued to the thread, replying thoughtfully, for the first two to three hours after posting. | 0–3 |
| Thick skin | You can take blunt, public criticism calmly and answer it honestly rather than defensively. | 0–3 |
| Capture readiness | Your landing page handles a traffic surge, captures emails, and your own pages are structured to be cited later. | 0–3 |
Read your total:
- 14–18 — Post it. You have genuine fit and the temperament to handle the thread. Use the two-week plan below.
- 9–13 — Fix the weak rows first. If account standing is low, build a comment history before you ever submit your own link. If trial-ability is low, you don’t have a Show HN — reframe as a technical write-up.
- 0–8 — Don’t submit. Either the content isn’t a fit or the risk to your reputation outweighs the upside. Start by commenting usefully instead (more on that below).
The 30-second format picker
- Show HN — only when people can try something you personally made: software they can run, a site they can use, hardware you can demo. Blog posts, newsletters, lists and sign-up pages are explicitly not Show HNs.
- Link submission — for a technical essay, research, or a deep write-up where the article itself is the thing. Submit the original source with a neutral, factual title.
- Ask HN — only when you genuinely want the community’s answers. An Ask HN that’s a launch in disguise gets seen through instantly.
How Hacker News ranking actually works in 2026
You can’t earn the echo without surviving the algorithm, and HN’s is unforgiving by design. The platform draws something like 15 million visits a month, but there are only 30 slots on the front page, 300–400 new posts arrive daily, and the feed turns over every 60–90 minutes. Most submissions never escape the /new page where they land.
Early velocity beats raw volume
The ranking score is time-decayed. HN applies a gravity multiplier that rises roughly every 45 minutes, so a post that earns ten genuine upvotes in its first fifteen minutes will outrank one that crawls to fifty over six hours. To graduate out of /new and onto the front page, founder analyses suggest you need on the order of eight to ten real upvotes and a couple of thoughtful comments within the first half hour. The first 60 to 90 minutes decide almost everything.
There’s no magic posting hour that rescues weak content, but timing matters at the margin because you want your audience awake and at their desks. The consistent advice across 2026 write-ups: aim for Tuesday to Thursday, roughly 8–10am US Eastern, when engineers check the news before stand-up and the West Coast comes online by the end of the window. Sunday evening is a solid second choice — lower competition, a more exploratory crowd. Avoid Monday mornings and Friday afternoons.
It helps to picture what graduation actually looks like. Every new submission lands in /new, the firehose where most posts quietly die. A handful of early upvotes from people genuinely browsing /new lift a post out and onto the lower reaches of the front page, where the much larger front-page audience can find it. From there it either gathers momentum and climbs, or stalls and slides back down as the time-decay catches up. The whole arc — from posting to peak to fading — often plays out inside a single day. This is why being present in the first hour isn’t optional: the post needs early signal to escape /new at all, and that signal has to be real.
Flags, moderators and the second-chance pool
Votes aren’t the only force acting on your post. Readers can flag submissions, software can kill threads that look like spam, and moderators intervene by hand. The flip side is gentler than founders expect: HN runs a second-chance pool where moderators occasionally re-expose strong posts that didn’t surface the first time. If your submission genuinely deserved better, a polite note to the moderators can earn a second airing. What you must never do is delete and resubmit the same link repeatedly — that pattern gets you flagged.
Where the links actually come from (since it isn’t the post)
Here’s the part that makes Hacker News worth the risk. A front-page hit doesn’t hand you one nofollow link — it triggers a cascade of followed links you never asked for, because of how the HN ecosystem works.
The aggregator wave
Hundreds of sites scrape, mirror and republish the Hacker News front page — aggregators, newsletters, “best of HN” digests, niche reader apps. When you hit the front page, your URL propagates across all of them, and many of those links are followed. Founder write-ups of front-page hits routinely report picking up over a hundred new referring domains in the days afterwards, with a visible jump in Domain Rating and a corresponding lift in search impressions. That’s the real link payoff, and it lands whether you wanted it or not.
To actually see it, set a backlink-monitoring baseline before you post and check it daily for the week after. You’ll typically watch the referring-domain count step up over the first 48 to 72 hours as crawlers find the aggregator copies, then plateau. Most of those links are low-individual-value — a scraper page isn’t a tier-one editorial placement — but in aggregate, arriving naturally and pointing at a genuinely popular page, they read to search engines exactly as an organic burst of interest should. That’s the quiet beauty of the channel: you can’t fake the popularity that produces the links, which is precisely why the links are trusted.
There’s a second, quieter benefit. That sudden flood of links from frequently-crawled pages is a powerful crawl signal. If you’ve just published the page you submitted, those links can accelerate how fast Google discovers and indexes it — a mechanism we cover in our guide to technical SEO link building. A front-page HN hit is one of the fastest indexation nudges available to a small site.
A word of caution on velocity
A hundred-plus referring domains arriving in 48 hours is a sharp spike, and sharp spikes are worth understanding rather than fearing. A genuine, newsworthy event like a viral post is exactly the kind of organic burst search engines expect; it doesn’t look like an engineered campaign because it isn’t one. Still, if HN hits are your only link source and nothing else moves between them, the on-off pattern can look unnatural over time. Treat HN as one input feeding a steadier programme — the velocity principles in our guide to how fast you should build backlinks apply directly. And if you want to weigh what each of those aggregator links is really worth, our model for the ranking impact of a single backlink gives you the framework.
Indie Hacker communities: the followed-link cousins
This is where the “indie hacker communities” half of the title earns its place. Unlike Hacker News, several adjacent communities pass followed links directly. Indie Hackers, with its 300,000-plus monthly users, treats well-ranked posts with site-link formatting in Google and passes link equity through to your domain. Developer-writing platforms and smaller technical forums often do the same. The play is to treat HN as the high-energy spike and these communities as the steadier, lower-risk presence channels — a genuine post on Indie Hackers about what you learned building the thing can keep earning long after your HN thread has scrolled away.
The common thread across all of these communities is that they reward the native idiom and punish imported marketing prose. The most common mistake brands make is shipping the same press-release copy they ship everywhere else, watching it underperform, and concluding the platform “doesn’t work.” The platform works fine; the content was wrong for the surface. On Indie Hackers the native form is the honest build-log or revenue-transparency post. On developer platforms it’s the technical retrospective — “how we did X, what broke, what we’d do differently.” Match the idiom and the same followed link that would have been ignored as an ad gets read, upvoted and, often, quoted elsewhere. The link is the same; the framing decides whether it travels.
Earning without burning: the reputation rules
This is the section that protects the asset. The HN community has a strong, mostly unwritten culture, and the gap between “welcome contributor” and “banned domain” is narrower than newcomers think. The rules cut both ways — readers are expected to be civil and curious rather than hostile — but as the person posting your own work, the burden of good behaviour is on you. The platform’s own guidelines are short and worth reading in full; here’s what matters most for link building.
The lines you do not cross
Never ask anyone — friends, followers, users, teammates — to upvote or comment. Ring detection is strong and the penalty is a shadowbanned URL or a permanently banned domain.
Never use paid upvote services. Same outcome, faster.
No hype in titles. No exclamation marks, no “revolutionary,” no marketing adjectives. A plain factual title outperforms and survives; a salesy one triggers reflexive downvotes and flags.
Don’t turn your first comment into a sales pitch. The community doesn’t need to be told your market is large. Give them a reason to care, honestly.
Don’t delete and resubmit the same link to chase a better slot. That gets you flagged.
The title and the first comment carry the whole thing
Two artefacts decide most of your outcome, and founders chronically under-prepare both. The title should be plain and specific — “Show HN: [Product] — [what it does]”, or for a write-up, the article’s honest headline. Concrete digits beat vague claims every time: “Show HN: I cut my AWS bill 82% with a 200-line script” lands far better than “How I saved money on AWS.”
The first comment is your one chance to add the human context the neutral title leaves out: what you built, why you built it, what stage it’s at, and — crucially — what it can’t do yet. Honesty about limitations consistently earns more goodwill than polish. Then ask for feedback, not support. People upvote things they find interesting; they help when you ask for something they can give.
A reliable structure for that first comment runs in four short beats. One: the honest origin — “I built this because I kept hitting [specific problem] and nothing existing solved it the way I wanted.” Two: what it does, plainly, in a sentence. Three: the candid caveat — “It doesn’t yet do X, and the Y is rough.” Four: the open question — “I’d love feedback on [specific thing].” That sequence reads as a builder talking to other builders, which is exactly the register HN rewards. Compare it to the instinct most marketers fight — leading with the value proposition and the addressable market — and you can see why so many launches die on contact. The community can smell a pitch in the first line, and once it does, the downvotes are reflexive.
Comments are the underrated channel
Here’s the move most link-building guides miss entirely: on Hacker News, commenting is often a better channel than submitting. A submission asks the whole site to care about you. A useful comment lets you help inside a conversation that’s already happening. Founders who quietly monitor threads about their problem space, their competitors and adjacent technologies — and add something genuinely useful before the discussion moves on — build a steady trickle of qualified traffic and a reputation that makes their eventual Show HN land softer. It’s lower-risk, it compounds, and it never trips the spam filter because you’re not promoting anything. You’re being helpful in public.
The practical system is simple. Set up alerts for your product category, competitor names, and the problem phrases your buyers use, so you catch relevant threads early — the first hour of a thread is where comments get read. Then write the comment you’d write if you had no product to sell: the actual answer, the real trade-off, the thing you learned the hard way. Mention your tool only when it’s genuinely the most useful thing you can offer, and even then, lightly. Done consistently, this builds the kind of standing that means when you do post your own work, people already recognise you as a contributor rather than a marketer. That recognition is worth more than any single front-page hit.
Why HN standing feeds the answer engines
The 2026 reason to care about Hacker News goes beyond links. Community platforms punch far above their weight as sources for AI answer engines, and a substantive HN discussion about your product is exactly the kind of independent, corroborating signal those engines reach for. When several models are asked “what’s the best tool for X,” they lean toward brands the wider web already vouches for — and genuine community standing is part of that vouching.
This is really a question of entity authority, not raw links. As we argue in our piece on how to measure entity authority when the old metrics can’t, the signals that predict whether a brand gets recommended are referring-domain breadth and community presence — broad corroboration — far more than on-page optimisation. A respected HN thread, an active Indie Hackers presence and the aggregator links a front-page hit produces all feed that corroboration layer at once. The same discussion that wins you traffic on the day quietly strengthens the case for an LLM to name you months later.
The catalyst chain, HN edition
Genuinely interesting post → front-page hit driven by early velocity → traffic spike + a wave of followed aggregator links + a DR bump → secondary coverage and a real community discussion → stronger entity authority and corroboration → you get named when buyers ask an answer engine what to use. The submission link is nofollow; almost everything downstream of it is not.
Where Hacker News fits among the channels
Like Product Hunt, Hacker News is a moment channel, not a presence channel — but it’s a sharper, riskier, more credible moment. A front-page hit is louder in link terms than a Product Hunt launch, because the aggregator wave delivers followed links rather than nofollow ones, and the audience carries more technical weight. What HN doesn’t give you is anything evergreen: the thread scrolls away within a day and won’t keep sending traffic the way a directory listing or a ranking blog post will.
So the right architecture pairs HN’s spike with steadier presence channels. Use Indie Hackers and developer-writing platforms for the followed-link, slow-compounding posts. Keep a genuine commenting habit on HN itself for the low-risk trickle. And route the credibility a front-page hit creates into the channels that hold value — the listicle placements, the review profiles, the original-data pieces that keep earning. The launch-style moment lights the fuse; the presence channels are what actually burn.
And the planning rule is the same one that governs every high-variance channel: never let a single HN attempt be the whole plan. Most posts die in /new, and that has to be survivable. Build a programme where HN is one input among several, so that a flop costs you an afternoon and a hit is a windfall — rather than betting a quarter’s growth on whether the community happens to like your post on a given Tuesday.
The two-week Show HN plan
Most HN failures are preparation failures — the title and first comment written in a rush minutes before posting. Here’s the executable version that front-loads the work.
Week −2: earn the right to post
- If your account is thin, spend the fortnight commenting usefully on relevant threads. Aim to be a recognisable, helpful contributor before you ever post your own link.
- Make the thing genuinely trial-able: a one-click demo, a cached landing page that survives a surge, no sign-up wall between a curious visitor and the “aha” moment.
- Publish and polish the page you’ll submit (if it’s a write-up) so the aggregator links and crawl signal land on a finished, citable asset — not a draft.
Week −1: prepare the two artefacts
- Draft the title: plain, factual, specific. Test three variants on a technical friend who’ll tell you if it sounds salesy.
- Write the first comment: what it is, why you built it, current stage, honest limitations, and a clear request for feedback. Rewrite it until there’s not a word of marketing in it.
- Pick the slot (Tue–Thu, ~8–10am ET, or Sunday evening) and check that no giant story — a major platform launch, a big event — is about to swamp the front page.
Launch day: be present, not promotional
- Post the original source with the neutral title, then immediately add your prepared first comment.
- Reply to every comment for the first two to three hours — curious, calm, honest. Treat criticism as useful and never get defensive. Silence in this window reads as abandonment and the algorithm punishes it.
- Do not message anyone asking for an upvote. Share the link where your real audience already is and let the votes come honestly, or not at all.
Weeks +1 to +2: harvest the echo
- Watch your backlink profile for the aggregator wave and note which followed links landed. Reclaim any unlinked mentions the discussion produced.
- Turn the best comment-thread feedback into testimonials, a follow-up post, or product fixes — then write the honest “what we learned” post for Indie Hackers.
- Run your category prompts across ChatGPT, Perplexity and Gemini and log whether the discussion moved your visibility. Those cited sources become your next targets.
What to measure (and what to ignore)
Upvotes and points are the vanity numbers. Track the things that actually compound:
- Referring domains gained in the week after a hit — the aggregator wave is your true link yield, and it’s followed.
- Domain Rating and indexation — a front-page hit often produces a measurable DR bump and faster indexation of the submitted page.
- Branded search and direct traffic in the following weeks — the cleanest proxy for the mind-share a strong discussion creates.
- Qualified signups and activation — HN traffic is technical and high-intent, so measure who reached first value, not just who landed.
For the tooling — mention monitoring to find threads worth commenting in, and AI-visibility trackers to sample citations — see our link building tools guide, and for the wider benchmarks our link building statistics for 2026. Read trends across multiple hits, not the result of any single post; HN is high-variance by nature.
One last measurement warning: don’t judge the channel on its first attempt. A single post that dies in /new tells you almost nothing — it might have been the wrong Tuesday, a crowded front page, or a title that didn’t quite land. The signal you’re after is the average across several genuine attempts over a quarter, alongside the slow build of the commenting habit running underneath them. Founders who quit after one flop are reading noise as a verdict. The ones who treat HN as a repeatable practice, posted into honestly and prepared properly, are the ones who eventually catch the hit that pays for all the misses.
Two anonymised composites: the hit and the ban
Both of the following are anonymised composites, drawn from patterns across publicly documented 2025–26 launches rather than any single company.
Founder A, a solo developer, posted a Show HN for a small tool with a one-click demo and an honest first comment explaining why they’d built it. It graduated out of /new on early velocity, sat on the front page for most of a day, and brought a concentrated wave of technical visitors. The lasting effect wasn’t the traffic — it was the cascade of followed links from aggregator sites, a Domain Rating jump over the following days, and a noticeable lift in search impressions. Modest spike, durable link echo, and a tool that started appearing in answer-engine recommendations for its niche over the next quarter.
Founder B had a better-funded product and decided to “guarantee” the launch. They asked their team and a Slack community to create accounts and upvote at a set time, and wrote a polished, benefit-heavy title. The vote pattern — a cluster of fresh accounts with no connection to the wider community — tripped ring detection within the hour. The post was buried, the URL was penalised, and the domain picked up a ban that no amount of emailing reversed. A single shortcut cost them the channel permanently.
The lesson isn’t subtle. The thing that earns the links on Hacker News and the thing that protects your domain are the same thing: genuine, honest participation. Engineer the velocity by being interesting, never by manufacturing votes.
Your Monday-morning action plan
Five steps, in order:
- Score your situation on the Fit-and-Risk Scorecard. Be brutally honest about account standing and thick skin — those two rows fail most launches.
- If your account is thin, start commenting usefully today on threads in your space. Build standing before you ever submit your own link.
- Make your thing genuinely trial-able and your landing page surge-proof. No Show HN without something to try.
- Draft the title and first comment now, then strip every trace of marketing language out of both. Read them aloud; if they sound like an ad, rewrite.
- Run your top five category prompts across ChatGPT, Perplexity and Gemini to set a pre-launch citation baseline, then pick a Tuesday–Thursday morning slot.
Frequently asked questions
Are Hacker News links dofollow or nofollow?
The link on your submission is nofollow, so it doesn’t pass authority directly. The real link value comes indirectly, from the wave of followed backlinks generated by the hundreds of sites that scrape and republish the HN front page, plus the secondary coverage a front-page hit attracts. Adjacent communities like Indie Hackers do pass followed links directly.
Does Hacker News still help SEO in 2026?
Yes, but indirectly. A front-page hit produces a burst of followed aggregator links, a measurable Domain Rating bump, faster indexation of the submitted page, and brand mentions that feed AI citations. The submission link itself is nofollow, so the SEO value is an echo of the attention rather than a direct injection of link equity.
Can I ask friends to upvote my Hacker News post?
No — this is the most dangerous mistake on the platform. Asking anyone to upvote, or coordinating votes, is against the rules, and HN’s ring detection is strong enough to shadowban your URL or ban your domain permanently. Share the link where your real audience already is and let votes come honestly.
What’s the best time to post on Hacker News?
Tuesday to Thursday, roughly 8–10am US Eastern, when engineers check the news before stand-up, is the consensus sweet spot. Sunday evening is a strong second choice for lower competition. Avoid Monday mornings and Friday afternoons. Timing helps at the margin, but it won’t rescue weak content — early vote velocity in the first 60–90 minutes matters far more.
What’s the difference between Show HN and a normal submission?
Show HN is specifically for something people can try right now — software they can run, a site they can use, hardware you can demo. Blog posts, newsletters, lists and sign-up pages are not Show HNs. For an article, essay or research piece, use a normal link submission with a neutral, factual title.
How much traffic does a front-page hit send?
A solid front-page placement typically sends a concentrated burst — founder reports commonly land in the region of 10,000–20,000 visitors over roughly a day — with about half the spike passing in the first eight hours and a trickle continuing for a few days before stopping. Like Product Hunt, the traffic is short-lived; the links and citations are the durable payoff.
What happens if my post flops?
Most good submissions die in /new, and that’s normal. Don’t delete and resubmit — that gets you flagged. Hacker News runs a second-chance pool where moderators sometimes re-expose strong posts that didn’t surface, so a polite note can earn a second airing. Otherwise, a different, well-prepared submission on another day is fine; repeatedly reposting the same link is not.
Does my account need history before I post my own link?
It helps a great deal. A brand-new account whose only activity is posting its own links reads as a marketer and gets less benefit of the doubt from both the community and the spam filters. Spending time beforehand leaving genuinely useful technical comments builds the standing that makes your eventual submission land softer. If your own account is thin and the work is genuinely strong, it’s better to build that history than to lean on shortcuts.
Be the most useful person in the thread, every time. On Hacker News that’s not just good manners — it’s the whole link-building strategy.
