Can your WordPress site move to the edge?

Enter your address and you will get one of three answers, with the reasoning attached: we can move this, we can move it with some custom work, or it is not a fit as it stands.

The scan reads your robots.txt, your home page, the WordPress API index, your sitemap, a handful of your pages, and the theme and plugin readme files those point to — around two dozen requests, and it keeps none of your content.

What we do with a site that can move

We move its front end to the edge and leave WordPress as the place you write. Your pages become files served from the data centre nearest each visitor. The things that cannot be files — forms, comments, search, and whatever else your site does — are rebuilt as small functions beside them. WordPress moves to a subdomain and stays exactly as it is, and the two are kept in step in both directions, automatically.

It is a white-glove service: we do the work, end to end, and you keep writing. It suits two situations — an existing WordPress, often an old one, that deserves modern infrastructure without being rebuilt; and a new site, set up this way from its first page.

How it works, phase by phase · What it costs · Is it the right setup for you?

How the scan knows what it knows

Most WordPress scanners read one page's markup and guess. That finds very little: on a real site we measured, 13 plugins were installed and the markup revealed one, because a plugin only appears in markup if it loads a front-end asset on the page you happened to fetch.

So this reads the WordPress API index instead, which names every plugin that registers routes — including the ones that draw nothing — then confirms each against its own readme for a real name and version. It reads your theme's style.css to get the theme actually in use rather than its parent, and it samples several of your pages so a form on your contact page is not missed.

What no scan can reach: your form field definitions when a form is not on a public page, your submissions, and which plugins are switched on but draw nothing and register no routes. So the verdict is a qualification, not a plan. The plan starts from the assessment below.

The scan identifies itself as EdgeWPsyncScan/1.0, with a link to this section, and reads nothing your robots.txt asks crawlers to leave alone — the home page or any path after it. If your robots.txt cannot be read, it stops. To keep it out entirely: User-agent: EdgeWPsyncScan, then Disallow: /.

Get a real assessment

A scan reads your public pages. An assessment reads your WordPress from the inside — which plugins are active, which theme is running, what fields your forms have, how many pages of each kind — and we run it ourselves, with temporary access to your server that you create and remove. We answer with an indicative scope and price range, or an honest no, free of charge.