How WranglePress works
In one sentence: we make a copy of your WordPress® site as plain files and show that copy to visitors from Cloudflare's worldwide network. Then you decide what happens to WordPress: keep it private for editing, or retire it.
- Copy. We visit every page of your site, like a very thorough visitor, and save each page with its images, styles and scripts.
- Check. You get a private preview link. Click around and send a test form before anything changes.
- Go live. You point your domain at WranglePress. Visitors now get the copy, served from a data center near them.
- Keep it or retire it. Keep editing in WordPress, and every publish updates the copy, usually within a minute or two. Or switch WordPress off for good, and the site stays exactly as it is.
What visitors get
Visitors get the same pages they see today: same design, same words, same web addresses. The difference is behind the scenes. Their requests are answered with saved files. No PHP runs and no database is asked anything. That's why it's fast, and why a flaw in WordPress, a plugin or PHP has no public door to come through.
What stays the same
- Your design and content. Your theme, page builder output, words and images are copied exactly.
- Your web addresses. Every page keeps its address, so search rankings and links keep working.
- Your forms. They keep working (see below).
- No passwords handed over. We don't need your hosting or WordPress admin password.
Your choice: keep WordPress or retire it
| Keep WordPress (private) | Retire WordPress | |
|---|---|---|
| Editing | In WordPress, as today | The site stays as it is |
| Updates when you publish | Automatic, usually within a minute or two | No more changes |
| hosting for WordPress | Keep paying for it | Cancel it |
| Plugins and PHP to update | Yes, on your schedule | None |
| Contact forms | Email or forwarded to WordPress | Emailed to you |
| Good for | Sites that change often | Sites that rarely change, or nobody maintains |
You can switch either way later. If a retired site needs changes, restore WordPress from a backup, point WranglePress at it, and build again.
Option 1: keep WordPress, private
After go-live, WordPress moves to a private address, for example wp.example.com, protected by a login screen in front of WordPress itself (we recommend Cloudflare Access, which is free for small teams). Strangers who find the address see a login prompt, not WordPress. You give WranglePress a key so our builder can still read your pages.
On cheap shared hosting, you can also tell the server to accept web traffic only from Cloudflare. Our help pages walk you through both.
Option 2: retire WordPress
Once your site is live on WranglePress and you've checked it, you can switch WordPress off. Make a full backup first (your host or a backup plugin can do this), download a ZIP of the site from your dashboard, set forms to email mode, then cancel the hosting for WordPress or delete the site. The copy keeps serving exactly as it was at its last build. The help pages walk you through it.
Rebuilds when you publish
If you keep WordPress, install our free WranglePress Connector plugin and paste in your key. From then on, WordPress tells us whenever you publish, update or delete something, or change menus, widgets or the theme. We rebuild the copy and switch it over all at once. The plugin also adds a Rebuild now button in WordPress.
If a build fails, the live site doesn't change. We email you, and the dashboard shows what went wrong.
Not on WordPress? The copy works the same way for any website that shows every visitor the same pages; the plugin is WordPress-only, so you click Build now after a change. What's different for other websites.
Forms
Your contact forms keep working. You choose how:
- Email mode: we send each submission to the addresses you choose. Nothing reaches WordPress.
- Forward mode: we pass each submission to your private WordPress, so your form plugin's own emails, saved entries and integrations keep running.
Contact Form 7 and WPForms are supported directly, and most simple contact forms work. Test yours on the preview first.
Download your site any time
Any finished build can be downloaded as a ZIP of every page and file, ready to put on any static host. Big sites resume if the download is interrupted. It's your site, so you can always take it with you.
Rollback in one click
Every good build is kept. If something looks wrong, pick an earlier build and click Roll back to this. The switch happens immediately. You can also take the copy offline and point your domain back at WordPress at any time.
Do it from your AI assistant
Everything above can also be done by chatting. WranglePress has an MCP server: connect Claude, ChatGPT, Claude Code or Cursor, and ask it to add sites, run builds, connect domains, publish, roll back or change form settings. It works through the same steps and the same permissions as the dashboard, and it can handle up to 25 sites in one go. AI assistants →
What you need
- A WordPress site (any host, any theme), or another website that shows every visitor the same pages.
- Access to your domain's DNS settings, to point the domain at us when you're ready.
- About 15 minutes for the first site. See the getting started guide.
Join the waitlist See pricing 14 days, 2 sites, no card needed.
Last updated 2026-10-24.