@mwmiller We're a bit fuzzy on it too, but I think the best way to think about it to know _why_ we're watching out for these in the first place. We're watching out for these because we don't want children to accidentally run into these when they search on DuckDuckGo. Consider the Urban Dictionary IA. Most of the time you get profanity for searches that aren't profane such as "dictionary" where you get:

![screen shot 2014-04-04 at 10 57 40 am](https://cloud.githubusercontent.com/assets/81969/2616678/7dd0968e-bc09-11e3-9907-2f1d354586e9.png)

So for Urban Dictionary we have to set the adult flag on because it's easy to run into these. I know that they can just click on the organic links for these, but at least it's an extra step. Another example is SoundCloud. If a kid searched "soundcloud ray bradbury" to listen to his talks, we wouldn't want her to run into this accidentally:

![screen shot 2014-04-04 at 11 07 31 am](https://cloud.githubusercontent.com/assets/81969/2616844/1d26d6de-bc0b-11e3-992d-188f09547ce7.png)
 
Again, it's easy to get to these on the Internet, but the least we can do is to prevent them from accidentally running into these. Maybe @yegg can shed some light on this, too. 

I hope I answered your question! Maybe I should put a version of this in the docs?