Over-answering a simple query can hurt more than help, because it buries the quick answer the searcher wanted under unwanted depth, raising friction and worsening the page’s fit with the intent. When someone wants a short, direct answer and lands on a page that makes them scroll through background, caveats, and tangents to find it, the page has served the answer worse, not better, even though it contains more. For a simple query, brevity that fully answers beats exhaustive depth, and the over-answer mismatches the intent.
The mechanism is about friction against intent. A simple query signals that the searcher wants something specific and fast, and the best result is the one that delivers it with the least effort. Pile depth on top of that and every extra paragraph is an obstacle between the searcher and what they came for. They have to skim past material they did not want, and many give up or leave for a cleaner result. The page’s relevance to the actual intent drops, because the intent was “answer me quickly” and the page answered slowly.
This is why the assumption that more thorough is always better breaks down. Thoroughness is a virtue when the query calls for it, a complex question, a decision, a how-to with real steps. For a simple lookup, thoroughness is a mismatch dressed as quality. The search engine reads engagement with the result, and a page that makes simple-intent searchers work for a simple answer reads as a worse fit than a concise page that just answers. Depth has to match the question, and depth aimed at a simple question is over-service that costs.
For your next page on a simple query, lead with the direct answer and keep it that way. Give the searcher exactly what they asked in the first line, add only the minimum context that genuinely helps, and resist the urge to demonstrate thoroughness the query never requested. Match the answer’s depth to the query’s simplicity, and let the brief, complete answer be the whole of the page rather than the buried center of a long one.