Go Live Without Risk: Run Your Old WordPress and the New Static Site Side by Side
04 Oct, 2026 • 5 min read
The scariest moment of leaving WordPress is not the migration. It is the day you switch the domain. This guide shows a low-risk way to do it: leave your old site untouched, bring the new static site up next to it, switch only when you are ready, and keep the old one for a couple of months as a safety net. Nothing here requires you to shut anything down on day one.
The idea in one paragraph
Your old WordPress stays exactly where it is, serving visitors. You publish the static version at a separate, private address and check it. When you are happy, you point your domain at the new site. If something is wrong, you point it back, because the old site is still running. After a couple of months without problems, you take a full backup of the old WordPress and close it.
Step 1: Leave the old site alone
Do not cancel hosting, change plugins or “clean up” anything yet. The whole plan depends on the old site staying exactly as it is. If you can, avoid publishing new content on it for the few days of the switch, so the two copies do not drift apart.
Step 2: Publish the new site at a test address
Both Cloudflare Pages and GitHub Pages give a project its own default address. Deploy the static site there first, not on your real domain.
- A test copy can be found by search engines. Don’t link to it publicly and don’t submit it to Google; block it from indexing or keep the address to yourself until the switch.
- Open it on your phone and your computer and compare it, page by page, with the old site.
Step 3: Check the things people forget
- Your most important pages, including the ones that bring traffic. Check titles, links and images.
- Old URLs. If any address changes, it needs a redirect from the old one to the new one.
- Forms, search and comments, if you use them: submit a test form and run a search.
- Analytics and tracking tags, so you don’t lose your history.
- Sitemap and robots file: the new site should publish its own.
- Email. Your domain’s email depends on DNS records (MX, SPF, DKIM). If you move DNS management, copy every existing record first. Changing the website must not change your email.
Step 4: Prepare the switch
A day or two before, lower the “TTL” (the time DNS records are cached) of the records you will change, so the switch takes effect faster and a rollback does too. Write down the current values of those records. They are your way back.
Step 5: Switch the domain
Point the domain (and the www version) to the new site, following your host’s instructions for custom domains. Wait for the HTTPS certificate to be issued, then check the real domain again: home page, a few inner pages, and a form if you have one.
Step 6: If something is wrong, go back
Because the old site is still running, rolling back is just putting the previous DNS values back. Keep the notes from Step 4 handy. Anything published on the old site during the overlap needs to be reapplied to the new one, which is why it helps to freeze content during the switch.
Step 7: Watch it for a few weeks
- In Google Search Console, submit the new sitemap and keep an eye on errors and “not found” pages.
- Look at your analytics: traffic should look like before. A sudden drop on specific pages usually points to a missing redirect.
- Check that forms and email still work.
Step 8: Close the old WordPress, safely
After a couple of months with no problems:
- Take a full backup: all files and the database, and keep two copies in different places.
- Make sure nothing in the new site still points to the old server (images, scripts, downloads).
- Cancel the old hosting. Keep renewing your domain name.
Until you close it, remember that the old server is still online and still needs updates, even if nobody visits it. Restrict access to it or keep it updated for the overlap period.
What it costs
The only extra cost is the old hosting for the overlap, typically a couple of months. In exchange, the day you switch is no longer a leap of faith: you can undo it.
Where ZeroPress fits
ZeroPress gives you the static site as a repository you own, so you can publish it to a test address and to your domain on your own schedule. If you want a second pair of eyes on the switch, run the free check first to see whether your site can go static, and start with the free 4-post migration to try the whole path before committing to anything.