Stop abuse before origin
Blocklists, allowlists, rate limits, and 404 bans run in Sitewrap so scanners never wake your Ghost host.
- IP block & allow lists
- Rate limits + 404 bans
- Rules sync to Sitewrap Edge
Keep writing in Ghost. Sitewrap caches public posts at the edge, gates admin, and gives you request-level analytics and partner tracking.
/ cached /blog/* cached /ghost/ gated /members origin-bound /content/images edge assets Ghost stays your CMS. Sitewrap is the edge layer for performance, security, and visibility.
Blocklists, allowlists, rate limits, and 404 bans run in Sitewrap so scanners never wake your Ghost host.
Gate admin and login surfaces until Sitewrap unlocks them with a passwordless magic link or short code — so random scans never reach the unlock screen.
Cache HTML and assets at Sitewrap Edge. Preload from your sitemap so first visitors already hit warm pages.
Detect HTML forms on proxied pages, harden submissions, and land clean leads in Sitewrap with field mapping.
See every visit in the Sitewrap request log, then ship the same event catalog to Mixpanel and GA4 without stacking more origin plugins.
Deploy selected pages, preload cache, and roll back from the dashboard — while your CMS stays the content source of truth.
Add the site, gate /ghost/, warm posts, go live.
Enter the public domain and current origin. Sitewrap verifies ownership and checks reachability.
Turn on firewall, admin gating, cache, and form protection. Exclude editor or checkout paths that must stay live to origin.
Point preload at your Ghost sitemap so key URLs are cached before you switch traffic.
Issue TLS, flip the A record, and operate from the dashboard — cache, firewall, forms, analytics, deploy.
Mixpanel/GA4 plus Sitewrap request logs — without stuffing the Ghost theme with scripts by hand.
Wrap Ghost blogs next to WordPress marketing sites and static docs.
No. Sitewrap sits in front of your existing Ghost origin. Keep your templates, apps, hosting, and editors — Sitewrap adds the edge layer.
Yes. Keep admin, editor, and other private paths origin-bound or gated. Public visitors get the cached, protected experience.
No. Firewall, cache, analytics, forms, deploy, and admin gating work in front of any CMS or static site. WordPress gets extra remaps and WAF defaults.
Yes. Wrap each client domain — whether Ghost, WordPress, or static — and manage cache, security, leads, and deploys from one Sitewrap account.
Create a Sitewrap account, gate admin, warm your sitemap, and point DNS.