How to Monitor Hacker News for Brand Mentions and Trending Topics
In March of last year, a developer tools startup I was working with had a normal Tuesday morning. By Tuesday afternoon, their site was down. Not because of a bug. Because someone had submitted their Show HN post from six months earlier to the front page of Hacker News — again — and this time it caught fire. Four hundred upvotes in two hours. Their free tier signup form was getting hammered. Their Postgres instance was maxing out connections. And the founding team had no idea any of it was happening until a customer emailed them to say the dashboard was broken.
They found out about their best marketing day of the year from a support ticket.
By the time the CTO opened the Hacker News thread, it had 200 comments. Most were positive. A few were technical questions about their architecture that had gone unanswered for hours. One commenter had pointed out a security concern with their OAuth flow — a valid one — and the thread had spun into a debate about whether the company could be trusted with production data. That sub-thread had 40 upvotes and zero response from anyone at the company.
The traffic spike was a gift. The unanswered security thread was a wound that stayed indexed on Google for months.
The Hacker News Effect Is Real — and Unpredictable
If you build developer tools, infrastructure software, or anything adjacent to the tech industry, Hacker News is probably the single highest-leverage community for your brand. Not because of raw audience size — Reddit and Twitter are both bigger. Because of who reads it and what they do with what they read.
The people on HN are founders, senior engineers, VCs, tech journalists, and hiring managers. A front page post on Hacker News has started companies, killed product launches, and driven more qualified signups in an afternoon than six months of paid ads. The "HN hug of death" is a running joke, but the traffic is only half the story. The comments section is where reputations get built or torched.
And here is the thing that makes HN particularly dangerous to ignore: you cannot predict when your product will surface there. Someone might submit your blog post. A user might mention you in an Ask HN thread. A competitor might launch on Show HN, and the comments section might turn into a comparison thread where your product gets dissected by people who actually use it. Any of these can happen on any given day, and the window to respond is measured in hours, not days.
Why Proactive Monitoring Matters
Most companies treat Hacker News the way they treat earthquakes — something that happens to you, not something you prepare for. That is a mistake. There are at least three concrete reasons to monitor HN systematically.
Competitor launches. When a competitor posts a Show HN or gets submitted to the front page, the comments section becomes the most honest competitive analysis you will ever read. Real users comparing features, sharing migration stories, pointing out weaknesses. This is intelligence that consultants charge five figures to produce, and it is sitting in a public comment thread. But only if you see it while the discussion is still active.
Brand reputation. The security thread I mentioned earlier? That company eventually responded, but by then the narrative had already solidified. On Hacker News, the first few hours of a discussion set the tone. If someone raises a concern about your product and you are there to address it thoughtfully — not defensively, thoughtfully — you can shape the conversation. If you show up twelve hours later, you are replying to a thread that everyone has already read and formed opinions about.
Hiring signals and industry trends. The monthly "Who is hiring?" threads are a goldmine for competitive intelligence. You can see which companies are scaling, what technologies they are investing in, and what roles they are filling. The "Ask HN" threads about tools and workflows tell you what pain points engineers are experiencing right now, in their own words.
How to Search HN Programmatically
Hacker News runs on a public API powered by Algolia. This is actually one of the better-documented search APIs in the wild, and it is completely free — no API key, no rate limit hassles, no enterprise sales call required.
The Algolia-powered Hacker News search API lets you query the full archive of stories, comments, Ask HN posts, Show HN posts, and front page items. The basics are straightforward: you send a search query and get back matching results with titles, authors, scores, comment counts, timestamps, and URLs.
What makes it useful for monitoring is the filtering. You can filter by content type — story, comment, ask_hn, show_hn, front_page — so you are not drowning in noise. You can sort by date to see the most recent mentions first. And you can combine filters, so a query like "your-brand-name" filtered to comment and sorted by date gives you every time someone mentioned your product in a comment thread, newest first.
A typical monitoring query looks something like this: search for your brand name, filter to stories and comments from the last 24 hours, sort by date, and cap the results at 20. Run that once a day and you have a basic surveillance system. Run it for your top three competitors as well, and you have a competitive monitoring system.
The same approach works for tracking industry keywords. If you sell observability tools, searching for "observability" or "monitoring" filtered to stories gives you a daily feed of what the HN community is talking about in your space. If a new entrant pops up in a Show HN that gets 300 points, you want to know about it the same day, not the following week when your sales team gets asked about it on a call.
Building an Automated Monitor
The real value is not in running manual searches. It is in building a pipeline that searches, filters, and alerts without human intervention.
The architecture is simple. A scheduled job runs your monitoring queries — brand name, competitor names, industry keywords — against the Hacker News search API once or twice a day. The results get filtered for relevance: anything with more than a handful of points or comments gets flagged as worth reading. High-signal results get pushed to a Slack channel with a summary: title, score, comment count, link, and a one-line description of why it was flagged.
The filtering step matters more than people realize. A raw search for a common keyword on HN will return dozens of results a day, most of which are irrelevant. You need a layer that evaluates whether a result actually warrants attention. Is this a front page story with 100+ points? Flag it. Is it a comment in a comparison thread that mentions your product? Flag it. Is it an Ask HN where someone is asking for tool recommendations in your category? Definitely flag it.
The alert should include enough context that whoever reads the Slack message can decide in ten seconds whether to click through. "Your brand was mentioned in a comment thread about CI/CD tools — 84 points, 47 comments, posted 3 hours ago" is actionable. A bare link is not.
Going Deeper: Sentiment and Discussion Velocity
Once you have the basic search-and-alert pipeline running, there are two dimensions worth adding.
Sentiment analysis on comments. Not every mention is created equal. "We switched to [your product] and it cut our deploy times in half" is categorically different from "we evaluated [your product] but the pricing was absurd for what you get." Both are mentions. Only one is a problem. Running comment text through a sentiment classifier lets you prioritize the negative mentions — the ones that need a response — over the positive ones that are doing your marketing for you.
Discussion velocity. A post with 5 points and 2 comments is background noise. A post that went from 5 points to 50 points in the last hour is a developing situation. Tracking the rate of change — not just the current score — tells you which discussions are heating up and might hit the front page. If you can catch a thread while it is accelerating and respond before it peaks, you are ahead of the curve instead of chasing it.
Both of these are hard to do with a raw API call but straightforward when you have an agent that pulls the data and applies judgment. Which brings me to the part where I tell you how we think about this at Cotera.
Putting It Together With an AI Agent
We built a Hacker News tool in Cotera specifically because this workflow kept coming up. Searching HN for brand mentions, pulling article details and comments, looking up user profiles — it is all available as a tool that an AI agent can call on its own.
The workflow I have seen work best: an agent that runs daily, searches for your brand, your competitors, and your top three industry keywords, filters the results for anything above a relevance threshold, then sends a Slack digest with the highlights. The whole thing takes about two minutes to run and costs nothing. No enterprise contract, no per-seat pricing, no dashboard you will forget to log into.
The Hacker News search API is free. The data is public. The only resource you are spending is the time to set it up once and then the thirty seconds a day it takes to scan the Slack digest. For a community that can drive more qualified traffic in an afternoon than most paid campaigns deliver in a month, that is an absurdly good trade.
Try These Agents
- Hacker News Search Tool — Search stories and comments, retrieve articles and user profiles from Hacker News
- Brand Monitoring Agent — Track brand mentions across Twitter, Reddit, news, and reviews
- News Monitoring Agent — Catch competitive moves and industry shifts from news sources
- Sentiment Analysis — Track sentiment trends across reviews, social media, and forums