Supported CMS Webflow

Webflow design. Sitewrap operations.

Keep designing in Webflow. Sitewrap wraps the published site with edge security, request visibility, experiments, and lead capture.

Keep Webflow DesignerEdge A/B testsForms & Leads
Webflow → Sitewrap Publish path
/ Webflow HTML · cached
/blog/* cached
/_webflow/* editor assets
/forms edge-protected
DNS Sitewrap Edge
Designer stays Webflow · visitors hit Sitewrap first
Built for Webflow Edge-first

Marketing sites that operators can run.

Webflow is excellent for design. Sitewrap adds the ops layer: security, analytics, experiments, and lead hygiene.

Edge firewall

Stop abuse before origin

Blocklists, allowlists, rate limits, and 404 bans run in Sitewrap so scanners never wake your Webflow host.

  • IP block & allow lists
  • Rate limits + 404 bans
  • Rules sync to Sitewrap Edge
Admin gate

Keep the back office private

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.

  • Magic link + short code
  • Unlock cookie on your domain
  • Works with remapped paths
Cache

Serve pages from the edge

Cache HTML and assets at Sitewrap Edge. Preload from your sitemap so first visitors already hit warm pages.

  • TTL + stale options
  • Sitemap crawl & warm
  • Editor paths stay origin-bound
Forms & leads

Spam dies at the edge

Detect HTML forms on proxied pages, harden submissions, and land clean leads in Sitewrap with field mapping.

  • Honeypot + time-on-page
  • Per-IP form rate limits
  • Lead groups & visitor context
Analytics

Request log + Mixpanel / GA4

See every visit in the Sitewrap request log, then ship the same event catalog to Mixpanel and GA4 without stacking more origin plugins.

  • Live users & engagement
  • Consent-aware partners
  • Server + client events
Deploy

Publish without origin drama

Deploy selected pages, preload cache, and roll back from the dashboard — while your CMS stays the content source of truth.

  • Page-level publish
  • Cache preload
  • Rollback-friendly releases
Setup Minutes, not months

Publish in Webflow. Wrap with Sitewrap.

Point Sitewrap at your Webflow hosting/origin, warm pages, then move DNS.

01

Add your Webflow site

Enter the public domain and current origin. Sitewrap verifies ownership and checks reachability.

02

Tune edge defaults

Turn on firewall, admin gating, cache, and form protection. Exclude editor or checkout paths that must stay live to origin.

03

Warm important pages

Point preload at your sitemap so key URLs are cached before you switch traffic.

04

Point DNS and go live

Issue TLS, flip the A record, and operate from the dashboard — cache, firewall, forms, analytics, deploy.

Experiments without Designer chaos.

Run A/B variants and tracking at the edge while designers keep shipping in Webflow.

FAQ

Webflow questions, answered.

Do I need to rebuild my Webflow site?

No. Sitewrap sits in front of your existing Webflow origin. Keep your templates, apps, hosting, and editors — Sitewrap adds the edge layer.

Will editors and admins still work?

Yes. Keep admin, editor, and other private paths origin-bound or gated. Public visitors get the cached, protected experience.

Is Sitewrap only for WordPress?

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.

Can agencies standardize this across clients?

Yes. Wrap each client domain — whether Webflow, WordPress, or static — and manage cache, security, leads, and deploys from one Sitewrap account.

Wrap Webflow without leaving Designer.

Create a Sitewrap account, connect your domain origin, and turn on edge controls.