Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
I don't see what to do with heavily downvoted answers, really. They're wrong, and clearly shown as such. What needs cleanup isn't the downvoted content really, it's the content that should be downvoted but isn't.
Why show only closed questions? Downvoted questions might need closing, whereas I don't know why downvoted closed questions would be different from non-downvoted closed questions.
See the question: if there's a deleted result, it's counted in the 100. I guess deleted results are eliminated late in the chain. I thought …/page=2 just after …/page=1 was counted differently, but I can't find a reference to that now, I might have imagined it or confused with some other site's API.
Ok, this technique works to avoid skipping an item in the middle. It assumes there aren't 100 questions with the same date (this is unlikely to happen naturally, but what about a mass import?). Your termination condition is wrong, there can be less than 100 results at any time. This technique is rather costly; as I understand it, querying page=2 after page=1 is cheaper in the backend (because the data is already sitting in some cache, I guess), and from the user's point of view it's cheaper because it doesn't count as a separate request against the API usage quota.
