Site Builder separates saved edits, preview, DNS connection, HTTPS readiness, publishing, and rollback. A saved or previewed change is not live until a publish succeeds.
Preview before publishing
- Open Admin → Website & Domains → Site Builder.
- Review pages, navigation, content, images, forms, reservation links, and commerce links.
- Open Preview ready edits or Preview site.
- Check desktop and mobile layouts and complete every customer action in preview.
- Return to Site Builder and review publish readiness.
Connect a custom domain
- Open the Site Builder domain or setup section.
- Enter the customer-owned domain intended for the live site.
- Save the domain and copy every exact DNS Type, Host / Name, and Value / Target row shown by Ellich.
- At the customer's current DNS host, add or update every listed website record.
- Keep the current nameservers unless the customer intentionally moves DNS hosting.
- Wait for DNS propagation, then select Check DNS & HTTPS.
For a root domain such as example.com, Ellich lists at least two required rows: @ for the root address and www for www.example.com. Both rows point to the same Ellich target, using the record type shown for each row. If the chosen primary address is already a subdomain such as shop.example.com, Ellich lists one row for that subdomain. Do not publish until every listed hostname passes DNS verification. URL forwarding can be used for a temporary demonstration but is not the final commercial connection.
Publish the website
Publish becomes available after required readiness checks pass and, for a custom domain, DNS is verified. Select Publish website or the current publish action once. Wait for the result and review any warning.
After publishing, verify:
- Every public live URL listed by Ellich opens over hostname-validating HTTPS.
- The expected release is active.
- Navigation, reservation, ordering, and contact actions work on the live domain.
- A clean browser session receives the current content.
- Domain health remains verified.
Roll back a release
Open the release history and choose Rollback only when a previous known-good release should become active. Confirm the target release before proceeding. Rollback changes live content; it does not undo unrelated database records, orders, reservations, or DNS ownership.
After rollback, open the live URL in a clean browser and verify the restored pages and customer actions.
If go-live is blocked
Read every readiness reason. Common causes include an unreviewed preview, missing required site content, commerce readiness, a domain not saved, DNS not verified, or HTTPS still provisioning. Correct the owning setting and run the readiness or DNS check again. Do not repeatedly publish while DNS or readiness remains unresolved.