Publishing is a one-click action that needs a ten-minute pre-check. This guide walks through the critical warning about replacing existing files, the pre-publish checklist, how to actually publish, domain and DNS configuration, SSL setup, and the post-publish verification steps every UK site should go through on launch day.
Introduction · Critical warning — publishing replaces existing files · Pre-publish checklist · How to publish your website · Domain and DNS configuration · Setting up SSL and HTTPS · After publishing — verification steps · Republishing and updating your site · Project status workflow · FAQ
Clicking Publish pushes your site from the Sitejet preview to the live web. The action is instant; the implications are not. A rushed publish can leak placeholder text, break inbound links from an old site, trigger “Not secure” warnings, or put draft content in front of customers. Ten minutes of checks before the click saves days of remediation after.
If you are publishing to an existing domain that already hosts a different site (for example, an old WordPress installation), publishing Sitejet replaces the existing files on that domain. The old site is gone from that domain. Back up your old site first if you need the content or files.
To stage a Sitejet site without touching an existing live one, publish to a staging subdomain (staging.yourdomain.co.uk) first. When ready, switch the DNS to the final domain.
/sitemap.xml).Three common scenarios:
DNS propagation: 15 minutes for most UK domains via Nominet; up to 48 hours for slow global resolvers.
SSL activates automatically via Let’s Encrypt once DNS resolves to the Sitejet server. Expect 5–15 minutes after DNS propagation for the padlock to appear.
If visitors see “Not secure” after 30 minutes, check:
dig yourdomain.co.uk from the command line)SSL auto-renews every 90 days. You do not need to do anything.
http:// redirects to https://.After the first publish, subsequent publishes push incremental changes. Sitejet intelligently pushes only modified pages. A routine content update typically republishes in seconds.
Practical note: autosave in the editor does not publish to live. You must explicitly click Publish to push changes to visitors. Some owners find this confusing — remember the distinction: autosave = preview draft; publish = live site.
The status indicator appears in the top toolbar. Always check it before closing the editor — leaving unpublished changes means they do not reach visitors.
Q: How long does publishing take?
A: Initial publish: typically under 30 seconds. Republishes: 5–15 seconds for incremental changes.
Q: Can I unpublish a site?
A: Yes — Site Settings → Unpublish. The site remains in your editor but is removed from the live URL.
Q: What happens if I publish over an existing WordPress site?
A: WordPress files on the domain are replaced with Sitejet output. Back up WordPress first if you need the content or plugins.
Q: Why is SSL not activating?
A: Usually a DNS issue. Run dig yourdomain.co.uk from the command line; if it does not resolve to the Sitejet IP, DNS has not fully propagated. Wait or check nameservers.
Q: Can I publish to a subdomain for staging?
A: Yes — configure staging.yourdomain.co.uk in DNS, publish to that subdomain, review, then switch main domain DNS when ready.
Q: Does Sitejet notify Google when I publish?
A: No. You must submit the sitemap to Google Search Console yourself. Typical indexing delay: 24–48 hours after submission.