Publishing versus exporting
Two ways to ship, what each requires, and how to move a live site over safely.
Updated 4 hours ago
You have two ways to ship, and they are not mutually exclusive.
Publish
One click puts the current version on a live zrdio URL at /sites/your-address.
- The address is stable. Re-publishing points that same URL at a newer version rather than creating a second site.
- It requires a confirmed email address, because it puts content on a public URL under our domain.
- Each published site counts against your plan's published-sites limit.
- You can take it offline at any time. Your versions and content are kept.
Export
Downloads a zip containing one HTML file per page, with the CSS inlined, plus a robots.txt, a sitemap.txt and a README.
- No build step, no framework, no runtime. It will host anywhere that serves static files.
- Available on every plan, including free. This is the anti-lock-in guarantee, so it is deliberately unrestricted.
Moving an existing site over
Do it in this order:
- Export the zip and upload it somewhere staging, not your live domain.
- Compare the two side by side. Check every phone number, email address and price.
- Point the contact form at your form handler. The exported form deliberately posts nowhere, so it cannot silently swallow enquiries.
- Replace the gradient placeholders with real photographs, and give each one meaningful alt text.
- Only then repoint DNS.
- Re-scan the live URL to confirm everything landed.
Custom domains
Available on Growth and Scale. Publish first, then add the domain from the publish tab and follow the DNS instructions shown there.