If you don’t want the blocked message, open up your site so that anyone can do whatever they want with it until your host shuts it down as a security risk.
Else understand that it is normal, expected, and desired, and don;t worry about the message for wp-admin pages.
No, wrong. There should be no need for anybody other than site admins to have access to that.
What @Mittineague is saying is that you should ensure files which need to be accessed are not in that folder, and then allow access to them.
[quote=“Mittineague, post:15, topic:222488”]
Those files should not be under the wp-admin folder. Typically they’re under the wp-includes folder.
[/quote]So you would allow access to the wp-includes folder, but not wp-admin.
If a site’s robots.txt file disallows crawling these resources, it can
affect how well Google renders and indexes the page, which can affect
the page’s ranking in Google search.
The admin files are no one else’s business but your own. You do not want them to be indexed or to rank, they should be kept private. So this warning does not matter, it’s saying they won’t index something that you don’t want indexed.
It will only be stopping access to “wp-includes” if that directory is located inside “wp-admin”, which it should not be. Check your site structure to see where “wp-includes” is located.
Try a site:yourdomain search on Google to check whether there really is a problem with Google indexing pages.