WordPress plugin
WP Hide PRO for WordPress Path and Asset Rewriting
WP Hide PRO is the paid edition of WP Hide & Security Enhancer. It uses URL rewrite techniques and WordPress filters to change how technical paths appear to users and automated scanners. The changes are applied virtually: existing server files and directories stay in place.

Virtual path controls
WP Hide PRO is the paid edition of WP Hide & Security Enhancer. It uses URL rewrite techniques and WordPress filters to change how technical paths appear to users and automated scanners. The changes are applied virtually: existing server files and directories stay in place.
Administrators can hide or replace references to WordPress core files, the login page, themes, plugins, and selected assets. Settings can also hide or block default paths that may identify WordPress. Sites can keep their public content URLs while changing administrative and static asset paths. Posts, pages, categories, sitemaps, and canonical tags are described as remaining unchanged.
Path and response header options
- Hide WordPress core files and plugin paths from front-end detection.
- Replace the default wp-admin and wp-login.php login paths with an alternative URL.
- Mask or replace theme, add-on, upload, and other asset paths.
- Support complex themes and plugins that may require the PRO edition.
- Configure HTTP response headers, including COEP, COOP, CORP, Referrer-Policy, X-Content-Type-Options, X-Download-Options, X-Frame-Options, X-Permitted-Cross-Domain-Policies, and X-XSS-Protection.
Nginx configuration
The interface generates dedicated Nginx configuration snippets for URL masking, asset renaming, and response header rules. Add the generated snippets to the server block. The product information describes compatibility with Apache, LiteSpeed, and IIS, as well as Nginx when it is used as a reverse proxy.
Setup and maintenance
Install WP Hide & Security Enhancer, activate the paid PRO edition, and open its settings. Review the hiding and replacement options, select the paths and headers the website needs, and apply the configuration. For Nginx, generate the required snippets and add them to the server block.
Test the login URL, front-end asset paths, response headers, and website cache before completing setup. Detector reports may be delayed by caching, so clear the relevant server cache and test again, including an inner URL as well as the homepage. WordPress, plugin, and theme updates can continue through the dashboard or WP-CLI without disabling WP Hide.
