01The steps
Export
WordPress export for posts and pages, plus a copy of the uploads folder.
Create the site
Sign up and connect GitHub. The repository and hosting are provisioned for you.
Rebuild
Your coding agent generates the static version from the export, with the SEO basics in the markup.
Test on the preview domain
Every page, the contact form, the mobile layout. Before any DNS change.
Map URLs
Keep slugs where possible. A redirect for every old address that changed.
Flip DNS last
Point the domain using the targets in your portal, with a short TTL.
Post-flip checks, then cancel
Search Console, form test, sitemap. Cancel the old hosting once satisfied.
02The steps
03The steps
New here? Start at the pillar page for the full picture.
Export the content from WordPress, and take a copy of the uploads folder. Sign up and create the site, which provisions the repository and hosting. Rebuild: hand your coding agent the export and the old site address, and it generates the static version with the SEO basics in place. Test everything on the preview domain before any DNS change: every page, the contact form, the mobile layout. Map URLs, keeping slugs where possible and redirecting the rest. Flip DNS last, using the targets shown in your portal, with a short TTL. After the flip: check Search Console, test the form again, submit the sitemap. Cancel the old hosting once you are satisfied, and the annual bill drops to one line.
04What each step prevents
DNS last prevents the classic outage, where the domain points at a host that has nothing built yet. Testing before DNS prevents discovering the broken contact form from a customer. The URL map prevents the ranking dip, which is the only common way a migration costs search traffic. Cancelling last prevents the awkward call to recover an export from a closed account.
05If you would rather not do it yourself
A coding agent does this well because the job is mechanical: read the old site, produce the new files, commit. You review pages in a browser. If you prefer a human, the job is small and quotable flat. Either way the old site stays live until the moment you choose to switch, and what carries over was decided back at the export.
06Frequently Asked Questions
Will there be downtime?
Not if DNS flips last. The old site serves until the records propagate and the new one serves from then on. A five-minute TTL keeps the window short.
Do I need to use the command line?
No. The agent handles git and the build. Your part is reviewing pages in a browser and clicking the DNS change at your registrar.
My site has a shop. Does it convert?
The content pages do. The shop needs a server-side application or a hosted commerce service. Convert the pages, keep the cart where it belongs.
Can I undo the whole thing?
Until DNS flips, trivially: nothing has changed. After, the old export still exists and LoomWeb keeps deployment history for everything since.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.