How it works

We move your site's front end to the edge and leave WordPress as the place you write — or set a new site up that way from the start. It is a white-glove service rather than a button, because the interesting half of any site is the half no crawler can see.

Publishing a post pushes that page, and every page that lists it, to the edge within seconds. A form submitted or a comment left at the edge arrives in WordPress as a real submission or a real comment. Every night, a full check compares what WordPress publishes with what the edge actually serves, and reports any difference instead of hiding it.

You may have met the idea as static WordPress, headless WordPress or WordPress on Cloudflare® Pages. It is closest to the first: the pages your theme renders become static files. What a static export leaves out — forms, comments, search, and keeping the files current — is the part we build. Unlike headless WordPress, your theme stays; nothing is rewritten in a JavaScript framework. For how this compares with every other way of running WordPress, see the best way to set up WordPress in 2026.

What changes, and what does not

The service, phase by phase

Each phase names what we need, what we do, and what you have at the end of it.

1. The scan and the assessment — free

   You

   Scan your address, add your site in your account, and give us temporary access to your server — an SSH account or a hosting-panel login you create and remove.

   We

   Read how your WordPress is built — active plugins, theme, forms and their fields, how much content of each kind — without opening your users, comments or submissions. Then work out which features map onto endpoints that already exist, which need building, which stay on WordPress, and whether your site is a candidate at all.

   You get

   An indicative scope and price range. Or an honest no, which is worth as much: shops, member areas, courses and booking calendars hold live state that a mirror cannot, and saying so in week one is cheaper for everyone than saying it in week six.

2. A rehearsal on a copy — the migration audit

   You

   Give us access: WordPress administrator, your hosting control panel or SSH, and your DNS.

   We

   Clone your site somewhere disposable and run the entire migration on the copy. A rehearsal is how we find the two or three things about your site nobody wrote down: the plugin that hard-codes a domain, the theme that caches its own menu, the form that posts to an absolute address.

   You get

   A written report — what broke, what it costs, what the switch-over window looks like — and a firm price. If the price changes, it changes here, before your live site has been touched. The audit is paid, and deducted from the conversion if you go ahead.

3. WordPress moves to a subdomain

   We

   Move WordPress to an address such as wp.example.com with two lines in wp-config.php rather than a database rewrite — so undoing it is deleting two lines. Anonymous visitors to that address are sent to the public page; only requests carrying credentials are asked for them.

   You get

   The same WordPress, at a new address, with the same editors and the same workflow. Nothing public has changed yet.

4. The edge is built — including your site's own functionality

   We

   Convert every page with its stylesheets, fonts, images and search index, and then do the part that is actually the work: rebuild what your site does. Six endpoints are shared — forms, comments, search, the submission drain, publishing and the sitemap. Everything past those is yours alone: a newsletter signup, a long conditional registration form, a testimonial flow with its own moderation, language routing.

   You get

   The whole site on a preview address, to click through before anything public moves.

5. Both directions, verified

   We

   Install the small plugin that connects WordPress to your edge. Publishing reaches the edge in seconds; submissions and comments reach WordPress. The nightly check starts, and reports the four ways the two sides can disagree: missing, stale, orphaned, or different.

   You get

   Both directions demonstrated on your own content, while we are still watching. A site that publishes but does not receive is half a site, and the missing half is the one that earns.

6. The switch

   We

   Follow a runbook written around the rollback rather than the happy path. Your domain's DNS moves to Cloudflare days ahead, so the switch itself is one record change — seconds to make, and seconds to undo.

   You get

   A live site on the edge, and a rollback that is a phone call and a minute, not an afternoon.

After the switch, you choose how it runs: in your own Cloudflare account, which for most sites costs nothing, with an optional care plan from us. See pricing.

Starting a new site

The same result, without a site to move. There is no scan, no assessment and no rehearsal: we set up WordPress on a private subdomain, with hosting you choose; the edge in your own Cloudflare account; the functions your site needs, such as forms, comments and search; and the sync between them. Then we check the result against the same SEO and accessibility rules as a migration. You start writing in WordPress, and your first page is served from the edge.

Design and content stay yours, or your designer's. What we build is the environment they live in.

A way to modernise an old WordPress

An ageing WordPress is usually slow and exposed for the same reason: every visitor reaches it. Moving the public site to the edge fixes both without rebuilding what you have. The pages, theme and content stay; what serves them becomes modern infrastructure; and the old WordPress stops facing the public. If WordPress itself needs bringing up to date — its PHP version, its plugins — the rehearsal on a copy is where we find out, and the quote says what it takes.

What we need from you, and when it ends

We ask for no more than this, and only for the length of the project. At the end we list every account and key we used, and you remove them. We keep no credentials afterwards. Personal data we can see while we work is covered by a data processing agreement that comes with every quote.

What cannot move

A shop, a members' area, courses, or a booking calendar: each holds live state — a basket, a login, progress, availability — that a mirror cannot hold. A site that draws its content with JavaScript rather than sending it from the server cannot be mirrored either. When your site depends on one of these, we say so at the scan or the assessment, before anything is paid for. We are extending the engine to support these too, and the sites we hear about decide what comes first: if yours depends on one, add it in your account and we will work on a solution with you.

One we have done

7etresoi.fr, a ten-year-old wellness site that had outgrown its shared hosting. Pages that took over 800 ms now arrive in under 50 ms. It meets WCAG AA, its analytics set no cookies, and its form data stays in the EU — and its owner still writes in the same WordPress.