That'd work too, although I'd implement it the other way around. Define a new http header that indicates what type of content the site you're visiting is hosting and handle the content blocking client-side based on those headers.