Black Friday Black FridayUp to 85% off all WP Ghost plans.48 months from $49, or pay once for lifetime. SHOP NOW

Does WP Ghost Work on SiteGround Hosted Websites?

Moved

This tutorial has moved to the new WP Ghost Knowledge Base where each feature is presented in detail.

View on new site

Yes. WP Ghost works on SiteGround: it writes its rules to .htaccess, which SiteGround’s Apache layer reads, and it has a SiteGround option in Server Type if auto-detection misses it. No Nginx configuration is needed.

How WP Ghost works on SiteGround

SiteGround uses Nginx as a reverse proxy in front of Apache. WP Ghost detects this setup and writes rewrite rules to the .htaccess file, which Apache processes behind Nginx. You do not need to edit any Nginx configuration files manually. WP Ghost handles everything through the standard .htaccess mechanism that SiteGround supports.

When you install WP Ghost on a SiteGround site, the plugin auto-detects SiteGround as the hosting provider. If it doesn’t, you can manually select the SiteGround profile at WP Ghost > Advanced > Compatibility > Server Type.

SiteGround caching and WP Ghost

SiteGround includes its own caching system (the Speed Optimizer plugin, formerly SG Optimizer) with both static cache and dynamic cache (Nginx Direct Delivery). If you want to hide WordPress common paths to file extensions like CSS, JS, TXT and HTML with WP Ghost’s Hide WordPress Common Paths feature, you may need to switch off SiteGround’s Nginx Direct Delivery option. Nginx Direct Delivery serves static files before they pass through Apache’s .htaccess rules, so WP Ghost’s rules for those file types can be skipped.

To check this setting, go to your SiteGround Site Tools panel, open Speed > Caching > Nginx Direct Delivery, and switch it off if you use WP Ghost’s file extension hiding. Standard page caching (Dynamic Cache) can stay on and works with WP Ghost.

Using WP Ghost with the host’s security plugin

SiteGround also offers its own free security plugin, and WP Ghost runs alongside it. That plugin focuses on activity logging, login hardening and post-hack tools; WP Ghost focuses on hack prevention with path security, firewall rules and a smaller attack surface.

The key rule is to avoid switching on the same feature in both plugins. Let WP Ghost handle the custom login path, brute force protection and 2FA. If the host’s plugin has its custom login URL on, turn it off there and set the login path in WP Ghost. For the full configuration guide, see the WP Ghost with SiteGround’s security plugin tutorial.

Frequently asked questions

Do I need to edit Nginx config files on SiteGround?

No. SiteGround processes .htaccess rules through Apache behind Nginx. WP Ghost writes all its rules to .htaccess automatically. No manual Nginx configuration is required.

Do I need the host’s security plugin if I have WP Ghost?

Not for hack prevention: WP Ghost covers that, and it has its own User Events Log for activity logging. The host’s plugin adds post-hack tools. If you keep it, switch off the features WP Ghost already handles.

Will WP Ghost work with SiteGround’s staging environment?

Yes. WP Ghost works on staging sites the same way it works on production sites. When you push a staging site to production on SiteGround, clear all cache afterward and verify your WP Ghost paths are working by running the Security Check.

Does WP Ghost modify WordPress core files?

No. WP Ghost writes rewrite rules to .htaccess and uses WordPress hooks for application-level changes. No WordPress core files are modified. Deactivating WP Ghost restores all default paths instantly.