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 transfer this, we can transfer 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. No public address? That is fine: a repository and a database dump tell us more than a scan ever can.

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, which live in the database and have no public route at all. So the verdict is a qualification, not a plan — scoping a transfer needs the WordPress files and a database dump, both onboarding-scoped and both revocable.