How do you track brand mentions on Hacker News?

Does Hacker News only discuss developer tools?

No. Its audience skews technical, but threads regularly cover consumer apps, fintech, hardware, media and any product a founder or engineer happens to use or build.

Show HN welcomes anything a maker built, and plenty of posts there are consumer apps, hardware or services with no developer audience at all. Ask HN threads ask for recommendations on everything from note-taking apps to banking for freelancers to standing desks. And ordinary story threads, about a funding round, a security incident, a product launch, pull in comments that name specific brands and compare them to rivals.

If your buyers or users include people who read Hacker News, which is a wider group than 'developers' alone, the threads that mention your category are worth finding, whether or not your product is itself a developer tool.

How do you actually search Hacker News for mentions?

Use hn.algolia.com, not the search box on the HN site itself, and search brand, product and competitor names separately.

HN's native search is limited. Hn.algolia.com (Algolia's official HN search) covers the full archive, lets you filter by date, sort by popularity or recency, and search both story titles and comment text. That last part matters: a brand is often named inside a comment on an unrelated story, never in a title you would have found otherwise.

Search four things on a regular basis: your exact brand name, your product name if different, common misspellings or abbreviations, and two to five competitors you actually compete with. A broad category phrase (one, not ten) catches 'anyone know a good alternative to X' threads you would otherwise miss entirely.

• Search hn.algolia.com, sorted by date, for each term on your list.
• Check comment text as well as titles; most mentions of a specific brand live inside comments, not headlines.
• Keep the keyword list short enough that every result is worth a human look; a list that is too broad trains you to stop checking it.
• Note the language people use when they compare you to a competitor; it belongs on your comparison and FAQ pages.

How often should you check, and what do you do with a hit?

A weekly review catches almost everything that matters; reply the same day only when the thread is live and growing, otherwise a thoughtful reply after a day or two is fine.

Hacker News comment sections move fast for the first few hours of a popular thread, then slow down. If a thread is actively live (fresh comments every few minutes), a same-day reply from someone who can speak plainly about the product is worth it. For most mentions, found days after they were posted, a late but honest reply still reads fine; HN readers do not expect instant responses outside an active launch thread.

Whatever you find, route it somewhere: a genuine complaint goes to the product team, a comparison to a competitor goes on your compare page, and a question worth answering publicly gets a reply from someone who will say who they are.

How does MarketHQ help track Hacker News mentions?

MarketHQ checks Hacker News for your brand and competitors on every plan, for any kind of company, and keeps it in one feed next to the other communities buyers actually use.

Every MarketHQ plan, from Lite at $29 a month, checks Hacker News, GitHub, Stack Overflow, Dev.to and Lobsters, and blogs and RSS feeds you add, four times a day, and keeps the last 30 days in one feed. There is no requirement that your product be a developer tool; a consumer brand, a fintech company or a media outlet tracked here gets the same coverage.

The same plans add Reddit, X, LinkedIn and YouTube to the same feed, label each mention positive, negative or neutral, and draft a reply for you to edit and post yourself. Weekly AI-visibility tracking across six AI engines runs alongside it, so a Hacker News objection and an AI-answer gap show up in the same place instead of two separate tools.

What does a useful week of Hacker News monitoring look like?

Illustrative example: a budgeting app for freelancers finds three competitor threads, one brand mention, and a recurring objection worth adding to its FAQ.

Illustrative example: a budgeting app built for freelancers searches hn.algolia.com weekly for its brand name, two competitors, and the phrase 'freelancer taxes'. One week turns up a thread where a competitor is praised for automatic tax set-asides, a comment mentioning the app's own name by a happy user, and an older thread raising a bank-sync reliability complaint about the whole category.

The team replies briefly to the mention thanking the commenter, adds a short note to its product roadmap about tax set-asides, and writes a line on its FAQ page addressing the bank-sync concern directly, since it is clearly a recurring worry for this audience wherever they raise it.

When is Hacker News monitoring not worth the effort?

When your actual buyers do not read it, or when you will not act on what you find.

HN's audience is real but specific: technical, skeptical of marketing language, and concentrated in certain categories. If your buyers are, say, retail store owners or school administrators, your time is better spent elsewhere. And a mention you never reply to or act on is just a notification you learn to ignore; keep the keyword list short enough that every hit gets a real response.