Provide generic and/or targeted motivation for the X-Robots-Tag: noindex header on package page

[pieterjanv]

npmjs.com prevents my package from being indexed by serving its page with a X-Robots-Tag: noindex header. It would be very helpful to be able to examine and eliminate the possible reasons for this.

Possible solutions:

• List (the most common) reasons for this header to be served on a package page in the documentation, possibly under the policies section.
• An automated notification to the user of the header being generated with a specified reason.