From Ask Yahoo! to Answers
Yahoo Answers opened to its first public users on December 8, 2005. Yahoo built it to replace Ask Yahoo!, its older question-and-answer feature, and borrowed the model from Naver’s Knowledge iN in South Korea, where the community that answered questions was the product. On a mid-2000s web where Quora and Stack Exchange did not yet exist, that was the entire appeal. You typed a question, strangers replied within the hour, and nobody had to be an expert to get a response. Homework help, wiring advice, arguments about relationships, anxious health questions people would rather ask anonymously — it all got a thread.
Scale followed quickly. By late 2006 Yahoo was using comScore numbers to call Answers the leading Q&A site on the web. In 2009 the company claimed 200 million registered users worldwide. The site passed its billionth answer around April 2010, when one famous user asked a perfectly mundane thing: what laptop part would speed up a slow PC (the answer: upgrade the RAM). For the better part of a decade, “look it up” usually meant reading something a stranger had asked on one’s behalf.
Why people answered
Nothing about the mechanics pushed anyone toward accuracy. Asking a question cost five points; answering earned two; winning the asker’s “best answer” nod paid ten. The points bought nothing — no prizes, no money — but they fed a visible seven-level ranking, and the most prolific answerers in a category carried a Top Contributor badge under their name. The system ran on two fuels at once: real human willingness to help and a status game simple enough for anyone to play. The same design also rewarded participation over knowledge, because a guess and a careful answer earned identical points.
A useful, unreliable archive
The useful half came from lived experience. A person who had actually fixed a stubborn drain, filed a complaint, or survived an awkward conversation could answer with ground truth no encyclopedia had. Because the archive was searchable, a thread from 2009 could still settle today’s question about a discontinued phone. None of it was checked, though. Once an asker picked a best answer it could not be corrected, the point system encouraged guessing, and researchers who studied the site described its knowledge as broad but superficial. That same laxness produced the Yahoo Answers people quoted for laughs: questions too misspelled to parse, answers that were wrong with total confidence, and the famous 2008 “how is babby formed” thread that became a decade of internet joke material. The record was authentically human, which is exactly why it was unreliable.
The shutdown
On April 5, 2021, Yahoo announced that Answers would close. New questions and answers stopped on April 20; the site ceased working on May 4; and on June 30 Yahoo deleted the stored content. The stated reason was plain: the service had become less popular over the years. Individual users could download their own posts until the deadline, but nobody could export the accumulated public archive, and Yahoo offered no broad data dump.
The archive and after
The deletion was not total. Archive Team, the volunteer preservation collective that crawls closing services, saved 4.75 terabytes of question and answer pages before the doors shut, and its capture remains browseable on the Internet Archive. Gizmodo separately archived a small clutch of questions pulled from the site’s index files. Combined with users who saved their own posts and years of screenshot repositories on Reddit and Tumblr, the corpus did not simply evaporate. The Japanese twin, Yahoo! Chiebukuro, kept running, and readers who used to wander into a stranger’s question now find their answers on Quora, Reddit, or a search engine’s result page.
What ended with the closure was the mass public question-and-answer community and its single, searchable archive — the one place where the ordinary questions of millions of people were stored together, answerable, reusable, and endlessly quotable. That record now survives only in partial copies rescued by outsiders, which is a quiet reminder of how fragile a mass user-generated archive is when its corporate owner stops caring.