Indexed despite being blocked in the robots.txt file, how to fix it?

Question

Google

Google gave me this error.

It is interesting that the link to the authorization page with a redirect indicates:
https://basseyn-svoy.ru/wp-login.php?redirect_to=h...

If you follow it, there will be an authorization page. After authorization opens the post.

There is a ban on /WP-LOGIN.php in ROBOTS.TXT.

The standard solution to this problem is to write noindex in the head. But here you need to get into the core of WORDPRESS.

How to be and what are the proposals? Thank you all for your replies in advance.

Answer 1

1. Ask a question, how does this bother you? How critical is that wp-login is indexed like a billion other sites on WP. If this was a real problem, WP would have jumped in and fixed the head for this page a long time ago.
2. Robots for Google is not a ban, but only a recommendation. Therefore, robots cannot solve this problem.
3. I'm not a WPer, there is probably a way to fix the situation with meta robots or meta goolebot without breaking the core, as is done in other CMS.
4. Google the subject of the HTTP header "X-Robots-Tag: googlebot: noindex".
5. Well, the most perverse way is to catch Googlebot (or all bots at once) at the web server level (for example, by User-Agent or some other signs, by subnets), and return 403 to them when accessing wp-login .php