Finding Sitejet Changes That Do Not Appear on the Live Site Print

When the editor and public website disagree, identify which version and address you are viewing before changing design settings.

Steps

1. Confirm that the edit was saved in the correct project and language. Preview it in the editor to establish that the intended draft contains the change.
2. Follow this product’s deployment behavior: cPanel uses a separate Publish action, while Sitejet Studio can push saved edits directly to an already published site. Check the resulting public version instead of assuming Save is always draft-only.
3. Compare the full public URL: domain, HTTPS, page path, and language prefix. Check both the page linked by navigation and the direct URL.
4. Use a private browser window and compare another device or connection. If only one browser is stale, refresh its cached page.
5. If all visitors see an older version after a successful publication, inspect any configured website or CDN cache and purge the affected URL using that service’s controls.
6. If one element alone is wrong, check whether it is a shared reference, a language-specific copy, or custom code whose live behavior differs from the editor.

Check the result

Repeat the public visit without an editor session and confirm that the intended text, image, and navigation destination are current.

Before you continue

Keep customizations inside the supported builder workflow. Changes made directly to generated hosting files can disappear during a later publication.

Documentation for this guidance: help.sitejet.io — 24275952909463 Overview Website Builder CMS; docs.cpanel.net — sitejet builder; help.sitejet.io — 24276005732503 How to create references.