Hacker News and Developer Tools: The Source That Shapes Technical Answers

If you sell to developers, this is where a meaningful part of your AI reputation gets written.

Why engines weight it so heavily

Hacker News has traits that answer engines seem to favor. The site is text-only. Comments are often long and technical, written by people who identify themselves as users or maintainers. Disagreements get worked out in public, which gives a model both sides of a tradeoff on one page. And the domain has two decades of history, so almost every tool with any traction has a thread.

In our testing, Hacker News shows up most for "what do people actually think of X" questions, for comparisons between tools, and for questions where the honest answer involves caveats. An engine summarizing a thread will often phrase its answer as "developers praise X for its speed but note that Y is a common pain point," which is a direct paraphrase of how a thread reads.

What gets pulled from a thread

The top-voted comments carry most of the weight. A comment that explains a specific experience, including what broke and how it was fixed, is the kind of text that becomes part of an answer. "We tried this and went back to Postgres" will be summarized, and it may follow your product around for years.

Show HN posts matter because they often include a founder explanation of what the tool does and why it exists. That text tends to be treated as a primary description, similar to how an engine reads a README or an About page.

Threads do not need to be recent. A 2021 thread with three hundred comments can outweigh a 2026 thread with twelve.

What you can and cannot do

You cannot control what gets said. Manufactured positive comments are spotted quickly, and the resulting thread is worse than silence.

What you can do:

• Launch with a Show HN that explains the tool plainly. What it does, who it is for, what it does not do, and what the pricing is. This is the text an engine will quote. Marketing language gets mocked in the comments and ignored by the model.
• Show up in your own threads and answer honestly. When a maintainer explains a limitation and what is planned, the thread reads as credible, and the engine summarizes it that way.
• Fix what people complain about. The threads that hurt most are the ones where a known problem is raised, acknowledged, and never fixed. The next thread will reference the old one.
• Post follow-ups when something significant changes. A "we rewrote the storage layer" post that addresses an old criticism gives the engine a newer source that contradicts the older complaint.

Checking what engines already think

Run the questions a developer would ask about your category and your tool by name. Note which threads are cited and read them. Usually one old thread is doing most of the damage or most of the work. Knowing which one tells you where to focus.

Then check your own documentation and README. If the Hacker News thread describes you more clearly than your site does, the fix is on your side. Your site should be the clearest source, with pages written to be quoted, consistent schema markup, and an llms.txt that states the facts.

Where this fits

At AEO GEO Labs, developer-facing clients get a source map that almost always has Hacker News near the top. We do not try to change what the threads say. We try to make sure the company's own pages are clear enough that an engine does not have to rely on a four-year-old comment to describe the product, and we track whether that shift actually happens in the answers over time.

A practical close

Search Hacker News for your product name and for your category. Read the top thread with fresh eyes. Write down the three criticisms that appear most often and check whether your site addresses each one directly. If not, that is the next page to write. AEO GEO Labs offers a free answer-ready checker that will tell you whether those pages are written in a way an engine can actually use.