Board Thread:Support Requests - Getting Technical/@comment-5907266-20160128170738/@comment-24473195-20160129170858

Despite being a duplicate post this highlights a core problem with the database reports. I think that some of these are probably not easy to get around, and in some cases might be quite "expensive" to do so. For example, aside from just links from the content namespace that list can also be polluted by the {{ifexists parser function, by broken wikitext, and more. This seems to be a mediawiki problem for close to a decade :


 * https://phabricator.wikimedia.org/T12857

There might not be an easy solution to that problem aside from spending considerable time refactoring the infrastructure or treating other namespaces (e.g. forum) as non-content.

Also, you should be aware that not all insights are actually "violations". For example, there is nothing you can do to make the insights "popular" pages disappear as it is merely informative, and in some cases plain wrong because it doesn't read images from templates for examples.

I think 452's solution would help in your case and many others.