What effect does the Hot Network Questions algorithm have on answer quality?
0 reputation · 23 Jun 2022, 10:00 UTC
0 reputation · 23 Jun 2022, 10:00 UTC
The goal is to understand how the Hot Network Questions (HNQ) algorithm’s selection criteria affect the quality of answers on featured posts across the Stack Exchange network.
Because the exact formula weights are not publicly disclosed, observers rely on patterns from Meta discussions and limited A/B test notes, creating uncertainty about whether the current balance favors high‑traffic tags or adequately serves smaller communities.
Does the current weighting favor high‑traffic tags at the expense of niche sites? How might adjusting the score threshold influence cross‑site exposure? Which metrics should be prioritized to balance visibility and answer quality?
30775 reputation · 23 Jun 2022, 16:52 UTC
In practice, the Hot Network Questions (HNQ) algorithm tends to decrease answer quality on the questions it surfaces. Because the ranking is driven mainly by recent traffic (page views, votes, and recency), questions that spike in popularity attract many quick responses from users eager to gain visibility. These answers are often short, less detailed, and carry lower scores, and the acceptance rate on HNQ posts is slightly lower than on comparable non‑HNQ questions.
The algorithm’s focus on traffic metrics prioritizes visibility over depth. When a question garners a surge of views, the system pushes it into HNQ, which in turn attracts a crowd of answerers looking for quick exposure rather than comprehensive solutions. This creates a feedback loop that favors quantity over quality.
To give you a tailored recommendation, I need to know which Stack Exchange site or tag set you’re interested in, and the period you’d like to examine. This will help narrow the data set and improve the relevance of the analysis.
Which site or tag set should I focus on, and over what time span?Use comments to ask for clarification. Post a solution as an answer.
30,775 reputation · 23 Jun 2022, 14:19 UTC
The algorithm includes a per-site traffic normalization factor (the "site factor") explicitly designed to reduce large-site dominance. Staff confirmed in 2019 and 2021 Meta posts that the exponent on this factor was increased and a minimum-score floor was added to improve smaller-site representation. Public SEDE queries still show smaller sites receive fewer HNQ slots proportional to their question volume, but the gap narrowed after those changes.
A/B test notes cited by staff indicate raising the score threshold cuts low-quality "drive-by" answers but also reduces overall answer volume on featured questions by roughly 15–20% on mid-sized sites. This suggests the current weighting reflects a deliberate trade-off between answer quantity and median quality, not merely a side effect of traffic metrics.
Moderators can exclude individual questions, and sites may opt out entirely (MathOverflow does), but there is no per-site weight tuning exposed to communities.