WPS Hide Login does exactly one thing: it rewrites which URL reaches wp-login.php and blocks the real one. A public visitor never requests wp-login.php or wp-admin during ordinary browsing on a static site, so this has no effect on static build output at all. Worth knowing up front, though: this targets the exact same thing Static Shield's own built-in Admin Access Gateway already controls, and running both at once is a real, documented source of lockouts — not just redundancy.
Fully Static
Everything — the plugin has no public-facing feature of any kind. Its login-URL rewrite only ever concerns an admin or editor who is already trying to sign in, never an ordinary visitor.
None.
None needed — WPS Hide Login declares no public routes of its own.
Detected automatically once active — but before relying on it, check whether Static Shield's own Admin Access Gateway is also enabled. Running both at the same time is not recommended; see limitations above.
This overlaps directly with Static Shield's own Admin Access Gateway: both try to control reachability of wp-login.php and wp-admin at the same time. If they disagree about what the "real" login path currently is, an admin or editor can be locked out of the dashboard entirely, or the two rewrites can conflict and produce confusing 404s instead of a login screen. Run only one of the two — Static Shield's own Admin Access Gateway is the recommended choice since it's mode-aware and already integrates with Zero-WordPress and Vault; once it's configured, disable WPS Hide Login's URL rewriting rather than leaving both active. This has not been behaviorally validated against a live install.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp