Stop abuse before origin
Blocklists, allowlists, rate limits, and 404 bans run in Sitewrap so scanners never wake your TYPO3 host.
- IP block & allow lists
- Rate limits + 404 bans
- Rules sync to Sitewrap Edge
Supported CMS TYPO3
TYPO3 enterprises, edge-hardened.
Sitewrap sits in front of TYPO3 so public pages hit edge cache, the backend stays gated, and automated abuse dies before it reaches PHP.
TYPO3 surfaces Edge policy
/ cached /page/* cached /typo3 gated /typo3temp hardened fileadmin edge assets Public HIT · /typo3 gated · probes blocked
Built for TYPO3 Edge-first
Enterprise CMS with a modern edge.
Keep TYPO3. Add Sitewrap for visitor-facing performance, security, and operational visibility.
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
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
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
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
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
Wrap TYPO3 with a clear cutover.
Add the site, gate backend paths, warm the sitemap, go live.
Add your TYPO3 site
Enter the public domain and current origin. Sitewrap verifies ownership and checks reachability.
Tune edge defaults
Turn on firewall, admin gating, cache, and form protection. Exclude editor or checkout paths that must stay live to origin.
Warm important pages
Point preload at your sitemap so key URLs are cached before you switch traffic.
Point DNS and go live
Issue TLS, flip the A record, and operate from the dashboard — cache, firewall, forms, analytics, deploy.
Agency and enterprise portfolios welcome.
Standardize TYPO3, WordPress, and static properties under one Sitewrap account.
Platform Multi-origin
TYPO3 plus every other popular origin.
Browse the full Supported CMS list for WordPress, Drupal, Magento, builders, and static websites.
- Any CMS behind the same edge controls
- Static websites without a CMS at all
- Custom origins and hybrid stacks
WordPress Hide WordPress, WAF defaults, admin gate, Oxygen-safe cache, and Forms & Leads. Shopify Edge cache, bot defense, and analytics in front of your Shopify storefront origin. Drupal Shield /user and admin, cache anonymous pages, and harden forms at the edge. Joomla Edge firewall, admin gating, and cache in front of classic Joomla sites. Magento Absorb catalog traffic and bots at the edge; keep checkout on Magento.
FAQ
TYPO3 questions, answered.
Do I need to rebuild my TYPO3 site?
No. Sitewrap sits in front of your existing TYPO3 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 TYPO3, WordPress, or static — and manage cache, security, leads, and deploys from one Sitewrap account.
Wrap TYPO3 without a migration project.
Create a Sitewrap account, gate the backend, warm pages, and point DNS.