Stop abuse before origin
Blocklists, allowlists, rate limits, and 404 bans run in Sitewrap so scanners never wake your PrestaShop host.
- IP block & allow lists
- Rate limits + 404 bans
- Rules sync to Sitewrap Edge
Cache and shield public PrestaShop pages at Sitewrap Edge while cart, account, and checkout stay on your PrestaShop origin.
/ cached /category/* cached /cart origin-bound /order origin-bound /admin* gated PrestaShop remains your store. Sitewrap absorbs public traffic and abuse earlier.
Blocklists, allowlists, rate limits, and 404 bans run in Sitewrap so scanners never wake your PrestaShop 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.
Exclude cart and checkout, warm categories, cut DNS.
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 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.
Firewall, request log, and analytics — standardized for commerce teams.
Wrap PrestaShop beside WordPress content sites and static landing pages.
No. Sitewrap sits in front of your existing PrestaShop 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 PrestaShop, WordPress, or static — and manage cache, security, leads, and deploys from one Sitewrap account.
Create a Sitewrap account, exclude checkout paths, and go live.