2 ms·

> For some queries, not necessarily all, I'd also like to be able to block all sites containing AdSense. What kind of queries would you want to do that for? I

• benologist 16y ago
  Because when was the last time you saw a spam site that didn't use AdSense?
• gojomo 16y ago
  I don't currently have exact examples in mind. (For the last few months, NoScript has blocked me from seeing lots of the most annoying ads, and I've been trying to avoid clicking on some of the worst domains, like ehow.com.) I just recall that on some queries – especially related to diet/health, or product/household how-tos – after clicking several of the top results, I'd seem lots of AdSense, and very little useful content. Other ads can be just as bad; I mentioned AdSense specifically because it's so widely used, and has at times seemed the first choice of low-quality filler sites (though that may be changing). Also, implementing an AdSense filter would be the acid test of Google's willingness to offer search functionality with no concern for revenue effects. I don't need such a setting to be persistent; I certainly would not suggest it should be the default. So that the functionality is not spun as a specifically anti-AdSense step, I would be happy if it worked against any <SCRIPT>-included ad-codes, based on originating domain(s). For example, [-adsfrom:doubleclick.net]. That is, if as this article speculates, I may soon be able to block by content-serving domain, I'd also like to be able to block by content-subsidizing domain, as evidenced by the page's ad inserts.