Sitewrap sits in front of your existing WordPress site with edge cache, Hide WordPress, admin gating, WAF defaults, and Forms & Leads. Keep your theme, plugins, and hosting.
/assets /wp-content /vendor /wp-includes /api /wp-json /admin /wp-admin /login.php gated · /wp-login.php Security plugins and host panels still matter. Sitewrap adds the layer visitors hit first: remaps, gates, cache, and form defense that do not require a rebuild.
Remap /wp-content, /wp-includes, /wp-json, /wp-admin, and /wp-login.php to cleaner public paths. Sitewrap rewrites HTML, CSS, and JS so visitors never see the usual WordPress tells.
Gate /wp-admin and /wp-login.php until Sitewrap unlocks them with a passwordless magic link or short code. Scanners never reach the real login screen.
Disable XML-RPC, harden comments and REST user endpoints, block author enumeration, and stop readme/license probes — without stacking another security plugin.
Edge cache and preload from wp-sitemap.xml (or your sitemap) so visitors hit Sitewrap first. Builder and editor traffic stays on origin so Oxygen and similar tools keep working.
Detect Contact Form 7, WPForms, and other HTML forms on proxied pages. Protect submissions at the edge and land clean leads in Sitewrap — field mapping included.
When Sitewrap recognizes WordPress during setup, you can apply a recommended security skeleton before cutover — firewall, WAF toggles, and route hygiene included.
The dashboard wizard recognizes WordPress and nudges you toward a safe starting config.
Enter the public domain and current origin. Sitewrap verifies ownership and checks reachability.
If WordPress is detected, review Hide WordPress, WAF, admin gate, and cache recommendations — then save.
Point preload at wp-sitemap.xml (or your 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.
Request log, live users, Mixpanel/GA4, A/B tests, deployments, and AI assist work the same on WordPress as on any other origin.
Agencies and product teams often run WordPress beside marketing sites, headless fronts, and static exports. Sitewrap wraps each property the same way — with WordPress getting the richest defaults.
No. Sitewrap sits in front of your existing WordPress origin. Keep your theme, plugins, hosting, and editors — Sitewrap adds the edge layer.
Yes. Builder and editor requests are treated as origin-bound so you can edit safely. Public visitors get the cached, optimized experience.
It remaps common WordPress paths to cleaner URLs and rewrites references in HTML, CSS, and JavaScript served through Sitewrap. Your origin still speaks WordPress paths upstream.
No. Firewall, cache, analytics, forms, deploy, and admin gating work in front of any CMS or static site. WordPress gets deeper defaults and remaps — this page is that story.
Yes. Wrap each client domain, apply the WordPress skeleton, and manage cache, security, leads, and deploys from one Sitewrap account.
Create a Sitewrap account, apply WordPress defaults, gate admin, and warm your sitemap — then point DNS.